deliver SKILL.md skillA
deliver from domengabrovsek/agent-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add domengabrovsek/agent-config/deliver@git:20261116.b96b2bcPins git:20261116.b96b2bc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- domengabrovsek/agent-config
- Path
skills/deliver/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261116.b96b2bc, committed Nov 16, 2026
- First version recorded
- Sep 23, 2026
- Size
- 3,682 bytes
- Repository stars
- 23
- License
- none declared
Deliver a feature end to end with one human gate: you approve the spec, then the agent plans, builds tests-first, verifies against the spec, opens the PR, and drives CI and review comments until it is ready to merge.
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
# Deliver Deliver: $ARGUMENTS An orchestrator. You approve the spec. Everything after that runs without asking, except the gates listed below. The run keeps its state in `.claude/state/runs/<branch-slug>/tasks.md`, so it survives compaction and a resumed session. ## Stages **why-no-hook:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). 1. **Research**: run `/research` when the code is unfamiliar. Skip it for code already read this session `(review-time: see section note)` 2. **Spec**: run `/spec`. Discovery asks one question at a time. The spec's Open Questions must be empty before you approve it. Notify with `~/.agents/scripts/notify.sh "Spec ready for review"` `(review-time: see section note)` 3. **Set up**, after approval: `(review-time: see section note)` - Create the branch and worktree with `/worktree <slug>`, adding `--repo <path>` when the task targets another repo, and set the spec's `branch:` frontmatter `(review-time: see section note)` - Write `tasks.md` with one line per stage, and tick stages as they finish `(review-time: see section note)` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tzb6zskpioqu457z/de8538f9c9e0f33d6e6aeb1170ea4a9a5415a12548aa05bbc3b583133fafc009.json
Then /plugin install deliver@markdownregistry-tzb6zskpioqu457z in Claude Code. It installs git:20261116.b96b2bc, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add domengabrovsek/agent-config/deliver@sha256:de8538f9c9e0f33dThe line at the top of this page pins the label git:20261116.b96b2bc, 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_tzb6zskpioqu457z)
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 domengabrovsek/agent-config/deliver 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 deliver from somewhere else? Ask it: where did my deliver 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 5 versions of this file, between Sep 23, 2026 and Nov 16, 2026, about one every 14 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.b96b2bc latest | 2026-11-16 | b96b2bc | 3,682 B | A | view · diff |
| git:20261014.335cecb | 2026-10-14 | 335cecb | 3,623 B | A | view · diff |
| git:20260926.be2e930 | 2026-09-26 | be2e930 | 3,535 B | A | view · diff |
| git:20260923.48da5d0 | 2026-09-23 | 48da5d0 | 3,481 B | A | view · diff |
| git:20260923.75d78bb | 2026-09-23 | 75d78bb | 3,463 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/deliver/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 (3682 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
domengabrovsek/agent-config · 23 stars · license none declared · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tzb6zskpioqu457z GET https://markdownregistry.com/api/v1/resolve?ref=domengabrovsek/agent-config/deliver GET https://markdownregistry.com/api/v1/blob/de8538f9c9e0f33d6e6aeb1170ea4a9a5415a12548aa05bbc3b583133fafc009
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 domengabrovsek/agent-config
Every file in domengabrovsek/agent-config