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 ./instructions/r3/core/skills/checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body is an unusually lean, well-sequenced process specification with explicit validation loops and termination criteria — workflow clarity is excellent. Its main weakness is actionability: the checklist artifact itself is never concretely exemplified, so an agent must infer the item format, storage location, and reviewer prompt structure from abstract rules.

Suggestions

Include a short example checklist block (3-5 real items with the 0-100 ranking annotation) so the item format, category structure, and severity calibration are concrete rather than inferred.

Add a minimal template or bullet list for the fresh-eye reviewer delegation (what to pass, what to ask for, expected report format) to make step 4 directly executable.

Specify concrete storage guidance in step 1 (e.g. a default path or naming pattern like .claude/checklists/<feature>.md) instead of 'a project/feature temporary location'.

DimensionReasoningScore

Conciseness

The body is telegraphic and dense ('Each item contains < 8 words', 'Limited only by medium+ findings, not amounts/count') with no padding and no explanation of concepts Claude already knows; the two-line Problem/Solution framing is the only exposition and it earns its place. This matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete rules exist (item word limit, 0-100 ranking instead of binary checkboxes, medium+ severity threshold, explicit reviewer inputs, termination criteria), but the central artifact is never shown: only two fragmentary sample items ('Build: no warnings, no errors') and no example checklist or reviewer delegation prompt. Guidance is instruction-only, which is acceptable, but key executable details are missing rather than minor.

3 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit validation checkpoints ('Before reporting completion, reload the checklist and honestly validate every item'), a full feedback loop ('Any new medium+ finding must be added to the checklist, resolved, and the validation cycle repeated'), and explicit termination conditions. This matches the top anchor including error-recovery loops.

5 / 5

Progressive Disclosure

There are no bundle files and the ~49-line body is appropriately self-contained, organized into Problem/Solution, Key Points, and a numbered adaptation workflow. It falls just short of the simple-skill top anchor because it uses no section headers and the numbered list mixes persistence rules with workflow steps, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

40%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 real, distinct niche but provides no actions, no 'use when' trigger guidance, and no synonyms users would naturally say. It functions more as a title than a capability description and would rarely be selected by trigger matching alone.

Suggestions

Add 2-3 concrete actions in third person, e.g. 'Creates and maintains a category-based completion checklist, validates every item against the final state, and spawns a fresh-eye reviewer subagent before reporting completion.'

Add an explicit 'Use when...' clause with natural trigger phrases, e.g. 'Use when doing long-running or multi-step work, when requirements may drift, or before declaring a task complete.'

Include common synonym terms users would actually say (checklist, verify work, validate completion, acceptance criteria) to improve trigger matching.

DimensionReasoningScore

Specificity

The description is a bare noun phrase ('Session self-verification checklist') that names a domain but lists no concrete actions or verbs, matching the 'names the domain but actions are minimal or generic' anchor. It is not entirely vague abstraction (a concrete domain is named), but it also does not reach the 1-2 concrete actions of the level-3 anchor.

2 / 5

Completeness

There is no 'Use when...' clause or equivalent trigger guidance, and the 'what' is only vaguely implied since a noun phrase does not state what the skill actually does. This fits the 'vague what and no when' anchor, not level 3 which requires a clearly stated 'what'.

2 / 5

Trigger Term Quality

It contains a few relevant, natural keywords ('session', 'self-verification', 'checklist') but misses common variations and synonyms users would say, such as 'verify work', 'validate completion', or 'requirements drift'. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of level 4.

3 / 5

Distinctiveness Conflict Risk

'Session self-verification' is a fairly distinct niche with only minor overlap risk against generic review or verification skills. It is more specific than the level-3 anchor but lacks the explicit distinct trigger phrases needed for level 5.

4 / 5

Total

11

/

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

instructions/r3/core/skills/checklist/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.