ledger-tasks-yylo

Comprehensive guide for using YYLO Ledger task management without bypassing controller routing, lifecycle state, or mutation receipts. Covers task commands, dependency management, best practices, and workflow patterns. Use when you need to interact with the YYLO Ledger board.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./builtin-skills/skills/ledger-tasks-yylo/SKILL.md

Quality

Content

77%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 highly actionable, well-sequenced CLI reference with strong validation checkpoints on destructive operations. Its weaknesses are repeated guardrail guidance across sections and a monolithic single-file structure that would benefit from splitting detail into reference files.

Suggestions

De-duplicate the preflight/read-state/preserve-receipts rules: state them once in 'Supported task contract' and reference that section from the intro and Best Practices instead of restating.

Move time-sensitive/version-specific notes (e.g. 'Ledger 0.3.x exposes...') into a clearly labeled compatibility/version section so they can be maintained without bloating the core reference.

Split the bulky archive-pack, controller-routing, and environment-variable sections into separate reference files (e.g. ARCHIVE.md, ROUTING.md) and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference material assuming Claude's competence, but the preflight/read-state/preserve-receipts guidance is repeated across the intro, 'Supported task contract', and 'Best Practices', and version-specific statements ('Ledger 0.3.x exposes...') sit outside any 'deprecated/old patterns' section — more than minor trimming needed.	3 / 5
Actionability	Every command group ships copy-paste-ready invocations with concrete options and filters (e.g. 'yy ledger mark done --id TASK_ID --response "..." --commit abc123def'), fully covering the common cases.	5 / 5
Workflow Clarity	Destructive/batch flows are explicitly sequenced with validation checkpoints and feedback loops — the archive-pack section requires preflight + owner authorization + clean repo/index, independent inspection of the plan, and 'fail closed: discard the plan, resolve the conflict, and plan again' on stale-plan/conflict; the merge flow is dry-run plan → review → apply → retain receipt.	5 / 5
Progressive Disclosure	Section headers give reasonable structure, but this 177-line SKILL.md inlines large blocks that clearly belong in separate reference files (immutable archive packs, controller routing, env vars) and signals zero external references — no bundle files exist — so it lands at 'some structure, content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

73%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 solid, niche-specific description that clearly states both what it covers and when to use it, with low conflict risk. It is held back from the top tier by generic 'covers/using' verbs and a 'when' clause that could name more concrete trigger situations.

Suggestions

Replace generic verbs ('guide for using', 'covers') with concrete actions, e.g. 'Create, list, search, and mark tasks; manage dependencies and archive cold packs via the yy ledger CLI.'

Sharpen the 'when' clause with specific triggers, e.g. 'Use when adding or updating tasks, resolving blockers, ordering parallel work, or planning archive packs in the YYLO Ledger board.'

Add 'kanban'/'board' as trigger synonyms since those terms appear in the body and are natural user phrasing.

Dimension	Reasoning	Score
Specificity	It names the YYLO Ledger domain and lists several coverage areas ('task commands, dependency management, best practices, and workflow patterns'), but the verbs are generic ('guide for using', 'covers') rather than concrete actions like extract/fill/merge, so it sits at the domain-plus-actions-but-not-comprehensive anchor rather than above.	3 / 5
Completeness	Both halves are present — a 'what' ('Comprehensive guide for using YYLO Ledger task management... Covers...') and an explicit 'when' ('Use when you need to interact with the YYLO Ledger board.'), but the 'when' trigger is fairly generic and could be more specific, matching the both-present-but-when-could-be-sharper anchor.	4 / 5
Trigger Term Quality	It surfaces natural product terms a user would say ('YYLO Ledger', 'task management', 'dependency management', 'interact with the YYLO Ledger board') with good coverage, missing only a few synonyms like 'kanban'/'board' that appear in the body.	4 / 5
Distinctiveness Conflict Risk	The 'YYLO Ledger' niche is highly product-specific with distinct triggers ('YYLO Ledger board', 'controller routing', 'mutation receipts'), making conflict with other skills minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: iflytek/skillhub
Path: builtin-skills/skills/ledger-tasks-yylo/SKILL.md
Commit: 7352597

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.