CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

checklist-runner

Generic checklist execution engine for any .md checklist. Use this skill when an agent needs to validate work against a checklist. Supports YOLO (autonomous) and interactive modes with pass/fail/partial verdicts.

Quality

77%

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

Quality

Content

68%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 well-structured, actionable workflow with concrete templates and decision thresholds. Its chief gap is the absence of an explicit validation/feedback loop for what is fundamentally a batch evaluation operation.

Suggestions

Add an explicit feedback loop for the batch evaluation, e.g. after the final report, a 'Review FAILED items → address → re-run checklist' checkpoint, to lift workflow clarity above the batch cap.

Tighten abstract guidance like 'Consider both explicit mentions and implicit coverage' into concrete checks (e.g. grep for the requirement keyword, inspect the cited file/line) to improve actionability.

Move or trim the Available Checklists table if those checklists live elsewhere, keeping the SKILL.md focused on execution behavior.

DimensionReasoningScore

Conciseness

The body is efficient — tables for modes/verdicts, a copy-paste report template, and no padding with concepts Claude already knows — matching the efficient/minor-trim anchor; not a 5 because a few phrasings like 'Read and understand the requirement' could be tightened.

4 / 5

Actionability

Provides concrete search paths, a verdict symbol table, an exact pass-rate formula, and a copy-paste report template with decision thresholds (>=90%, 70-89%), matching mostly-executable guidance with minor gaps; not a 5 because some steps like 'Consider both explicit mentions and implicit coverage' remain abstract.

4 / 5

Workflow Clarity

A clear 6-step sequence with per-item evidence checks and decision thresholds, but this is a batch operation with no explicit validate→fix→retry feedback loop, so per the batch-operation cap it cannot exceed 3; not a 2 because the sequence and per-item verification are well defined.

3 / 5

Progressive Disclosure

A single self-contained file (~104 lines) with well-organized sections (Usage, Execution, Available Checklists) and no bundle references to split, matching the good-structure/minor-gaps anchor; not a 5 only because there are no one-level-deep references to demonstrate ideal split, and the Available Checklists table is somewhat tangential.

4 / 5

Total

15

/

20

Passed

Description

76%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 well-constructed: it states concrete capabilities, includes an explicit 'Use this skill when...' trigger, and occupies a clear niche. Its main weakness is limited keyword/synonym coverage for trigger terms.

Suggestions

Add natural trigger synonyms and phrasings users might say, e.g. 'checklist validation', 'review against a checklist', 'definition-of-done check', to broaden trigger-term coverage.

Consider naming a couple more concrete actions (e.g. 'produces a pass/fail/partial report with approval decision') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'validate work against a checklist', 'Supports YOLO (autonomous) and interactive modes with pass/fail/partial verdicts' — matching the anchor for several specific actions with minor coverage gaps; not a 5 because it stops short of comprehensive action enumeration.

4 / 5

Completeness

Clearly answers 'what' (generic checklist execution engine with modes and verdicts) and explicitly answers 'when' via 'Use this skill when an agent needs to validate work against a checklist', matching the anchor for both what and when with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Contains the natural term 'checklist' and 'validate work against a checklist', but lacks common synonyms or variations users might say, fitting the anchor for some relevant keywords missing common variations; not a 4 because keyword coverage is thin rather than good.

3 / 5

Distinctiveness Conflict Risk

A clear niche — checklist validation engine — with distinct triggers and only minor overlap risk with closely related review/QA skills; not a 5 because 'generic' and 'any .md checklist' leave some breadth.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

SynkraAI/aiox-core

Path

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