verification-mastery
Installation
SKILL.md
<domain_overview>
✅ VERIFICATION MASTERY: EVIDENCE BEFORE CLAIMS
Philosophy: Claiming work is complete without verification is dishonesty, not efficiency. Evidence before claims, always. EVIDENCE INTEGRITY MANDATE (CRITICAL): Never claim a task is complete based on assumption or past memory. You MUST generate fresh evidence (logs, screenshots, test output) for every claim. AI-generated success reports are untrustworthy without proof. Any completion signal sent without accompanying verification artifacts must be rejected as "Hallucinated Success".
🚨 THE IRON LAW
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim it passes. Violating the letter of this rule is violating the spirit of this rule. </domain_overview> <core_workflow>
🚪 THE GATE FUNCTION
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?