spec SKILL.md skillA
spec from strands-agents/box is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add strands-agents/box/spec@git:20261007.158dadePins git:20261007.158dade in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- strands-agents/box
- Path
.agents/skills/spec/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261007.158dade, committed Oct 7, 2026
- Size
- 16,555 bytes
- Repository stars
- 548
- License
- Apache-2.0
Walk through spec-driven development, design then requirements, producing a local .spec.md and .requirements.md for one feature. Both files are local working material and are never committed. Use when planning a feature before building it.
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
# Spec Skill
Walk a feature through **spec-driven development**: two phases, each with a user approval gate.
```
Design ──[approve]──> Requirements ──[approve]──> build
```
**A spec is local working material, and it is never committed or promoted.** It guides one piece
of work while that work is being built. When the work lands, the spec has done its job:
| What the spec held | Where it goes when the work lands |
|---|---|
| Behaviour and its contract | The code and its tests. A test is the durable form of an acceptance criterion. |
| A decision someone would later ask "why" about | One entry in `docs/design/decisions.md`, through `/kd`, once the user decides it. |
| Everything else: options, task lists, open questions, history | Nowhere. It stays in the local draft. |
`docs/design/` pages are written for a reader who was not in the discussion. Write one fresh
from the code when one is needed. **Never copy or adapt a spec into one.**
**When implementing a feature, strictly honour its spec.** The design (`.spec.md`) defines the
architecture and the decisions, and the requirements define testable behaviour.
## Skill Invocation
`/spec {area}/{feature}`
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_63avkj5kcs3d5gan/0b16fd53f9eda230aee402f90e2df76836b8a590a229c740d08e11eb8db7f043.json
Then /plugin install spec@markdownregistry-63avkj5kcs3d5gan in Claude Code. It installs git:20261007.158dade, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add strands-agents/box/spec@sha256:0b16fd53f9eda230The line at the top of this page pins the label git:20261007.158dade, 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_63avkj5kcs3d5gan)
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 strands-agents/box/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 spec from somewhere else? Ask it: where did my 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 1 version of this file, committed on Oct 7, 2026.
Watch this file (sign in, one email per new version)
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/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 (16555 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
strands-agents/box · 548 stars · license Apache-2.0 · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_63avkj5kcs3d5gan GET https://markdownregistry.com/api/v1/resolve?ref=strands-agents/box/spec GET https://markdownregistry.com/api/v1/blob/0b16fd53f9eda230aee402f90e2df76836b8a590a229c740d08e11eb8db7f043
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 strands-agents/box
Every file in strands-agents/box
Other files named spec
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.