verification-before-completion
No security findings. Scanned 1 time, most recently 2026-02-08.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
- Package
- 1 file, 4.1 KB
- SKILL.md
- 630 words, 11 sections
- Code
- None. Instructions only.
SKILL.md covers: Verification Before Completion · Overview · The Iron Law · The Gate Function · Common Failures · Red Flags - STOP · Rationalization Prevention · Key Patterns · Why This Matters · When To Apply · The Bottom Line
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 4.1 KB |
Package contents recorded 2026-10-22 at commit 06b92f36820f. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Llm analyzer. A language model reads the skill and reports intent-level issues the rules cannot express.
- Meta analyzer. A second model pass that validates, deduplicates and re-scores the other analyzers' findings.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/obra/superpowers
- Raw scan result: verification-before-completion-scan.json
- Badge for your README:
- Request a re-scan