CtrlK
BlogDocsLog inGet started
Tessl Logo

verification-before-completion

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

92

1.22x
Quality

91%

Does it follow best practices?

Impact

92%

1.22x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is verification-before-completion in obra/superpowers

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is exemplary: a tight, well-structured discipline skill with a concrete gated workflow, explicit validation checkpoints, and actionable per-scenario patterns, all with no wasted tokens and no external-file dependency. It fully satisfies the simple-skill exception across every dimension.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding, no explaining what verification or commits are — and uses tight tables and code blocks where every token earns its place, matching the 'lean and efficient' top anchor.

5 / 5

Actionability

Provides a concrete executable 5-step Gate Function (IDENTIFY→RUN→READ→VERIFY→CLAIM) plus per-scenario ✅/❌ Key Patterns and a Red Flags word-list, giving copy-paste-ready, specific guidance across common cases.

5 / 5

Workflow Clarity

Clear sequence with an explicit validation checkpoint (VERIFY step with 'If NO / If YES' branches) and feedback loops for error recovery, matching the top anchor for sequenced validation with recovery.

5 / 5

Progressive Disclosure

A single ~130-line SKILL.md with no bundle files, organized into clearly delineated sections with no nested references or wall of text — meeting the simple-skill exception that allows a 5 with well-organized sections alone.

5 / 5

Total

20

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it explicitly pairs a 'Use when' trigger with a clear behavioral 'what', using natural completion/commit language that users actually produce. Minor gaps in synonym coverage and slight genericness keep specificity and trigger quality at 4 rather than 5.

Suggestions

Add a few common synonyms/paraphrases (e.g., 'done', 'ready', 'shipped', 'green') to broaden trigger-term coverage toward the top anchor.

Lead with the concrete action ('Runs verification commands and confirms output before any completion claim') before the 'Use when' clause to strengthen the 'what' framing and distinctiveness.

DimensionReasoningScore

Specificity

Names several concrete actions — 'claim work is complete, fixed, or passing', 'committing or creating PRs', 'running verification commands and confirming output' — with only minor framing-as-constraint gaps, fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers both 'what' ('requires running verification commands and confirming output before making any success claims') and 'when' ('Use when about to claim work is complete... before committing or creating PRs') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Includes natural phrases users actually emit ('complete, fixed, or passing', 'committing or creating PRs') with good keyword coverage, but omits a few common synonyms, matching 'good keyword coverage; a few natural terms missing' rather than the exhaustive 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a distinct niche (verification discipline before success claims/commits) with specific triggers and only minor overlap risk with general diligence skills, fitting 'mostly distinct; minor overlap risk' rather than the cleanly-niched 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
lucianghinda/superpowers-ruby
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.