spec SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
spec from korya/avocetta is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add korya/avocetta/spec@git:20260902.1f9ccb7Pins git:20260902.1f9ccb7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- korya/avocetta
- Path
test/fixtures/real/swd-mini/skills/spec/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260902.1f9ccb7, committed Sep 2, 2026
- Size
- 4,686 bytes
- Repository stars
- 2
- License
- MIT
Turn a fuzzy feature request into a reviewable product spec — goals, non-goals, testable acceptance criteria with stable IDs, invariants — that later skills cite by path and ID. Use when the user says "/spec", "spec this out", "write a product spec", "turn this idea into requirements", or brings a feature request that needs a contract before planning or building.
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: the contract everything else cites The point is a document later work can be *checked against*: `/blueprint` cross-validates its plan with it, `/e2e-test` derives cases from its criteria, `/revise` uses it as the scope fence. That only works if the spec is product-level, testable, and stably addressable — which is what this skill enforces. `/spec` says what and why; how belongs to `/blueprint`. ## Principles - **WHAT and WHY, never HOW.** Everything is stated in user-observable terms. Litmus: two different implementations should both be able to satisfy the spec. Technical constraints appear only when they are genuine product constraints (compliance, platform), not design preferences. - **Testable or it isn't a criterion.** Each acceptance criterion is a concrete scenario with an observable outcome — something an end-to-end test could execute black-box. "The feature should be fast/intuitive/robust" is a goal at best, never a criterion. - **Stable IDs, append-only.** Criteria carry IDs that later skills cite; IDs are never renumbered or reused, and deletions leave holes. See `references/format.md`. …
Read the whole file at its exact version.
How to install
mdr add korya/avocetta/spec@sha256:6cf8c8e87bccf3bcThe line at the top of this page pins the label git:20260902.1f9ccb7, 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_3ghbihfbkl4k2n53)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 2, 2026.
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 (4686 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
korya/avocetta · 2 stars · license MIT · pushed 2026-10-31 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_3ghbihfbkl4k2n53 GET https://markdownregistry.com/api/v1/resolve?ref=korya/avocetta/spec GET https://markdownregistry.com/api/v1/blob/6cf8c8e87bccf3bcd224d5eee81af4b15e340abae9ee3e1dfaa2cbc2d11d1df2
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.