setup SKILL.md skillA
setup 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/setup@git:20261116.574db06Pins git:20261116.574db06 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- abdurrafay2004/handoff
- Path
skills/setup/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261116.574db06, committed Nov 16, 2026
- First version recorded
- Jul 2, 2026
- Size
- 6,863 bytes
- Repository stars
- 5
- License
- MIT
Scaffold the handoff project-memory system into THIS repository (new or existing) — copies the template tree into .handoff/, then runs a guided discovery pass that drafts a real STATUS, MAP, TECH_STACK, and PRODUCT from the actual codebase and confirms with the user before saving. Use when the user says "set up handoff", "initialize handoff", "add project memory", or when a repo has no .handoff/ and the user wants one. Run once per repo. Also runs the read-only drift check when the user says…
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
# Set up handoff in this repo
Scaffold the durable project-memory system, then populate it from the real
codebase so it ships useful — not blank. **Discovery drafts; the user confirms
before anything is saved.** Never invent project facts (RULES rule 5).
## 0. Locate templates & detect existing install
- The template tree is bundled with this plugin at `../../templates/` relative
to this skill file (i.e. `<plugin-root>/templates/`). Resolve that absolute path.
- Check whether `.handoff/` already exists in the project root:
- **Exists** → do NOT overwrite. Tell the user it's already set up; offer to
*refresh* specific files (e.g. re-run discovery for STATUS/MAP/TECH_STACK),
seed a CONTEXT.md, or run the drift check (section 7). Stop here unless
they choose one.
- **Absent** → continue.
## 1. Copy the template tree
Copy the bundled `templates/` into the project as `.handoff/`, preserving
structure (BOOT, RULES, STATUS, MAP, CHANGELOG, context/, docs/ with
SKILL-WORKFLOW.md, tasks/ with inbox/now/done). Keep the `.gitkeep` files.
Do not edit RULES' universal section.
Write the current plugin version into `.handoff/VERSION` (single line) — the
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_wujxop25yha3ztjc/1f80d55bd5638a1b0eabb6c995d8a1d3bee21c38acf6a8881bc1163f457a7704.json
Then /plugin install setup@markdownregistry-wujxop25yha3ztjc in Claude Code. It installs git:20261116.574db06, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add abdurrafay2004/handoff/setup@sha256:1f80d55bd5638a1bThe line at the top of this page pins the label git:20261116.574db06, 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_wujxop25yha3ztjc)
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/setup 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 setup from somewhere else? Ask it: where did my setup 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 Nov 16, 2026, about one every 34 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.574db06 latest | 2026-11-16 | 574db06 | 6,863 B | A | view · diff |
| git:20261008.0e07558 | 2026-10-08 | 0e07558 | 5,832 B | A | view · diff |
| git:20260711.bfd3a58 | 2026-07-11 | bfd3a58 | 5,060 B | A | view · diff |
| git:20260702.0ea7c43 | 2026-07-02 | 0ea7c43 | 5,114 B | A | view · diff |
| git:20260702.3e0422e | 2026-07-02 | 3e0422e | 4,779 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/setup/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 (6863 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_wujxop25yha3ztjc GET https://markdownregistry.com/api/v1/resolve?ref=abdurrafay2004/handoff/setup GET https://markdownregistry.com/api/v1/blob/1f80d55bd5638a1b0eabb6c995d8a1d3bee21c38acf6a8881bc1163f457a7704
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