to-spec SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 13 indexed copies. Same content hash, so the same checks give both the same grade.
to-spec from mattpocock/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mattpocock/skills/to-spec@git:20260819.5c89081Pins git:20260819.5c89081 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mattpocock/skills
- Path
skills/engineering/to-spec/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260819.5c89081, committed Aug 19, 2026
- First version recorded
- Aug 15, 2026
- Size
- 3,043 bytes
- Repository stars
- 327,521
- License
- MIT
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
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
This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know. The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`. ## Process 1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching. 2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one. Check with the user that these seams match their expectations. 3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage. <spec-template> ## Problem Statement The problem that the user is facing, from the user's perspective. ## Solution …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_z2cj2jidsxk4ageb/43ad9cf318e5e7d3d1fa360253a37021796dc87a0c2e595ad262661a10f85088.json
Then /plugin install to-spec@markdownregistry-z2cj2jidsxk4ageb in Claude Code. It installs git:20260819.5c89081, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mattpocock/skills/to-spec@sha256:43ad9cf318e5e7d3The line at the top of this page pins the label git:20260819.5c89081, 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_z2cj2jidsxk4ageb)
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 mattpocock/skills/to-spec 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 to-spec from somewhere else? Ask it: where did my to-spec 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 Aug 15, 2026 and Aug 19, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260819.5c89081 latest | 2026-08-19 | 5c89081 | 3,043 B | A | view · diff |
| git:20260819.3216582 | 2026-08-19 | 3216582 | 3,041 B | A | view · diff |
| git:20260815.6a34259 | 2026-08-15 | 6a34259 | 3,050 B | A | view · diff |
| git:20260815.1dab982 | 2026-08-15 | 1dab982 | 3,103 B | A | view · diff |
| git:20260815.fcf0071 | 2026-08-15 | fcf0071 | 3,055 B | A | view |
Copies
11 files in 10 other repositories hold the exact bytes of one of this file's versions, each committed after this file had them: all of them hold the newest version.
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
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/to-spec/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 (3043 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
mattpocock/skills · 327,521 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z2cj2jidsxk4ageb GET https://markdownregistry.com/api/v1/resolve?ref=mattpocock/skills/to-spec GET https://markdownregistry.com/api/v1/blob/43ad9cf318e5e7d3d1fa360253a37021796dc87a0c2e595ad262661a10f85088
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 mattpocock/skills
Every file in mattpocock/skills