CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-verify

Use when a nontrivial change needs end-to-end verification before committing or shipping

Quality

69%

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-verify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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's core verification-gate content is strong: a memorable iron law, a concrete 5-step gate, evidence-requirement tables, and runnable examples. Its weaknesses are redundancy (the Red Flags table duplicates the Rationalization Table), a jargon-heavy opening section that doesn't connect to the rest, and a dangling reference to a host-adapter file that does not exist in the bundle.

Suggestions

Merge the 'Rationalization Table' and 'Red Flags' sections into one — they repeat the same excuses nearly verbatim and could cut ~15 lines.

Fix or remove the reference to 'skills/blocks/codex-host-adapter.md' (and the sibling-skill list): either ship those files in references/ or drop the cross-references, since they currently point at files not in the bundle.

Rewrite or move the 'Portable feature evidence' opening section: its jargon ('policy provenance', 'open-marker count', 'task-contract digest') is not actionable and is not connected to the Gate workflow below it.

DimensionReasoningScore

Conciseness

The body is mostly operational rather than explanatory, but there is clear redundancy: the 'Red Flags — STOP and Verify' table restates the 'Rationalization Table' almost line-for-line ('I'm confident', small-change excuses, agent-reported success appear twice), and the host/multi-provider material ('Claude Octopus', 'orchestrate.sh', probe/grasp/tangle/ink) is niche context that could be tightened. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' — better than noticeably verbose (2), short of the efficient (4) anchor.

3 / 5

Actionability

The Gate gives a concrete executable sequence (IDENTIFY/RUN/READ/VERIFY/STATE), the Evidence table maps specific claims to specific required outputs, there are runnable bash commands for synthesis verification, and the red-green regression example is fully concrete. It falls short of 5 because the opening 'Portable feature evidence' section is abstract jargon ('policy provenance and open-marker count through the existing boundary adapter') with no executable counterpart, and most verification commands appear as examples rather than copy-paste-ready prescriptions.

4 / 5

Workflow Clarity

The core workflow is a clearly sequenced 5-step gate with explicit validation checkpoints and error-recovery guidance (rationalization handling, red-green cycle with revert/re-run), plus a concrete when-to-apply checklist. It misses 5 because the 'Portable feature evidence' opening section doesn't integrate into that sequence and reads as disconnected requirements, leaving a minor coherence gap in an otherwise strong flow.

4 / 5

Progressive Disclosure

The body references 'skills/blocks/codex-host-adapter.md' and names sibling skills (flow-develop.md, skill-tdd.md, etc.), but none of these files exist in the bundle — the reference is dangling, so navigation leads nowhere. At ~135 lines the file is also above the under-50-line simple-skill case, and host-specific adaptation notes are inlined in the body rather than split out. Some structure exists (well-labeled sections), matching the 3 anchor: 'some structure but could be better organized; references present but not clearly signaled.'

3 / 5

Total

14

/

20

Passed

Description

58%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 has a clear, explicit 'Use when' trigger with a reasonable scope (nontrivial changes, pre-commit/pre-ship), but it states only one generic capability and misses common trigger synonyms (test, validate, PR, push). It is serviceable but sits in the middle of the range rather than exemplifying the strong examples.

Suggestions

Lead with the concrete 'what' in third person before the trigger clause, e.g. 'Runs the verification commands for a change (tests, build, exit codes) and gates completion claims on fresh evidence.'

Add natural trigger synonyms and phrases users would say: 'verify', 'test', 'validate', 'before pushing', 'before opening a PR', 'before shipping'.

Sharpen distinctiveness by naming the gate itself — e.g. 'before marking a task complete or claiming a bug is fixed' — to separate it from generic testing/TDD skills.

DimensionReasoningScore

Specificity

The description names one concrete action — 'end-to-end verification' — tied to a clear domain ('a nontrivial change'), but coverage is minimal: no concrete verification activities (run tests, check exit codes, gate the commit) are listed. It sits between the 'minimal or generic actions' anchor (2) and '1-2 concrete actions' (3); the single named action with an explicit scope earns 3 rather than 2, but comprehensiveness gaps keep it below 4.

3 / 5

Completeness

An explicit 'Use when ...' clause states the trigger clearly ('a nontrivial change needs end-to-end verification before committing or shipping'), and the 'what' is present though embedded in the when-clause rather than stated as its own capability sentence. Both what and when exist, but the when-embedded 'what' and absence of concrete trigger phrases keep this at 4 rather than the fully explicit 5 anchor.

4 / 5

Trigger Term Quality

Relevant keywords are present ('verification', 'end-to-end', 'committing', 'shipping', 'nontrivial change') but common natural variations are missing — users would equally say 'verify', 'test', 'validate', 'before pushing', or 'before opening a PR'. This matches the anchor for 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

The 'nontrivial change' + 'before committing or shipping' scoping is somewhat distinctive, but 'verification' overlaps broadly with any testing, TDD, or code-review skill that also triggers on changes near commit time. It could still overlap with similar skills, matching the 3 anchor rather than the mostly-distinct 4.

3 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nyldn/claude-octopus

Path

skills/skill-verify/SKILL.md

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.