Browse 138,453 skills across 70 categories. Mirrored from majiayu000/claude-skill-registry.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verifi...
Household Expense Tracker (Hackathon 2026-01-07)
This skill should be used when about to claim work is complete, fixed, or passing. It requires running verification comm...
Use when about to claim work is complete, fixed, or passing. REQUIRES running verification commands and confirming outpu...
Run verification commands and confirm output before claiming success
Never claim completion without fresh verification evidence
Claiming work is complete without verification is dishonesty, not efficiency.
verification-before-completion
Enforces rigorous verification evidence before any claims of task completion, preventing false positives, untested deplo...
This skill should be used when the user asks to "verify the implementation", "check before finishing", "quality gates",...
Use when about to claim work is complete, fixed, or passing. MANDATORY TRIGGER on phrases like: 'I'm done', 'fixed', 'co...
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs, when task are finished -...
Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests p...
（中文）Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running ve...
Use when about to claim completion, express satisfaction with work, or state that a task is done. Triggers on phrases li...
Claiming work is complete without verification is dishonesty, not efficiency. Use when ANY variation of success/completi...
Confirms fixes are effective before marking complete
Use when finishing any task. Final checklist before marking complete. Ensures nothing forgotten, all tests pass, documen...
Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified
Use before marking any task complete to ensure all requirements are met
Verification checklists for game development tasks. Use when completing features, assets, or systems to ensure nothing i...
Enforce comprehensive verification and testing before declaring completion. Use when implementing features, making chang...
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Us...
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements...
Define checkpoints to validate work before proceeding to next phase
Validate outputs using rule-based checks (required strings, regex, length, ranges). Use when you need deterministic veri...
A comprehensive verification system for Claude Code sessions.
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes",...
Pre-PR verification checklist. Use after completing features, before creating PRs, or after refactoring. Do NOT use for...
Run verify → identify failures → fix → verify again until all checks pass. Iterative quality enforcement loop for reachi...
Comprehensive 6-check verification framework for validating implementation quality across build, types, lint, tests, sec...
Rigorous protocol for verifying code correctness before considering a task complete.
Comprehensive verification system for construction automation deliverables. Use after completing estimates, schedules, r...
Verify changes work before completing. Use browser testing, test suites, and manual checks.
Evidence before claims, always. No completion claims without fresh verification. The final gate before declaring success...
Verification mode that stops and analyzes on failures, workarounds, or resolution issues