CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-verification-gate

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

64

Quality

76%

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 ./skills/skill-verification-gate/SKILL.md

The canonical home for this skill is skill-verify in nyldn/claude-octopus

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a highly actionable, well-sequenced verification protocol with concrete commands and explicit validation checkpoints; its only weaknesses are mild table redundancy and cross-references that aren't clearly distinguished from bundle files.

DimensionReasoningScore

Conciseness

The body is mostly lean and table-driven with terse directives and real commands, but the Rationalization Table and Red Flags table overlap thematically (both hammer 'confidence ≠ evidence', 'small change'), adding redundant tokens that keep it just below anchor 5.

4 / 5

Actionability

It provides a concrete IDENTIFY/RUN/READ/VERIFY/ONLY-THEN gate plus real executable commands (`npm test`, `ls -la ... | tail -1`, `wc -l`) and a precise claim-to-evidence table, matching the fully executable anchor 5.

5 / 5

Workflow Clarity

The five-step Gate is a clearly sequenced workflow with an explicit verification checkpoint and a Red-Green regression loop with feedback (fail->fix->re-run); since validation is explicit, the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The single self-contained file is well-sectioned and appropriately scoped, but the intro host-note references like `skills/blocks/codex-host-adapter.md` and the trailing cross-skill list are not clearly signaled as external/non-bundle references versus bundle files, leaving minor navigation ambiguity at anchor 4.

4 / 5

Total

18

/

20

Passed

Description

63%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 excels at natural trigger phrasing but is fundamentally incomplete: it tells Claude when to use the skill without ever saying what the skill does, leaving the 'what' half of the equation unspecified.

Suggestions

Add a clause stating what the skill does, e.g. 'Forces fresh verification evidence (test/build/command output) before any completion claim is stated.'

Keep the strong 'Use when about to declare work complete, fixed, passing, or done' trigger but pair it with the concrete action so both 'what' and 'when' are explicit.

Tighten specificity by naming the verification artifact required (e.g. 'requires a fresh test/build command run this turn') rather than only the trigger condition.

DimensionReasoningScore

Specificity

The description only provides the trigger context ("declare work complete, fixed, passing, or done") and names no concrete actions the skill performs, matching anchor 2 (names domain but actions are minimal/generic) rather than 3 which requires 1-2 concrete actions.

2 / 5

Completeness

It has an explicit "Use when..." clause answering 'when' clearly, but the 'what' (what the skill actually does) is entirely absent, which per the rubric caps completeness at 3 when 'what' is missing or only weakly implied.

3 / 5

Trigger Term Quality

Phrases like "complete, fixed, passing, or done" are exactly the natural completion vocabulary a user or model would say, giving comprehensive coverage including synonyms, so it matches the anchor 5 example.

5 / 5

Distinctiveness Conflict Risk

"Declare work complete/fixed/passing" is a fairly distinct verification niche with minimal conflict risk against file-format or domain skills, though it could overlap with general task-completion skills, fitting anchor 4 (mostly distinct, minor overlap).

4 / 5

Total

14

/

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