delivery-constraints SKILL.md skillA
delivery-constraints from vraj-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vraj-ai/skills/delivery-constraints@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vraj-ai/skills
- Path
pipeline/delivery-constraints/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.0, committed Oct 14, 2026
- First version recorded
- Sep 5, 2026
- Size
- 9,255 bytes
- Repository stars
- 3
- License
- MIT
Deliver a ticket whose delivery path is decided by something other than the code — a token/spend cap, a live data migration, restricted git authority, an unwritable tracker, or a pipeline state that is lying about progress. Use when budget is capped, when a change touches production data or costs money to run, when push/PR authority is restricted, when tracker writes are unavailable and work must hand off through a file, or when the tracker says implementing but nothing landed and retrying…
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
# Delivery constraints Normal ticket work assumes a normal environment: full authority, a writable tracker, an honest state machine, and budget to spare. This skill is for when one of those assumptions is false — when the constraint, not the code, decides how the work ships or whether it can ship at all. A missing authority and a lying pipeline state are the same class of problem: an external fact that invalidates the obvious path. Both are handled by naming the fact first, then choosing a path that respects it. This skill composes three principles: principle-named-constraints (step 1), principle-evidence-over-report (step 2), and principle-bounded-repair (the repair budget). The detail below is the application; the principles hold everywhere else too. ## Step 1 — Name the constraints explicitly Write them down before starting. An unnamed constraint gets violated. | Constraint | Questions to answer now | |---|---| | **Budget** | Token/spend cap? What is already burned? What happens at the cap — stop, or degrade? | | **Spend authority** | Does this run call paid providers, deploy, or purchase? Spend is **always separately authorized.** | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_w5nhfufc73rvcq57/973dded96499b8becfa914be8c459ad322718dc689b371161c404a65dd7ad814.json
Then /plugin install delivery-constraints@markdownregistry-w5nhfufc73rvcq57 in Claude Code. It installs v1.1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vraj-ai/skills/delivery-constraints@sha256:973dded96499b8beThe line at the top of this page pins the label v1.1.0, 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_w5nhfufc73rvcq57)
5 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 vraj-ai/skills/delivery-constraints 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 delivery-constraints from somewhere else? Ask it: where did my delivery-constraints 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 5, 2026 and Oct 14, 2026, about one every 10 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-10-14 | 6cb60ee | 9,255 B | A | view · diff |
| v1.0.0 | 2026-10-14 | 6bd9b35 | 9,255 B | A | view · diff |
| v1.0.0 | 2026-09-05 | cab4674 | 8,963 B | A | view · diff |
| v1.0.0 | 2026-09-05 | 6047076 | 8,678 B | A | view · diff |
| v1.0.0 | 2026-09-05 | fcbc5cc | 8,768 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/delivery-constraints/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 (9255 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
vraj-ai/skills · 3 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w5nhfufc73rvcq57 GET https://markdownregistry.com/api/v1/resolve?ref=vraj-ai/skills/delivery-constraints GET https://markdownregistry.com/api/v1/blob/973dded96499b8becfa914be8c459ad322718dc689b371161c404a65dd7ad814
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.