CtrlK
BlogDocsLog inGet started
Tessl Logo

verification-loop

A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/verification-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 skill body is a well-structured, actionable verification playbook with executable commands and clear stop-gates on the critical phases. The main weakness is uneven validation rigor across phases and slight redundancy in the framing sections.

Suggestions

Add explicit pass/fail gating to Phases 3-6 (e.g. 'If lint errors exceed N, STOP and fix') so every phase has a clear checkpoint.

Trim the redundant opening line and the 'Integration with Hooks' commentary to tighten token use.

Replace the 'X' placeholders in the report template with a short note on how to fill them, or reference the command output that populates each field.

DimensionReasoningScore

Conciseness

The body is mostly lean bash commands and short imperatives, with only minor redundancy such as the opening line repeating the description and the somewhat padded hooks section.

4 / 5

Actionability

It provides concrete, copy-pasteable commands for each phase (npm run build, npx --no-install tsc --noEmit, ruff check ., grep, git diff), with minor gaps like OR alternation and 'X' placeholders in the report template.

4 / 5

Workflow Clarity

Six verification phases are clearly sequenced with explicit stop-and-fix gates on build and types, though later phases (lint, security, diff review) only say 'report' and lack explicit validation checkpoints.

4 / 5

Progressive Disclosure

The single self-contained file is well-organized into clear sections (When to Use, Verification Phases, Output Format, Continuous Mode, Integration) with no external references needed; at ~120 lines it sits just above the simple-skill threshold.

4 / 5

Total

16

/

20

Passed

Description

57%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 clearly signals when to invoke the skill and carves out a distinct niche, but it stays abstract about what the skill actually does and lacks concrete action verbs. Strengthening it with specific verification actions and more trigger synonyms would raise the score.

Suggestions

Replace 'comprehensive verification system' with concrete actions, e.g. 'Runs build, type-check, lint, tests, and security scans before declaring work complete.'

Add natural trigger synonyms such as 'check', 'validate', 'review', or 'QA' alongside 'verifying' so it matches more user phrasings.

Tighten the 'what' to a short enumerated capability list so the description answers both what and when with concrete phrases.

DimensionReasoningScore

Specificity

The phrase 'comprehensive verification system' names the domain but lists no concrete actions (no mention of build, type-check, lint, test, or security steps), matching the anchor for minimal/generic actions.

2 / 5

Completeness

Both 'what' (a verification system for Claude Code sessions) and an explicit 'when' ('Use when verifying a Claude Code session's work before claiming it is complete') are present, though the 'what' is somewhat vague.

4 / 5

Trigger Term Quality

It includes relevant natural terms like 'verifying', 'Claude Code session', and 'claiming it is complete', but misses common synonyms users might say such as 'check', 'validate', 'review', or 'QA'.

3 / 5

Distinctiveness Conflict Risk

The trigger of verifying a session before claiming completion is a fairly distinct niche, with only minor overlap risk against generic code-review or PR-prep skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.