verification-before-completion
Enforces evidence-based completion claims. Use before claiming work is done, tests pass, or bugs are fixed. Requires running verification commands and confirming output before any success claims.
- Installs
- 39
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/delphine-l/claude_global --skill verification-before-completion- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads verification-before-completion automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Verification Before Completion
Overview
Core principle: Evidence before claims, always.
The Gate
BEFORE claiming any status:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the command (fresh, complete)
3. READ: Full output, check exit code
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Common Failures
| Claim | Requires | Not Sufficient |
|---|---|---|
| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check |
| Build succeeds | Build command: exit 0 | "Looks good" |
| Bug fixed | Original symptom: gone | Code changed, assumed fixed |
| Pipeline complete | Output files exist and are valid | Tool reported success |
| Notebook runs | All cells executed without error | Some cells ran |
Red Flags — STOP
If you catch yourself:
- Using "should", "probably", "seems to"
- Expressing satisfaction before verification ("Great!", "Done!")
- About to commit without running tests
- Relying on partial verification
- Trusting a tool's success report without checking output
Rationalizations
| Excuse | Reality |
|---|---|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence != evidence |
| "Just this once" | No exceptions |
| "Tool said success" | Verify independently |
| "Partial check is enough" | Partial proves nothing |
Key Patterns
Tests:
CORRECT: [Run test] → [See: 34/34 pass] → "All tests pass"
WRONG: "Should pass now" / "Looks correct"
Pipeline output:
CORRECT: [Check output file exists] → [Verify size/format] → "Pipeline produced valid output"
WRONG: "Galaxy shows green" (without checking actual data)
Notebook:
CORRECT: [Restart kernel] → [Run All] → [Check no errors] → "Notebook runs cleanly"
WRONG: "I updated the cell" (without re-running)
The Bottom Line
Run the command. Read the output. THEN claim the result.
Attribution
Adapted from obra/superpowers verification-before-completion skill.
FAQ
What does the verification-before-completion skill do?
Enforces evidence-based completion claims. Use before claiming work is done, tests pass, or bugs are fixed. Requires running verification commands and confirming output before any success claims.
How do I install verification-before-completion?
Run npx skills add https://github.com/delphine-l/claude_global --skill verification-before-completion in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/verification-before-completion/ (personal) or .claude/skills/verification-before-completion/ (project).
Which AI agents can use verification-before-completion?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is verification-before-completion safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains verification-before-completion?
It is published by delphine-l in delphine-l/claude_global. It has 39 recorded installs.
More from delphine-l/claude_global
token-efficiency
delphine-l/claude_global
Token optimization best practices for cost-effective Claude Code usage. Automatically applies efficient file reading, command execution, and output handling strategies. Includes model selection guidance (Opus for learning, Sonnet for development/debugging). Prefers bash commands over reading files.
bioinformatics-fundamentals
delphine-l/claude_global
Core bioinformatics concepts including SAM/BAM format, AGP genome assembly format, sequencing technologies (Hi-C, HiFi, Illumina), quality metrics, and common data processing patterns. Essential for debugging alignment, filtering, pairing issues, and AGP coordinate validation.
folder-organization
delphine-l/claude_global
Open the skill to read its SKILL.md instructions.
bioinformatics-visualization
delphine-l/claude_global
Publication-quality bioinformatics figures - phylogenetic trees, genome browsers, iTOL datasets, and data presentation
obsidian
delphine-l/claude_global
Integration with Obsidian vault for managing notes, tasks, and knowledge when working with Claude. Supports adding notes, creating tasks, and organizing project documentation. Updated with 2025-2026 best practices including MOCs, properties, practical organization patterns, and Obsidian CLI (1.12+).
jupyter-notebook-analysis
delphine-l/claude_global
Best practices for creating comprehensive Jupyter notebook data analyses with statistical rigor, outlier handling, and publication-quality visualizations. Includes Claude API image size helpers.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work