CtrlK
BlogDocsLog inGet started
Tessl Logo

save-task-list

Save current task list for reuse across sessions

56

Quality

64%

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/save-task-list/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, mostly executable workflow with explicit verification checkpoints and no over-explanation of known concepts. Minor gaps in a few vague steps and the absence of a write-verification feedback loop keep it just below exemplary.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence without explaining basic concepts, but the dynamic 'Session Context' shell-output block and some explanatory prose in steps 4-5 are minor instances that could be trimmed, fitting the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

Steps 3, 4, and 5 provide concrete executable bash, JSON, and a startup command, while steps 1, 2, and 6 give concrete direction with minor gaps (e.g., 'compare them to any tasks you know' is less specific), matching mostly-executable guidance with minor gaps.

4 / 5

Workflow Clarity

Six numbered steps are clearly sequenced with explicit checkpoints (step 2 'Verify the match', step 4 'Confirm it's present' with conditional add-back/skip logic); it is not 5 because there is no read-back feedback loop confirming the JSONL append succeeded.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clear sections (Session Context, numbered Instructions) with no nested references; it is not 5 because the inline dynamic shell-output block and the embedded hook JSON keep it just shy of exemplary organization.

4 / 5

Total

16

/

20

Passed

Description

53%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 clear and reasonably specific about a single concrete action but omits any explicit 'Use when...' trigger guidance, which caps completeness and leaves trigger-term coverage thin. It is distinct enough to avoid most conflicts but would benefit from explicit invocation triggers and a second concrete action.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to preserve or resume a task list in a new session.'

Include a second concrete action and natural synonyms, e.g. 'Save and restore the current task list across sessions; use when persisting tasks, resuming work, or reloading a task list in a new session.'

Add common user phrasings like 'resume tasks' or 'keep my task list' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'Save current task list' names the domain and one concrete action (save), with 'for reuse across sessions' stating purpose rather than additional actions, matching the anchor that names a domain and 1-2 concrete actions but is not comprehensive.

3 / 5

Completeness

It clearly states what the skill does ('Save current task list for reuse across sessions') but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap a missing when-clause holds completeness at 3.

3 / 5

Trigger Term Quality

'task list', 'save', and 'reuse across sessions' are relevant keywords a user might say, but the description offers a single phrase with no synonyms or common variations (e.g., 'persist tasks', 'restore tasks'), fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

'Save current task list for reuse across sessions' carves a fairly specific niche (task-list persistence across sessions) with only minor overlap risk against other task-management skills; it is not 5 because it lacks explicit distinct trigger phrases.

4 / 5

Total

13

/

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.

Validation15 / 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
coleam00/Archon
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.