CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ledger

Sweep the full current session, repo/task context, local task files, and (with approval) connected remote task stores for outstanding actionable work, then record only useful high-confidence items in docs/outstanding-issues.md with priority, context, and next steps. Use when the user types "/ledger" or asks to extract outstanding tasks from this session into the ledger.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-engineered instruction skill: every phase of the session-sweep workflow is concrete and executable, with explicit guardrails (approval boundary, dedupe-by-intent, no-op rule, immutable inbox writes). The only notable gaps are a slight template/mapping redundancy and the absence of an explicit error-recovery loop after the post-write check.

DimensionReasoningScore

Conciseness

The body is dense operational instruction with no explanations of concepts Claude already knows, but the structured-record template fields (importance, category, why, context, owner, dependencies, status, confidence) are re-listed in the field-mapping section, and the disambiguation paragraph could be tightened.

4 / 5

Actionability

The write path is copy-paste ready ('npm run issues:add -- --pri P2 --type issue --summary "<title>" --detail "<detail>" --source "session YYYY-MM-DD /ledger sweep"') with an explicit field mapping (P0/P1 → P1, category → Type), an escaping rule, a verification command, and concrete fallback search patterns ('outstanding*', '*issues*', 'TODO.md', 'BACKLOG.md').

5 / 5

Workflow Clarity

The four-phase sequence (read-only sweep → report with pause for confirmation → filter/dedupe → queue + check) has strong checkpoints, but there is no fix-and-retry instruction for the case where 'npm run check:outstanding-issues' fails, so it falls short of the feedback-loop anchor.

4 / 5

Progressive Disclosure

No bundle files exist; the body is self-contained with clear numbered sections, and its only reference ('Follow every writing rule in the issues skill' → ../issues/SKILL.md) is one level deep and clearly signaled. All inlined content is needed at execution time, so no split is warranted.

5 / 5

Total

18

/

20

Passed

Description

88%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.

A strong description: third-person voice, concrete actions covering the whole sweep-to-record pipeline, and an explicit trigger clause. Its only weaknesses are missing common synonyms for the trigger terms and a naming collision with the separate branch-review 'ledger' tooling.

DimensionReasoningScore

Specificity

'Sweep the full current session, repo/task context, local task files, and (with approval) connected remote task stores' plus 'record only useful high-confidence items in docs/outstanding-issues.md with priority, context, and next steps' names multiple concrete actions across the full pipeline with comprehensive coverage.

5 / 5

Completeness

It clearly answers both 'what' (sweep four named sources and record high-confidence items with priority, context, and next steps) and 'when' ('Use when the user types "/ledger" or asks to extract outstanding tasks from this session into the ledger') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger terms like '/ledger', 'outstanding tasks', 'extract', and 'ledger' are present with an explicit 'Use when' phrasing, but common user synonyms such as 'TODO', 'follow-up', 'backlog', or 'pending' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The extractor-vs-reader niche (docs/outstanding-issues.md, '/ledger') is mostly distinct, but the generic word 'ledger' overlaps with the sibling branch-review ledger and its 'ledger:lookup'/'ledger:index' npm scripts acknowledged in the body, leaving minor conflict risk with a closely related tool.

4 / 5

Total

18

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

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