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

Quality

Content

92%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 exemplarily lean, well-sectioned checklist that is directly usable for its single purpose. Its only weakness is a handful of items that defer to undefined targets or standards, which could be tightened with pointers to where those targets live.

DimensionReasoningScore

Conciseness

The body is a lean checkbox list with zero padding or explanation of concepts Claude already knows; every line states a check and nothing else, fitting 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Most items are concrete, checkable criteria ('Coverage 80% or higher', 'changed code coverage ≥85%', 'no critical or high findings'), but a minority reference undefined targets ('meet defined targets', 'applicable laws, regulations, standards') without saying where those are defined, leaving minor gaps.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose single action — walk the checklist — is unambiguous; the sections (General, Outcome, Verification, Delivery, Closure) give a clear ordered progression and the content itself is a set of validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (none exist in the bundle), and the content is well organized into clearly headed sections, which the simple-skill exception scores at 5.

5 / 5

Total

19

/

20

Passed

Description

28%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 a terse noun phrase that identifies the skill's domain but gives Claude almost nothing to trigger on: no concrete capabilities, no natural trigger terms, and no 'use when' guidance. It sits well below the good examples, which pair concrete actions with explicit trigger clauses.

Suggestions

Add a verb-led statement of concrete actions, e.g. 'Verifies completed work against a checklist covering tests, coverage, security, delivery, and closure criteria.'

Add an explicit trigger clause, e.g. 'Use when asked to verify, QA, or sign off on completed work before delivery.'

Include natural synonyms users would actually say (verify, check, review, sign off, QA) to reduce trigger misses.

DimensionReasoningScore

Specificity

The description 'Session self-verification checklist' names the domain (session self-verification) but describes no concrete actions — it is a bare noun phrase like 'Processes PDF files' with no enumerated capabilities.

2 / 5

Completeness

The 'what' is present but vague (a checklist for checking work results) and there is no 'Use when...' or equivalent trigger clause, matching the anchor 'has a vague what and no when'.

2 / 5

Trigger Term Quality

It contains only generic keywords ('session', 'self-verification', 'checklist') and none of the natural phrases a user would say when they need this skill, such as 'verify my work', 'QA the result', or 'check the changes'.

2 / 5

Distinctiveness Conflict Risk

'Session self-verification' is somewhat specific but a generic verification checklist overlaps with code-review, QA, and verification skills, so it could trigger for the wrong skill.

3 / 5

Total

9

/

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