principle-bounded-repair SKILL.md skillA
principle-bounded-repair 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/principle-bounded-repair@v1.0.0Pins v1.0.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
principles/principle-bounded-repair/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 14, 2026
- Size
- 1,929 bytes
- Repository stars
- 3
- License
- MIT
Bound every repair loop — retrying an identical failure the same way burns budget without generating information. Set a repair budget before fixing, change the hypothesis or the observation when a retry fails the same way twice, and escalate to a blocker report when the budget expires instead of weakening acceptance. Apply during any fix loop, CI-chasing, or repeated verification failure.
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
# Principle: bounded repair Retrying an identical failure is not persistence. It is a loop with no exit condition. ## The rule Before the first fix attempt, state the repair budget: how many rounds, what counts as a round, and what happens when it expires. The pipeline default is three rounds per issue unless the work states otherwise. A round only counts if it produces new information: a different failure, a narrowed reproduction, a changed hypothesis. Two consecutive rounds emitting identical output mean the loop is not learning — change the hypothesis or the observation method, or stop. ## When the budget expires Report the blocker instead of weakening acceptance. An expired budget yields: - What was tried, with the round each attempt happened on. - The failure as it currently stands, verbatim where it matters. - The hypothesis that remains untested and why. - What unblocks it: a decision, an authority grant, an environment fix. Do not lower the gate to match the diff. Do not reframe "cannot verify" as "verified enough." A blocker stated cleanly is a successful outcome of a bounded loop; an unverifiable "fix" is not. ## What does not count as repair …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5sb25etqwfqdbvub/235644f15be55051c57aa99b34bf5a3c4a4160769905bb3d95fe0fefb93e48b4.json
Then /plugin install principle-bounded-repair@markdownregistry-5sb25etqwfqdbvub in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vraj-ai/skills/principle-bounded-repair@sha256:235644f15be55051The line at the top of this page pins the label v1.0.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_5sb25etqwfqdbvub)
4 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/principle-bounded-repair 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 principle-bounded-repair from somewhere else? Ask it: where did my principle-bounded-repair 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 Oct 14, 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/principle-bounded-repair/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 (1929 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_5sb25etqwfqdbvub GET https://markdownregistry.com/api/v1/resolve?ref=vraj-ai/skills/principle-bounded-repair GET https://markdownregistry.com/api/v1/blob/235644f15be55051c57aa99b34bf5a3c4a4160769905bb3d95fe0fefb93e48b4
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.