subsystem-summary-of-history

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

Quality

48%

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-history/SKILL.md

Quality

Content

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

This is a thorough, well-structured technical reference for the history subsystem rather than an actionable skill: it excels at describing classes and data flows but offers no executable guidance and inlines all detail with no progressive disclosure. Its strength is clarity of system structure; its weakness is actionability and file-level organization.

Suggestions

Add an actionable 'How to use this summary' section with concrete next steps or commands a user might run after reading (e.g., inspecting the publish queue, verifying an archive).

Move the per-class member and method detail into reference files (e.g. references/classes.md) and keep SKILL.md as an overview with one-level-deep links, improving progressive disclosure.

Trim exhaustive member/signature listings to the essentials needed to understand behavior, reducing token cost.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and specific to this codebase (class names, methods, atomicity model) without padding with concepts Claude already knows, but at ~267 lines it is long for a SKILL.md and could be tightened in places such as the exhaustive member/signature listings.	3 / 5
Actionability	It provides concrete reference information (specific class and method names) but only describes the system rather than instructing any executable action; there are no commands, code, or steps for Claude to perform.	2 / 5
Workflow Clarity	The 'Key Data Flows' sections (Checkpoint Construction, Publication Pipeline, Crash Recovery, Catchup) present clearly numbered, well-sequenced steps with implicit checkpoints and a crash-recovery validation flow, with only minor explicit-validation gaps.	4 / 5
Progressive Disclosure	The document is well-organized into clear sections but is a single 267-line monolith with no bundle files and no references to separate files, so class-detail content that could live in reference files is inlined.	3 / 5
	Total	12 / 20 Passed

Description

48%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 names a specific domain and a concrete action but omits any explicit 'when to use' guidance and uses second-person imperative voice instead of third person. It is recognizable but would benefit from a trigger clause and rephrasing.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks for a summary of the history subsystem or needs to understand its checkpoint/publication mechanics.'

Rephrase in third person ('Summarizes the history subsystem...') instead of the imperative 'read this skill for...'.

Include natural trigger synonyms such as 'history archives', 'checkpoints', or 'publish queue' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'token-efficient summary of the history subsystem' names the domain and a single concrete action (summarize), but it is framed as the second-person imperative 'read this skill for...' rather than third-person voice, so the specificity score is reduced by one per the voice guideline.	2 / 5
Completeness	It conveys a clear 'what' (a token-efficient summary of the history subsystem) but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3.	3 / 5
Trigger Term Quality	It includes the relevant keyword 'history subsystem' and 'summary', but lacks common variations or synonyms a user might naturally say, and offers no natural trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	'history subsystem' denotes a fairly distinct niche unlikely to trigger for unrelated skills, though the term is generic enough to carry minor overlap risk with other subsystem-summary skills.	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-history/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.