engineering-standards SKILL.md skillA
engineering-standards 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/engineering-standards@git:20260922.205b151Pins git:20260922.205b151 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/engineering-standards/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260922.205b151, committed Sep 22, 2026
- Size
- 7,404 bytes
- Repository stars
- 6
- License
- MIT
The one standard both the coding work and the reviewers work from: architecture, failure handling, security, scalability, performance, naming, data and migrations, behaviour analytics, and tests. Also defines review scope (the diff plus the code around it) and the one-pass discipline. Load it before writing code and before reviewing any, so what is written and what is judged come from the same list.
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
# Engineering standard One base for writing and for judging. Before this existed, each skill carried its own idea of what good looks like, so code was written against one list and marked against another, and the gap arrived as review findings the author had no way to avoid. Where a repository's own `CLAUDE.md` or `AGENTS.md` is more specific, the repository wins and this fills the gaps. ## 1. Architecture - Logic belongs in the layer that owns it: transport handles transport, services orchestrate, domain code holds the rules, and data access stays in the data layer. Business logic in a controller or a repository is a finding, not a shortcut. - Mirror a sibling module before inventing a shape. Two ways of doing the same thing in one codebase cost more than either way costs alone. - Shared contracts stay in step across repositories. A change to a shared schema ripples to every consumer, and the clients have to agree on names and payloads. - New public surface is a decision, not a detail: name it once, and expect to live with the name. ## 2. Failure handling (always on) Every failure mode is handled on purpose. A "nothing happened" path an operator …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rx4f3gezuc4irrhc/ba4264c66ca0f55080fda67d0b330e4bba7b2370108f4d4573393949a1c3ffd5.json
Then /plugin install engineering-standards@markdownregistry-rx4f3gezuc4irrhc in Claude Code. It installs git:20260922.205b151, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kulykivska/claude-plugins/engineering-standards@sha256:ba4264c66ca0f550The line at the top of this page pins the label git:20260922.205b151, 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_rx4f3gezuc4irrhc)
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 kulykivska/claude-plugins/engineering-standards 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 engineering-standards from somewhere else? Ask it: where did my engineering-standards 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 Sep 22, 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/engineering-standards/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 (7404 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_rx4f3gezuc4irrhc GET https://markdownregistry.com/api/v1/resolve?ref=kulykivska/claude-plugins/engineering-standards GET https://markdownregistry.com/api/v1/blob/ba4264c66ca0f55080fda67d0b330e4bba7b2370108f4d4573393949a1c3ffd5
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