CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-verification-gate

Use when about to declare work complete, fixed, passing, or done

48

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-verification-gate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable and presents a clear, checkpoint-driven verification workflow with concrete commands and examples. Its main weakness is redundancy across the Rationalization and Red Flags tables and a monolithic structure with no progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient and concrete, but the Rationalization Table and Red Flags table restate the same excuses ("I'm confident", "small change", "agent said it worked") twice, and the Multi-Provider Context re-explains hallucination risk Claude already knows, so it could be tightened.

2 / 3

Actionability

It gives concrete executable guidance: a 5-step IDENTIFY/RUN/READ/VERIFY procedure, real commands (npm test, ls -la ~/.claude-octopus/results/*-synthesis-*.md, wc -l, git diff), and a Red-Green regression recipe with copy-paste-ready example output.

3 / 3

Workflow Clarity

The Gate is an explicitly sequenced 5-step process built around validation checkpoints, supplemented by the 'When to Apply' checklist and the evidence-mapping table that define explicit verify-before-claim feedback loops.

3 / 3

Progressive Disclosure

The skill is a single well-organized SKILL.md with clear section headers and no nested references, but it is a ~130-line monolith with no bundle files and no file splitting; the Claude Octopus / multi-provider specifics could plausibly live in a separate reference.

2 / 3

Total

10

/

12

Passed

Description

22%

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 provides an explicit trigger but omits any statement of what the skill actually does, leaving it incomplete and light on concrete capability detail. Its trigger terms are recognizable but framed around the agent's state rather than natural user requests.

Suggestions

Add a 'what' clause stating the skill's action, e.g. 'Enforces a verification gate requiring fresh evidence before declaring work complete. Use when about to claim work is complete, fixed, passing, or done.'

Broaden trigger terms to natural user phrasings such as 'verify the tests pass', 'check this is actually done', or 'confirm the fix works' alongside the completion-state words.

Make the niche explicit to reduce overlap with other workflow skills, e.g. 'Requires running a fresh verification command and reading its output before any completion claim.'

DimensionReasoningScore

Specificity

The description "Use when about to declare work complete, fixed, passing, or done" names no concrete actions at all — it states only a trigger, never what the skill does (e.g. enforce a verification gate), matching the score-1 anchor 'Vague or no actions; abstract language'.

1 / 3

Completeness

It explicitly answers "when" via the Use-when clause but never states "what" the skill does; per the guideline to score only what is explicitly stated and not infer, missing the what matches the score-1 anchor 'Missing what OR when'.

1 / 3

Trigger Term Quality

It includes natural completion-state keywords ("complete", "fixed", "passing", "done") a user might echo, but it frames the trigger around the agent's own declaration rather than common user phrasings like "verify" or "check the tests", leaving common variations missing.

2 / 3

Distinctiveness Conflict Risk

The verification-before-completion niche is somewhat specific, but as a meta-process skill it could overlap with related workflow skills (code-review, TDD, delivery gates) that also gate on completion, matching the score-2 anchor 'Somewhat specific but could still overlap'.

2 / 3

Total

6

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nyldn/claude-octopus
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.