verify-completion — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited verify-completion (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
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.
Before stating any status, or even expressing satisfaction ("great", "perfect", "done"):
Skipping any of these steps turns a verification into a guess.
| Claim | What proves it | What does not |
|---|---|---|
| Tests pass | A fresh test run showing 0 failures | A previous run; "should pass" |
| Linter clean | Linter output, 0 errors | A partial check; extrapolating |
| Build succeeds | Build command, exit 0 | Linter passing; logs "looking good" |
| Bug fixed | The original symptom retested and gone | The code changed, so it's "probably fixed" |
| Regression test works | Watched it fail before the fix, pass after | It passes once now |
| Requirements met | A line-by-line pass over the requirements | Tests passing |
| Subagent finished | The actual diff / output inspected | The subagent reporting "success" |
A linter passing doesn't mean it compiles. A subagent saying "done" doesn't mean it did the work — check the diff. A regression test that's only ever passed hasn't been shown to catch anything; verify it fails without the fix, then passes with it.
Different phrasing doesn't exempt you — a paraphrase that implies the work is done is still a completion claim.
Run the command. Read the output. Then make the claim. There's no shortcut that preserves the honesty of the statement.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.