CtrlK
BlogDocsLog inGet started
Tessl Logo

subsystem-summary-of-herder

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

51

Quality

56%

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/subsystem-summary-of-herder/SKILL.md
SKILL.md
Quality
Evals
Security

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 well-structured, dense reference summary of the herder subsystem with clear sections, concrete file/class/method pointers, and sequenced control flows. It is strongest in conciseness and workflow clarity, but as a single inlined file it does not use progressive disclosure and offers reference rather than executable guidance.

Suggestions

Split the detailed class/data-structure catalog into a separate reference file (e.g. references/classes.md) and keep SKILL.md as a concise overview that links to it, improving progressive disclosure.

Add a brief "How to use this summary" line indicating the concrete actions this reference supports (e.g. locating code, tracing a ledger-close path) to boost actionability.

Trim any duplicated ownership/cache detail between the class catalog and the ownership diagram to tighten conciseness further.

DimensionReasoningScore

Conciseness

The body is a dense technical summary that assumes familiarity with stellar-core and SCP, with minimal padding or restating of concepts Claude already knows; only minor sections could be trimmed, fitting anchor 4.

4 / 5

Actionability

It provides concrete reference detail (specific file names, classes, methods, line counts, and constant values) useful for navigating the subsystem, but as a summary it describes rather than giving executable steps, matching anchor 3.

3 / 5

Workflow Clarity

The "Key Control Flows" section sequences startup, ledger close, envelope processing, and recovery as numbered steps with clear ordering; no validation checkpoints are needed since this is a non-destructive reference, fitting anchor 4.

4 / 5

Progressive Disclosure

The content is well-organized into clear sections but is a single monolithic ~290-line file with no external references or bundle files to split detail into, and the under-50-line simple-skill exception does not apply, matching anchor 3.

3 / 5

Total

14

/

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 clearly identifies a narrow niche (the herder subsystem) and what it provides, but it omits an explicit "when to use" trigger and uses imperative rather than third-person voice. Adding a "Use when..." clause and rephrasing as a capability would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about the stellar-core herder subsystem, SCP consensus, transaction queues, or quorum intersection."

Rephrase in third-person capability voice (e.g. "Summarizes the stellar-core herder subsystem...") instead of the imperative "read this skill".

Include broader natural terms like "stellar-core", "SCP", or "consensus" to improve trigger term coverage.

DimensionReasoningScore

Specificity

The phrase "token-efficient summary of the herder subsystem" names the domain and one action (summary), matching anchor 3, but the imperative "read this skill" is second-person voice rather than third person, so specificity is reduced by 1 per the rubric guideline.

2 / 5

Completeness

It states a clear "what" (a token-efficient summary of the herder subsystem) but has no explicit "Use when..." trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes relevant keywords ("herder subsystem", "summary") but lacks common variations, synonyms, or the broader "stellar-core" framing users might naturally say, fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

"herder subsystem" is a specific, well-scoped niche with minimal conflict risk, though it could overlap marginally with other stellar-core summary skills, fitting anchor 4.

4 / 5

Total

12

/

20

Passed

Validation

100%

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