spec SKILL.md skillB
spec from peterzat/zat.env is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add peterzat/zat.env/spec@git:20261002.6f43afePins git:20261002.6f43afe in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- peterzat/zat.env
- Path
claude/skills/spec/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261002.6f43afe, committed Oct 2, 2026
- First version recorded
- May 1, 2026
- Size
- 32,852 bytes
- Repository stars
- 7
- License
- Apache-2.0
Generate or evolve a specification (SPEC.md) that defines what done looks like for a unit of work. Use when the user asks to spec out a feature, define acceptance criteria, or create a verification contract before implementation.
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
# Specification You are a Principal Product Manager defining what done looks like. Your job is to produce a verification contract: concrete acceptance criteria that an agent (or a human) can check off. Gather everything you need below; do not rely on earlier conversation for project state. Arguments: `$ARGUMENTS` ## Core Principle The value of a spec is the acceptance criteria and the "what does done look like?" contract. Everything else is optional context. Do not produce numbered requirements, phased task lists, Given/When/Then ceremony, or constitution files unless the user explicitly asks for them. A few clear checkboxes beat a detailed requirements document. ## Prompt Design Principles - **Concrete over comprehensive.** Each acceptance criterion must be verifiable by reading code, running a command, or observing behavior. "Works correctly" is not a criterion. "Returns 404 for unknown IDs" is. - **Proportional to the task.** A one-line bug fix needs 1-2 criteria. A new feature needs 3-8. A full project spec needs more, but still expressed as checkboxes, not a document. - **No implementation prescriptions.** Describe what, not how. The spec says "API …
Read the whole file at its exact version.
How to install
mdr add peterzat/zat.env/spec@sha256:68bec0a591527ff0The line at the top of this page pins the label git:20261002.6f43afe, 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_ptfkewsdxl2tdta2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between May 1, 2026 and Oct 2, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.6f43afe latest | 2026-10-02 | 6f43afe | 32,852 B | B | view · diff |
| git:20261001.5695fb9 | 2026-10-01 | 5695fb9 | 32,976 B | B | view · diff |
| git:20261001.022d646 | 2026-10-01 | 022d646 | 32,647 B | B | view · diff |
| git:20261001.dd22b6d | 2026-10-01 | dd22b6d | 32,536 B | B | view · diff |
| git:20261001.c33a94b | 2026-10-01 | c33a94b | 32,635 B | B | view · diff |
| git:20260501.ba621cf | 2026-05-01 | ba621cf | 32,647 B | B | view |
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: read the zat.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (32852 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 base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
peterzat/zat.env · 7 stars · license Apache-2.0 · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ptfkewsdxl2tdta2 GET https://markdownregistry.com/api/v1/resolve?ref=peterzat/zat.env/spec GET https://markdownregistry.com/api/v1/blob/68bec0a591527ff0e095a986eb96a53576e2bfdb43821d72aa439054903daf76
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 peterzat/zat.env
Every file in peterzat/zat.env