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

1.22x

Quality

80%

Does it follow best practices?

Impact

92%

1.22x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/verification-before-completion/SKILL.md

Quality

Content

85%

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

This is a strong behavioral skill that provides clear, actionable verification workflows with concrete examples of correct and incorrect patterns. The Gate Function is an excellent sequential process with validation checkpoints. The main weakness is some redundancy between sections (Red Flags, Rationalization Prevention, and motivational content in 'Why This Matters') that could be consolidated for better token efficiency.

Suggestions

Merge the 'Red Flags' and 'Rationalization Prevention' sections into a single table to eliminate redundancy and save tokens.

Remove or significantly trim the 'Why This Matters' section — Claude doesn't need motivational framing about trust and replacement to follow instructions.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but has some redundancy — the 'Rationalization Prevention' table largely restates the 'Red Flags' section, and the 'Why This Matters' section includes motivational content that doesn't add actionable value. The repeated emphasis on 'non-negotiable' and 'no exceptions' is somewhat verbose for Claude.	2 / 3
Actionability	The Gate Function provides a clear, concrete 5-step process. The Common Failures table maps specific claims to specific required evidence. The Key Patterns section gives concrete ✅/❌ examples with actual verification patterns (run command, check output, then claim). This is highly actionable behavioral guidance.	3 / 3
Workflow Clarity	The Gate Function is a clear sequential workflow with an explicit validation checkpoint (step 4) and a feedback loop (if NO → state actual status). The regression test pattern includes a full red-green cycle. The 'When To Apply' section clearly defines trigger conditions. This is well-sequenced with proper validation gates.	3 / 3
Progressive Disclosure	For a standalone skill with no bundle files, the content is well-organized with clear sections progressing from principle → process → examples → application triggers. The sections are logically ordered and appropriately sized. No external references are needed for this behavioral skill.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 effectively communicates when to use the skill with a clear 'Use when' clause and a distinct behavioral niche around verification before success claims. However, it lacks specificity about what concrete verification actions should be taken (e.g., running tests, linting, building) and could include more natural trigger terms that users or Claude would encounter in practice.

Suggestions

Add specific concrete verification actions like 'run tests, check linting, build project, verify type checks' instead of the generic 'running verification commands'

Include more natural trigger variations such as 'done', 'finished', 'ready to merge', 'ship it', 'looks good', 'all tests pass' to improve matching

Dimension	Reasoning	Score
Specificity	The description names a domain (verification before claiming completion) and some actions ('running verification commands and confirming output'), but doesn't list specific concrete actions like 'run tests', 'check linting', 'build project', or 'run type checks'.	2 / 3
Completeness	Clearly answers both what ('running verification commands and confirming output before making success claims') and when ('when about to claim work is complete, fixed, or passing, before committing or creating PRs'). The 'Use when' clause is explicit and upfront.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'complete', 'fixed', 'passing', 'committing', 'creating PRs', but misses natural user phrases like 'done', 'finished', 'ready to merge', 'tests pass', 'ship it'. The terms are more about when Claude should self-trigger rather than what users would say.	2 / 3
Distinctiveness Conflict Risk	This skill occupies a clear niche — it's a meta-behavioral skill about verification before claiming completion, which is distinct from skills that actually perform testing, committing, or PR creation. Unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: roman01la/skills-agents
Commit: 45417f2

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.