CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

continuity-ledger

Create or update continuity ledger for state preservation across clears

Quality

73%

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

Quality

Content

82%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 strong, highly actionable instruction skill: exact commands, a complete YAML template, mandatory user checkpoint, and clear use/not-use guidance. Its weaknesses are minor — some duplicated statements and a trailing rationale section that could be trimmed, and no validation step confirming the handoff file was written or the mark command succeeded.

DimensionReasoningScore

Conciseness

The body is dominated by executable material (exact bash commands, a full YAML template, exact response text) with no padding explaining concepts Claude already knows. Minor trims are possible: the alias to /create_handoff is stated twice in the opening lines, 'If no handoffs exist, use general' is stated twice in step 1, and the closing 'Why Clear Instead of Compact?' section restates knowledge Claude already has about lossy compaction. This matches the level-4 anchor 'efficient; minor instances of over-explanation that could be trimmed' rather than the level-5 'every token earns its place'.

4 / 5

Actionability

Every step is copy-paste ready: an exact `ls -td ... | head -1 | xargs basename` command for folder discovery, a concrete filepath pattern with two worked examples, a complete YAML template with placeholder conventions and a field guide, exact AskUserQuestion options, an exact mark command, and the exact closing response text. This matches the level-5 anchor 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The four steps are clearly numbered and sequenced (determine filepath → write YAML → ask the user and mark outcome → confirm), and the mandatory AskUserQuestion acts as an explicit checkpoint. It falls short of the level-5 anchor because there is no validation of the written handoff (e.g., checking the file exists or the YAML parses) and no feedback loop if the artifact_mark.py command fails. It clearly exceeds level 3, whose sequences lack checkpoints entirely.

4 / 5

Progressive Disclosure

This is a single-file skill (no references/, scripts/, or assets/ exist, and no external files are referenced), and the sections (Process, When to Use, When NOT to Use) are well organized. At ~140 lines it does not qualify for the under-50-line simple-skill exception, and while the content is cohesive enough to stay inline, the structure is 'good, most content appropriately placed, minor organization gaps' (e.g., the duplicate alias note and trailing rationale section could be consolidated), matching the level-4 anchor rather than a clean level-5.

4 / 5

Total

17

/

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 communicates a clear single-purpose function but is under-built as a trigger: it names the domain and two actions, yet omits any 'use when' guidance and lacks the natural trigger phrases (handoff, save state, before clearing) a user would actually say. It sits at the mid-level anchors on three of four dimensions, with only distinctiveness scoring above the middle.

Suggestions

Add an explicit 'when' clause, e.g.: 'Use before running /clear, when context usage approaches 70%, or when picking up multi-day work' — this directly lifts completeness from the level-3 cap.

Include natural trigger terms and synonyms users would say, such as 'handoff', 'session handoff', 'save session state', or 'resume work', to improve trigger_term_quality.

Mention the concrete artifact ('writes a YAML handoff file') to move specificity from '1-2 actions' toward 'several specific actions'.

DimensionReasoningScore

Specificity

The description states 'Create or update continuity ledger' which names the domain (continuity ledger, state preservation across clears) and two concrete actions (create, update), but stops there. It does not reach the level-4/5 anchors' 'several/multiple specific actions' (e.g., writing a YAML handoff, marking outcomes, resuming sessions), so it fits the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

There is a clear 'what' ('Create or update continuity ledger for state preservation'), but no 'Use when...' clause or equivalent explicit trigger guidance — 'across clears' only weakly implies the when. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, which is exactly the level-3 anchor ('clear what, when missing or only weakly implied').

3 / 5

Trigger Term Quality

'continuity ledger', 'state preservation', and 'clears' are relevant keywords, but common natural phrases users would say are missing — 'handoff', 'session summary', 'context', 'save state', 'resume'. It matches the level-3 anchor 'some relevant keywords but missing common variations or synonyms', and does not have the broader coverage of the level-4 example.

3 / 5

Distinctiveness Conflict Risk

'Continuity ledger' carves a clear niche (state preservation across /clear) that is unlikely to fire for unrelated skills, giving 'mostly distinct; minor overlap risk'. It does not reach 5 because the term space overlaps with generic handoff/session-summary/resume skills — notably the body itself declares this skill an alias for /create_handoff — so a user asking for a 'handoff' could reasonably trigger the sibling skill instead.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

parcadei/Continuous-Claude-v3

Path

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