verify-completion SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
verify-completion from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add khaledsaeed18/dotclaude/verify-completion@git:20260921.3a2f779Pins git:20260921.3a2f779 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- khaledsaeed18/dotclaude
- Path
skills/engineering/verify-completion/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260921.3a2f779, committed Sep 21, 2026
- First version recorded
- Jun 9, 2026
- Size
- 3,406 bytes
- Repository stars
- 5
- License
- MIT
Gate every "it works / it's fixed / tests pass / done" claim behind fresh evidence. Run the actual verifying command, read its output, and only then state the result. Use before committing, opening a PR, marking a task complete, handing off to or trusting a subagent, or otherwise asserting that work succeeded.
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
Don't claim work is done, fixed, or passing unless you've just run the thing that proves it and read the output. Saying it's complete when you haven't checked isn't optimism; it's reporting something you don't know to be true, and it breaks trust the moment it turns out wrong.
## The one rule
**No completion claim without fresh verification.** If you haven't run the verifying command in this turn, you can't say it passes. "Should pass now", "I'm confident", "the logs looked fine" are not evidence; they're the feelings that precede unverified claims.
## The gate
Before stating any status, or even expressing satisfaction ("great", "perfect", "done"):
1. **Identify** the command that would prove the claim.
2. **Run** it: the full command, fresh, start to finish. Not a partial check, not a remembered result from earlier.
3. **Read** the whole output: exit code, failure count, warnings.
4. **Decide.** Does the output actually confirm the claim? If not, state the real status with the evidence. If so, state the claim *with* the evidence.
Skipping any of these steps turns a verification into a guess.
## What each claim actually requires
| Claim | What proves it | What does *not* |
…Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/verify-completion@sha256:a6ffb838e7b5cb45The line at the top of this page pins the label git:20260921.3a2f779, 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_hjqxdtwsw4fnfids)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 9, 2026 and Sep 21, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.3a2f779 latest | 2026-09-21 | 3a2f779 | 3,406 B | A | view · diff |
| git:20260921.6c17ffd | 2026-09-21 | 6c17ffd | 3,107 B | A | view · diff |
| git:20260921.36d6832 | 2026-09-21 | 36d6832 | 3,125 B | A | view · diff |
| git:20260609.13bdd5a | 2026-06-09 | 13bdd5a | 3,128 B | A | view |
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 (3406 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
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hjqxdtwsw4fnfids GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/verify-completion GET https://markdownregistry.com/api/v1/blob/a6ffb838e7b5cb45ad7b6522acd6eeee48e8788c1d2ccbe53b8520bfca1ec8c5
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 khaledsaeed18/dotclaude
Every file in khaledsaeed18/dotclaude