Verify claims by executing, not asserting, before declaring work done. TRIGGER when: about to report a task complete, confirming a fix/build/deploy works, or delegating work to another agent or tool. SKIP: scoring research/plan quality pre-implementation (use quality-validation); deciding test coverage strategy (use testing-strategy).
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
# Verification Before Completion Skill
## Purpose
A claim of "done" is only as good as the check that produced it. This skill
encodes the rule that every completion claim, and every fact a claim depends on,
must be backed by something actually executed and observed — not assumed,
remembered, or guessed — before it is reported.
## When to Apply
Apply this skill when:
- About to report a task, fix, or feature as complete
- Confirming that a build, test, deploy, or query actually succeeded
- Stating a fact about a file, branch, or config that the response depends on
- Delegating a task to another agent or tool
Do NOT apply this skill for:
- Scoring a ResearchPack or Implementation Plan against quality gates before work starts — use `quality-validation`
- Deciding what and how much to test — use `testing-strategy`
---
## Verification Rules
| Rule | Requirement |
|------|-------------|
| Prove before claiming | Run the actual command that demonstrates the outcome (test suite, build, the real query) and read its output. Exit code 0 alone is not proof of correctness — check the output content. |
…
The line at the top of this page pins the label git:20260921.9cd7bef, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4565 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
GitHub
komluk/scaffolding · 16 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cj4nsa3zddrinvfq
GET https://markdownregistry.com/api/v1/resolve?ref=komluk/scaffolding/verification-before-completion
GET https://markdownregistry.com/api/v1/blob/141808edc10749b7d9fc60f03a97bcb874add2d8ac4d6d4e621794a92c4841c7
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.
komluk/scaffolding · skills/frontend-design/SKILL.md · Distinctive, non-generic visual identity for new landing pages and public-facing UI. TRIGGER when: designing a new…
komluk/scaffolding · skills/github-actions-template/SKILL.md · GitHub Actions CI pipeline templates and workflow YAML patterns. TRIGGER when: creating or editing a CI workflow…
obra/superpowers · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs
mvschwarz/openrig · skills/_canonical/process/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs
a5c-ai/babysitter · library/methodologies/superpowers/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Evidence before…
a5c-ai/babysitter · library/methodologies/cc10x/skills/verification-before-completion/SKILL.md · Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success…
ganyuanran/aegis · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish…
coco-research/coco · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
