completion-verification SKILL.md skillA
completion-verification from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/completion-verification@git:20260828.f80dcb5Pins git:20260828.f80dcb5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/technology/skills/completion-verification/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260828.f80dcb5, committed Aug 28, 2026
- Size
- 1,921 bytes
- Repository stars
- 2,543
- License
- MIT
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.
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
# Completion verification The gap between "should work" and "does work" is where most wasted cycles live. This closes it. ## Before claiming done 1. **Run the real check**, not a subset. The command the project gates on, on the current state of the tree. 2. **Read the output.** An exit code of zero with skipped tests, or a build with new warnings, is not what it looks like at a glance. 3. **Re-read the original request.** Not your interpretation of it several steps ago — the actual words. Confirm each part was addressed, and name any part that was not. 4. **Check for collateral damage.** What else consumes what you changed? Did anything else move? 5. **Confirm nothing was left behind** — debug statements, a skipped test, a TODO standing in for the hard case. ## What a claim must carry Say what you ran and what it said. "Tests pass" is an assertion; the command and its output is evidence. If you could not run something, say that explicitly rather than omitting it — an unstated gap reads as a covered one. ## Honest incompleteness Partial work reported accurately is useful. Partial work reported as complete costs someone else the …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/completion-verification@sha256:3310045bae2daf74The line at the top of this page pins the label git:20260828.f80dcb5, 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_auqa5bfi7rzydsmw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 28, 2026.
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 (1921 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_auqa5bfi7rzydsmw GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/completion-verification GET https://markdownregistry.com/api/v1/blob/3310045bae2daf74ffcd479f49657b3ffb5d0cd04bde973bf060cf0ba115de1e
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 cbrock84/headcount
Every file in cbrock84/headcount