implementation-tdd SKILL.md skillA
implementation-tdd from vraj-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vraj-ai/skills/implementation-tdd@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vraj-ai/skills
- Path
pipeline/implementation-tdd/SKILL.md- Versions recorded
- 4
- Latest version
- v1.1.0, committed Oct 14, 2026
- First version recorded
- Sep 5, 2026
- Size
- 8,603 bytes
- Repository stars
- 3
- License
- MIT
Strict one-ticket TDD for implementation work — write the failing test first at the real production seam, lock the Verification-command before editing, drive red-green at the highest meaningful seam production traffic actually uses, and prove the fix and the provider failure modes (duplicate and out-of-order delivery, replay, partial failure, forged payloads, wrong-tenant access) rather than assuming them. Use when implementing a Coding ticket, and whenever the change touches an external…
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
# implementation-tdd One ticket. Gate first. Real seams. The tests that matter are the ones that fail for the reason production would. Plain logic bugs are the easy half. Anything crossing a network fails in ways a unit test of your own code never surfaces: the same event arrives twice, out of order, forged, or three days late. Both halves run through the same loop below. ## Step 1 — Lock the gate BEFORE editing Take the ticket's `Verification-command` verbatim. Then: 1. **Run it before any change.** You need to know whether it was already green, already red, or doesn't run at all. 2. If it doesn't run (missing harness, wrong path, no such script) — that's a **ticket defect**. Fix the command with the user's agreement *before* treating it as the done-definition, and note the correction on the ticket. 3. If the ticket has no command, derive one and get it agreed. Do not invent a private definition of done. Once locked, the gate does not move to accommodate your implementation. If the gate is wrong, you change it deliberately and say so — you never quietly relax it. ## Step 2 — Red at the highest meaningful seam …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_vgk5fi2qdryaduq2/6690091b8f160de89d40f74836c94fc3179677ad7d3c0cdd7e55772f98b0b59d.json
Then /plugin install implementation-tdd@markdownregistry-vgk5fi2qdryaduq2 in Claude Code. It installs v1.1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vraj-ai/skills/implementation-tdd@sha256:6690091b8f160de8The line at the top of this page pins the label v1.1.0, 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_vgk5fi2qdryaduq2)
5 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 vraj-ai/skills/implementation-tdd 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 implementation-tdd from somewhere else? Ask it: where did my implementation-tdd 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 4 versions of this file, between Sep 5, 2026 and Oct 14, 2026, about one every 13 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-10-14 | 6cb60ee | 8,603 B | A | view · diff |
| v1.0.0 | 2026-10-14 | 6bd9b35 | 8,603 B | A | view · diff |
| v1.0.0 | 2026-09-05 | 6047076 | 8,533 B | A | view · diff |
| v1.0.0 | 2026-09-05 | 0ec0145 | 8,582 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/implementation-tdd/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 (8603 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
vraj-ai/skills · 3 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vgk5fi2qdryaduq2 GET https://markdownregistry.com/api/v1/resolve?ref=vraj-ai/skills/implementation-tdd GET https://markdownregistry.com/api/v1/blob/6690091b8f160de89d40f74836c94fc3179677ad7d3c0cdd7e55772f98b0b59d
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.