delegate SKILL.md skillA
delegate from abdurrafay2004/handoff is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add abdurrafay2004/handoff/delegate@git:20261008.0e07558Pins git:20261008.0e07558 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- abdurrafay2004/handoff
- Path
skills/delegate/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261008.0e07558, committed Oct 8, 2026
- First version recorded
- Jul 2, 2026
- Size
- 5,617 bytes
- Repository stars
- 5
- License
- MIT
Use when a task would flood the main context window — broad searches, verbose test/build output, 2+ independent parallel tasks, or an isolated large workstream. How to hand work to subagents well, and when not to.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Delegate Part of the **Build** phase — see the `workflow` skill for tiers and sequencing. Subagents exist to **protect the main context window** and exploit **true parallelism** — not to add process. Every dispatch costs a full agent spin-up: the agent re-reads context, explores, works, and reports. Spend that cost only when it buys something. ## Triggers — delegate when (and only when) 1. **Context-flooding search/read:** answering requires sweeping many files but you only need the conclusion, not the file contents. 2. **Verbose output:** test suites, builds, long logs — where only the summary matters in the main session. 3. **True parallelism:** 2+ genuinely independent tasks with no shared state and no sequential dependency. 4. **Isolated large workstream (T3):** big enough that a fresh, focused context outperforms a crowded one. When a trigger fires, **stop and ask with the host's available question tool or a short chat question** (`AskUserQuestion` in Claude Code): name the task, why it triggered, a suggested model tier, and delegate-or-inline as options. Never decide silently in either direction. This applies at the trigger point, whenever …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dgglbai2d4eudkmy/1a8abe846e0a996dee32f4bd3a50a7de71d42357ddc6e6127cf2660ecbc1f04a.json
Then /plugin install delegate@markdownregistry-dgglbai2d4eudkmy in Claude Code. It installs git:20261008.0e07558, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add abdurrafay2004/handoff/delegate@sha256:1a8abe846e0a996dThe line at the top of this page pins the label git:20261008.0e07558, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dgglbai2d4eudkmy)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in abdurrafay2004/handoff/delegate since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of delegate from somewhere else? Ask it: where did my delegate come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Jul 2, 2026 and Oct 8, 2026, about one every 25 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.0e07558 latest | 2026-10-08 | 0e07558 | 5,617 B | A | view · diff |
| git:20260711.46a3400 | 2026-07-11 | 46a3400 | 5,536 B | A | view · diff |
| git:20260710.678ecc7 | 2026-07-10 | 678ecc7 | 5,654 B | A | view · diff |
| git:20260702.0ea7c43 | 2026-07-02 | 0ea7c43 | 5,188 B | A | view · diff |
| git:20260702.82cfccf | 2026-07-02 | 82cfccf | 5,162 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/delegate/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5617 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
abdurrafay2004/handoff · 5 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dgglbai2d4eudkmy GET https://markdownregistry.com/api/v1/resolve?ref=abdurrafay2004/handoff/delegate GET https://markdownregistry.com/api/v1/blob/1a8abe846e0a996dee32f4bd3a50a7de71d42357ddc6e6127cf2660ecbc1f04a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from abdurrafay2004/handoff
Every file in abdurrafay2004/handoff