CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

checklist

Session self-verification checklist

Quality

68%

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

Quality

Content

85%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 tightly written, well-sequenced workflow with strong validation and feedback loops — validation before completion reporting, an independent reviewer cycle, and explicit termination criteria. Its main weakness is a handful of abstract bullets in the checklist-construction section that lack concrete examples.

DimensionReasoningScore

Conciseness

The body is dense and lean — no padded explanations of concepts Claude already knows, every section carries instructions. It falls short of 5 because the 'zero unresolved medium+ findings' criterion is repeated across steps 4, 5, and 6, and a few bullets could be merged.

4 / 5

Actionability

Mostly concrete guidance: explicit thresholds ('zero unresolved medium+ findings', '0–100% confidence score'), concrete example items ('Build: no warnings, no errors', 'Absolutely all unit tests pass'), and a defined reviewer protocol. Not 5 because several bullets are abstract without examples ('Calibrate severity from impact, risk, and consequences of omission/failure', 'Each item covers archetype/concept'), leaving the reader to interpret them.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with explicit validation checkpoints and feedback loops: 'reload the checklist and validate every item against the final state', 'Resolve deviations, then repeat validation', and the fresh-eye reviewer cycle that repeats until zero medium+ findings. Termination criteria in step 6 are unambiguous.

5 / 5

Progressive Disclosure

The body is under 50 lines, self-contained with no external references needed, and organized into six well-ordered numbered sections. Per the rubric's simple-skill guidance, this earns a 5 with well-organized sections alone.

5 / 5

Total

18

/

20

Passed

Description

36%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 is extremely terse: it names a plausible niche but gives no actions, no use-when guidance, and no distinguishing trigger phrases. It reads more like a title than a description, which limits both completeness and trigger-term quality.

Suggestions

Expand the 'what' with 2-3 concrete actions, e.g. 'Create and maintain a category-based checklist of requirements and medium+ findings; re-validate every item against the final state before reporting completion.'

Add an explicit trigger clause, e.g. 'Use when starting long-running or multi-step implementation work, or before declaring a task complete.'

Add natural trigger terms users would actually say ('verify', 'didn't miss anything', 'before declaring done', 'long-running task') to improve both trigger quality and distinctiveness from generic todo/checklist skills.

DimensionReasoningScore

Specificity

'Session self-verification checklist' names a domain but contains no concrete action verbs ('create', 'maintain', 'validate'), matching the anchor for naming the domain with minimal or generic actions. It does not reach 3 because no specific actions are listed at all, and it is above 1 because the domain is identifiable rather than pure abstraction.

2 / 5

Completeness

The description offers only a vague 'what' (names an artifact, not what it does) and no 'when' / 'Use when...' trigger guidance whatsoever. Not 1 because the domain is at least identifiable; not 3 because even the 'what' is implicit.

2 / 5

Trigger Term Quality

'session', 'self-verification', and 'checklist' are somewhat natural keywords, but common variations users would actually say ('verify the work', 'validate completion', 'make sure nothing was forgotten', 'long-running task') are missing. Coverage is thinner than the 'good keyword coverage' of a 4.

3 / 5

Distinctiveness Conflict Risk

'Session self-verification checklist' is somewhat specific but overlaps significantly with todo/task-tracking, code-review, and verification skills, with no trigger phrases to disambiguate. Not 4 because nothing in the description would prevent it from firing for adjacent checklist or review use cases.

3 / 5

Total

10

/

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

griddynamics/rosetta

Path

.claude/skills/checklist-B/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.