requirements SKILL.md skillA
requirements from kulykivska/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kulykivska/claude-plugins/requirements@git:20260922.a4bd47bPins git:20260922.a4bd47b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kulykivska/claude-plugins
- Path
sdlc/skills/requirements/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260922.a4bd47b, committed Sep 22, 2026
- First version recorded
- Jul 11, 2026
- Size
- 1,354 bytes
- Repository stars
- 6
- License
- MIT
Turn a raw (often dictated) idea into concrete requirements before coding. Trigger on "let us build...", "I want a feature...", "add a feature", or any substantial new-feature request where scope is fuzzy. Produces user-visible behavior, edge cases, acceptance criteria, and a consistency check against the existing app.
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
# Requirements Turn an idea into something implementable without back-and-forth later. ## Steps 1. **Restate the goal** in one sentence: who gets what value. 2. **Concretize behavior**: for each user-visible surface (web, iOS, API, voice), what exactly does the user see/do? Free vs paid tier treatment (default policy: free = teaser, paid = everything). 3. **Edge cases**: empty data, first-time user, offline/failed upstream, locale (en/uk/es where the app is localized), mobile layout. 4. **Consistency check**: grep the codebase for adjacent features; flag anything the new behavior would contradict (naming, gating, i18n, existing endpoints). List conflicts explicitly. 5. **Acceptance criteria**: a short checklist that QA (the `qa` skill) can execute verbatim. 6. Keep it tight: one screen of output. If a decision is genuinely the owner's (pricing, tier gating changes, external services), ask; otherwise pick the sensible default and note it.
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lhx76s64cpb5aghp/bb8d4b1c1bad45a5450abca33e2a2a4de8c8fb958937699df07a2c98534c806b.json
Then /plugin install requirements@markdownregistry-lhx76s64cpb5aghp in Claude Code. It installs git:20260922.a4bd47b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kulykivska/claude-plugins/requirements@sha256:bb8d4b1c1bad45a5The line at the top of this page pins the label git:20260922.a4bd47b, 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_lhx76s64cpb5aghp)
1 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 kulykivska/claude-plugins/requirements 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 requirements from somewhere else? Ask it: where did my requirements 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 Jul 11, 2026 and Sep 22, 2026, about one every 72 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.a4bd47b latest | 2026-09-22 | a4bd47b | 1,354 B | A | view · diff |
| git:20260711.696597d | 2026-07-11 | 696597d | 1,368 B | A | 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/requirements/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 (1354 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
kulykivska/claude-plugins · 6 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lhx76s64cpb5aghp GET https://markdownregistry.com/api/v1/resolve?ref=kulykivska/claude-plugins/requirements GET https://markdownregistry.com/api/v1/blob/bb8d4b1c1bad45a5450abca33e2a2a4de8c8fb958937699df07a2c98534c806b
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 kulykivska/claude-plugins
Every file in kulykivska/claude-plugins