Name: subsystem-summary-of-catchup
Rating: 51.2 (1 reviews)
Author: stellar

Blog Docs Log inGet started

subsystem-summary-of-catchup

read this skill for a token-efficient summary of the catchup subsystem

Quality

55%

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 ./.claude/skills/subsystem-summary-of-catchup/SKILL.md

Quality

Content

63%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 dense, well-organized technical reference with concrete class/method/flow detail and clear sequencing, which is effective for orienting Claude in the catchup subsystem. Its weaknesses are verbosity relative to its 'token-efficient summary' framing and a monolithic structure with no progressive disclosure into separate files.

Suggestions

Trim exhaustive data-member lists to the most important members per class, or move full member listings into a separate reference file that SKILL.md points to.

Introduce progressive disclosure: keep a concise overview in SKILL.md and link to per-class detail files (e.g. CatchupWork.md, VerifyLedgerChainWork.md) one level deep.

Add a brief 'How to use this summary' orientation line at the top so Claude knows when to consult which section.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient factual reference material, but the exhaustive per-class enumeration of every data member across ~326 lines could be tightened for a skill branded as a 'token-efficient summary', fitting the 3 anchor; it is not padded with known concepts (so not below 3) nor trim enough for 4.	3 / 5
Actionability	It gives highly concrete, specific guidance (exact file paths, method names, numbered control flow, invariants); per scoring_notes code absence is not penalized for a reference skill, but it stops short of fully copy-paste-ready material, so 4 rather than 5.	4 / 5
Workflow Clarity	Multi-step processes are clearly sequenced (numbered runCatchupStep/onRun steps, ASCII data-flow diagrams, an error-handling/invariants section); it is not a destructive or batch operation so no cap applies, and it falls just short of the explicit validate/fix/retry checklist level of 5.	4 / 5
Progressive Disclosure	The body is well-sectioned with clear headers but is a monolithic ~326-line single file with no external bundle files or one-level-deep references; content that could be split out (per-class member references) is inlined, matching the 3 anchor.	3 / 5
	Total	14 / 20 Passed

Description

46%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 clearly identifies its niche (the stellar-core catchup subsystem) and what it provides (a token-efficient summary), but it lacks explicit trigger guidance and relies on technical jargon rather than natural user phrasing. It is distinct but weak on when-to-use clarity.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks about or needs to modify the stellar-core catchup subsystem.'

Include natural trigger synonyms users might say, such as 'ledger catchup', 'history archive sync', or 'replay ledgers'.

Add a second concrete action beyond 'summary' (e.g. 'navigate', 'trace the catchup data flow') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('catchup subsystem') and one concrete action ('token-efficient summary'), matching the anchor for 1-2 concrete actions; it does not list several specific actions so it is not a 4.	3 / 5
Completeness	It clearly states the 'what' ('token-efficient summary of the catchup subsystem') but provides no explicit 'Use when...' trigger guidance, so per the boundary guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	'catchup subsystem' is technical jargon and 'summary' is generic; there are one or two keywords but no natural user phrases or synonyms, fitting the 2 anchor better than 1 (a relevant term exists) or 3 (which expects broader coverage).	2 / 5
Distinctiveness Conflict Risk	The catchup subsystem is a narrow niche with minimal conflict risk, but the jargon-only trigger and absence of 'Use when' phrasing keep it just below the clearly-triggered 5 anchor.	4 / 5
	Total	12 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: stellar/stellar-core
Path: .claude/skills/subsystem-summary-of-catchup/SKILL.md
Commit: 88d2431

Reviewed: 4 hours 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.