feature SKILL.md skillC
feature from snowflake-labs/coco-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add snowflake-labs/coco-skills/feature@git:20260708.b732ce1Pins git:20260708.b732ce1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- C, 14 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- snowflake-labs/coco-skills
- Path
skills/spec-driven/feature/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260708.b732ce1, committed Jul 8, 2026
- First version recorded
- Jun 9, 2026
- Size
- 8,544 bytes
- Repository stars
- 55
- License
- none declared
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
# Feature Spec Sub-Skill
Create comprehensive specifications for new features following structured SDLC phases.
## CRITICAL RULE: One Phase at a Time
Even if the user asks for all deliverables at once ("give me requirements, design, and tasks"), produce ONLY the current phase's output, stop for approval, then proceed to the next phase. NEVER create files belonging to later phases before the current phase is approved.
- Phase 2 creates `requirements.md` only — do NOT create `design.md` or `tasks.md`
- Phase 3 creates `design.md` only — do NOT create `tasks.md`
- Phase 4 creates `tasks.md` and begins implementation
If the user requests all files at once, acknowledge the request and explain: "I'll produce these one phase at a time so you can review and approve each before I proceed."
## Workflow
### PHASE 1: CLARIFY
**Objective**: Gather complete requirements through structured questions.
**Questions to Ask** (adapt based on context):
1. **User Story**: Who is this for and what do they need?
- "As a [role], I want [capability] so that [benefit]"
2. **Scope**: What's included and excluded?
- Core functionality (must have)
- Nice-to-have (if time permits)
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_r3yczvuhro4heqmu/0b0811673e4154eaeae595612f4cd20e9672f8bdb537e5713d3b7a2a930b6d01.json
Then /plugin install feature@markdownregistry-r3yczvuhro4heqmu in Claude Code. It installs git:20260708.b732ce1, the one graded C here, pinned to the commit it was graded at, and leaves it there.
mdr add snowflake-labs/coco-skills/feature@sha256:0b0811673e4154eaThe line at the top of this page pins the label git:20260708.b732ce1, 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_r3yczvuhro4heqmu)
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 snowflake-labs/coco-skills/feature 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 feature from somewhere else? Ask it: where did my feature 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 2 versions of this file, between Jun 9, 2026 and Jul 8, 2026, about one every 29 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260708.b732ce1 latest | 2026-07-08 | b732ce1 | 8,544 B | C | view · diff |
| git:20260609.c696be1 | 2026-06-09 | c696be1 | 8,543 B | C | 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/feature/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
- fail: Frontmatter block present
- fail: Frontmatter declares a name
- fail: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8544 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
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
snowflake-labs/coco-skills · 55 stars · license none declared · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r3yczvuhro4heqmu GET https://markdownregistry.com/api/v1/resolve?ref=snowflake-labs/coco-skills/feature GET https://markdownregistry.com/api/v1/blob/0b0811673e4154eaeae595612f4cd20e9672f8bdb537e5713d3b7a2a930b6d01
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 snowflake-labs/coco-skills
Every file in snowflake-labs/coco-skills