verify-bug SKILL.md skillB
verify-bug from markphelps/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add markphelps/skills/verify-bug@git:20260924.c44a9c9Pins git:20260924.c44a9c9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- markphelps/skills
- Path
development/skills/verify-bug/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260924.c44a9c9, committed Sep 24, 2026
- Size
- 9,014 bytes
- Repository stars
- 6
- License
- MIT
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
# Verify bug Turn claimed bugs into verdicts you can act on. A claim is a lead, not a fact: code that looks wrong is often protected by validation in another file, a framework guarantee, a lock, a type, or configuration. And real bugs described vaguely get dismissed. This skill gives every claim a fair hearing with an advocate on each side, then records the verdict with its evidence. ## Hard rules - **Never modify the user's working tree.** Reads happen anywhere; repro tests happen only in a throwaway `git worktree` (see "Reproduction"). - **Never fix bugs, open issues, or post comments on your own.** Posting a verdict back to GitHub requires the user's explicit confirmation for that specific post. - **No verdict without receipts.** Every argument must point at code (`path:line` or `path:Symbol`). Arguments without receipts are discounted. ## Workflow 1. **Collect claims** from the source the user gave (see "Sources"). 2. **Normalize** each into a claim record (below). 3. **Dedupe:** merge claims that point at the same code path with the same trigger. Agents often report one root cause several ways; keep the clearest scenario and list the merged sources. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qgliz3szjumtpeei/169993ad5e310d889d053530ec80629daa246912e5f893c3e4756ff39cc1a0bf.json
Then /plugin install verify-bug@markdownregistry-qgliz3szjumtpeei in Claude Code. It installs git:20260924.c44a9c9, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add markphelps/skills/verify-bug@sha256:169993ad5e310d88The line at the top of this page pins the label git:20260924.c44a9c9, 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_qgliz3szjumtpeei)
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 markphelps/skills/verify-bug 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 verify-bug from somewhere else? Ask it: where did my verify-bug 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 24, 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/verify-bug/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
- fail: Frontmatter declares a description
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Size between 200 bytes and 200 KB (9014 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
markphelps/skills · 6 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qgliz3szjumtpeei GET https://markdownregistry.com/api/v1/resolve?ref=markphelps/skills/verify-bug GET https://markdownregistry.com/api/v1/blob/169993ad5e310d889d053530ec80629daa246912e5f893c3e4756ff39cc1a0bf
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.