workflow SKILL.md skillA
workflow 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/workflow@git:20261008.f553434Pins git:20261008.f553434 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- abdurrafay2004/handoff
- Path
skills/workflow/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261008.f553434, committed Oct 8, 2026
- First version recorded
- Jul 10, 2026
- Size
- 7,827 bytes
- Repository stars
- 5
- License
- MIT
The operating pipeline for all development work — 6 phases (Brief, Plan, Build, Verify, Ship, Learn) with risk tiers that decide how much process a task gets. Use at the start of any development task to pick the tier and execution mode, when unsure whether a task needs a plan/tests/review, or when another skill needs the phase and tier vocabulary. This skill overrides any process embedded in other skills.
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
# Workflow One pipeline for every project. The user is the product manager and architect: they decide **what** and **why**, and judge results as evidence — working demos, test output, preview URLs — never raw code. The agent is the senior engineer and devops: it proposes, builds, verifies, ships, and always brings evidence to the gate. ## Host compatibility Use the tools and skills actually available in the current host. Named tools and slash commands below are examples, not required APIs. In Codex, ask with `request_user_input` when available in Plan mode, an asynchronous question tool when available, or a short chat question. Never change modes just to ask. Review with the available review capability or a direct diff review; use `security` for security review when `/security-review` is unavailable. Run project checks with the host's shell tool and browser QA with its browser tools. Use the host's goal/automation features only when requested and available; don't assume `/loop` or `schedule` exists. Host and user instructions take precedence, including authorization already given in the conversation. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3fjvkxs3k6d6x5bh/74349f6648b07be2a43e7915385bc1abbf7538059e11fe62997c42f7615912ce.json
Then /plugin install workflow@markdownregistry-3fjvkxs3k6d6x5bh in Claude Code. It installs git:20261008.f553434, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add abdurrafay2004/handoff/workflow@sha256:74349f6648b07be2The line at the top of this page pins the label git:20261008.f553434, 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_3fjvkxs3k6d6x5bh)
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/workflow 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 workflow from somewhere else? Ask it: where did my workflow 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 10, 2026 and Oct 8, 2026, about one every 22 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.f553434 latest | 2026-10-08 | f553434 | 7,827 B | A | view · diff |
| git:20261008.0e07558 | 2026-10-08 | 0e07558 | 6,095 B | A | view · diff |
| git:20260711.bfd3a58 | 2026-07-11 | bfd3a58 | 5,271 B | A | view · diff |
| git:20260711.46a3400 | 2026-07-11 | 46a3400 | 5,277 B | A | view · diff |
| git:20260710.678ecc7 | 2026-07-10 | 678ecc7 | 5,386 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/workflow/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 (7827 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_3fjvkxs3k6d6x5bh GET https://markdownregistry.com/api/v1/resolve?ref=abdurrafay2004/handoff/workflow GET https://markdownregistry.com/api/v1/blob/74349f6648b07be2a43e7915385bc1abbf7538059e11fe62997c42f7615912ce
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