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

85

1.22x
Quality

80%

Does it follow best practices?

Impact

92%

1.22x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/verification-before-completion/SKILL.md
SKILL.md
Quality
Evals
Security

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 and explicit validation checkpoints. Its main weakness is some redundancy across sections (Red Flags, Rationalization Prevention, and motivational content in 'Why This Matters' overlap), which could be tightened. Overall it effectively teaches a critical discipline with specific patterns Claude can follow.

Suggestions

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

Trim the 'Why This Matters' section — the motivational framing ('trust broken', 'you'll be replaced') is less useful than the concrete patterns; a single line referencing past failures would suffice.

DimensionReasoningScore

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 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.

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 appropriately sized and logically ordered. No external references are needed for this behavioral/process 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 a clear behavioral guardrail skill with explicit trigger conditions, making it strong on completeness and distinctiveness. However, it could be more specific about what verification commands entail (tests, linting, builds, type-checking) 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-checking' instead of the generic 'running verification commands'.

Include more natural trigger variations such as 'done', 'finished', 'ready to merge', 'all tests pass', 'LGTM' to improve keyword coverage.

DimensionReasoningScore

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) with explicit trigger conditions.

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 has a very distinct niche — it's a meta-skill about verification discipline before claiming completion, which is unlikely to conflict with other skills that focus on specific technical tasks.

3 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
roman01la/skills-agents
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.