tessl install https://github.com/obra/superpowers --skill verification-before-completionUse 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
Average Score
96%
Content
100%
Description
90%
Generated
Validations
Total score
14/16| Criteria | Score |
|---|---|
skill_md_line_count SKILL.md line count is 140 (<= 500) | |
frontmatter_valid YAML frontmatter is valid | |
name_field 'name' field is valid: 'verification-before-completion' | |
description_field 'description' field is valid (225 chars) | |
description_voice 'description' uses third person voice | |
description_trigger_hint Description includes an explicit trigger hint | |
compatibility_field 'compatibility' field not present (optional) | |
allowed_tools_field 'allowed-tools' field not present (optional) | |
metadata_version 'metadata' field is not a dictionary | |
metadata_field 'metadata' field not present (optional) | |
license_field 'license' field is missing | |
frontmatter_unknown_keys No unknown frontmatter keys found | |
body_present SKILL.md body is present | |
body_examples Examples detected (code fence or 'Example' wording) | |
body_output_format Output/return/format terms detected | |
body_steps Step-by-step structure detected (ordered list) |
Content
Total score
12/12| Dimension | Score |
|---|---|
conciseness Extremely lean and efficient. Uses tables, bullet points, and minimal prose. Every section earns its place with no explanation of concepts Claude already knows. The repetition is intentional reinforcement for a critical behavioral rule, not padding. | 3/3 |
actionability Provides concrete gate function with numbered steps, specific command patterns (✅/❌ examples), clear tables mapping claims to requirements, and explicit red flags. The guidance is immediately actionable without ambiguity. | 3/3 |
workflow_clarity The 5-step gate function is crystal clear with explicit validation checkpoints. The regression test pattern shows a complete red-green verification cycle. Feedback loops are built into the core workflow (verify → if NO → state actual status). | 3/3 |
progressive_disclosure Well-organized with clear sections (Overview, Gate Function, Common Failures, Red Flags, etc.). For a behavioral skill of this scope (~100 lines), no external references are needed. Content is appropriately structured for quick scanning and reference. | 3/3 |
Overall Assessment
This is an exemplary skill document that teaches a critical behavioral pattern with maximum efficiency. It uses tables, checklists, and concrete examples to make the verification requirement unambiguous and immediately actionable. The document successfully balances thoroughness with conciseness by using structured formats rather than prose.
Description
Suggestions 1
Total score
11/12| Dimension | Score |
|---|---|
specificity Names the domain (verification before claims) and some actions ('running verification commands', 'confirming output'), but doesn't list specific concrete actions like 'run tests', 'check linter', 'verify build passes'. | 2/3 |
completeness Clearly answers both what ('running verification commands and confirming output before making success claims') and when ('about to claim work is complete, fixed, or passing, before committing or creating PRs'). Has explicit 'Use when' clause. | 3/3 |
trigger_term_quality Includes natural keywords users/Claude would encounter: 'complete', 'fixed', 'passing', 'committing', 'creating PRs', 'success claims'. These are terms that naturally appear when finishing work. | 3/3 |
distinctiveness_conflict_risk Clear niche focused on verification before completion claims - distinct from general testing skills or commit message skills. The specific trigger of 'about to claim work is complete' creates a unique activation context. | 3/3 |
Suggestions
Add specific concrete verification actions like 'run tests, check linter, verify build succeeds' to improve specificity
Overall Assessment
This is a well-structured skill description with strong trigger terms and clear when/what guidance. The main weakness is that the specific verification actions could be more concrete (e.g., 'run tests, check linter output, verify builds'). The phrase 'evidence before assertions always' is a good memorable principle but slightly informal.