CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

subsystem-summary-of-util

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

Quality

70%

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-util/SKILL.md
SKILL.md
Quality
Evals
Security

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 well-organized, information-dense reference that is directly actionable and assumes the reader's competence, with clear data-flow narratives tying the modules together. Its main weakness is the absence of any progressive disclosure: ~350 lines of detailed reference sit entirely inline with no external files or navigation paths.

Suggestions

Split the body into one-level-deep reference files (e.g., references/timing.md, references/scheduler.md, references/data-structures.md) and keep SKILL.md as a compact overview with clearly signaled links, so only the relevant section loads into context.

Trim entries that restate common knowledge (e.g., CoutLogger's 'Writes to std::cout', NonCopyable's 'disable copy/move semantics via deleted special members') to name-only mentions.

Add one short, representative usage snippet per high-traffic area (e.g., VirtualTimer async_wait, bigDivideOrThrow, RandomEvictionCache put/get) to close the gap between reference detail and copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

The body is a dense catalog of function names with one-line behavioral notes (e.g., "bigDivide(result, A, B, C, rounding): Computes A*B/C safely when A*B would overflow int64_t") that names algorithms without re-explaining them; only minor entries restate knowledge Claude already has (e.g., the CoutLogger and NonCopyable bullets).

4 / 5

Actionability

Concrete specifics are pervasive — exact names, signatures, defaults, and constants ("latency window (default 5s)", "4-byte big-endian size header", "SOROBAN_PROTOCOL_VERSION = V_20") — letting a reader go straight to the right API; minor gaps remain since some sections are name-only lists with no usage examples.

4 / 5

Workflow Clarity

This is a single-purpose reference skill with no multi-step process and no destructive or batch operations, so the single consult action is unambiguous; the "Key Data Flows" section additionally gives correctly-ordered sequences (e.g., crank → timers → ASIO IO → Scheduler::runOne → pending-queue transfer).

5 / 5

Progressive Disclosure

Section structure is good (16 numbered, consistently formatted sections plus Key Data Flows), but there are no bundle files or references at all — the entire detailed per-module API reference is inlined in SKILL.md rather than split into one-level-deep reference files with a shorter overview.

3 / 5

Total

16

/

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 states a clear, appropriately narrow purpose but is thin: one generic action, weak trigger coverage, and no explicit use-when guidance. It is distinctive because of its domain specificity, yet it undersells what the summary actually contains.

Suggestions

Enumerate the concrete coverage in the description, e.g., 'Summarizes the util subsystem: virtual clock and timers, fair scheduler, logging, safe numeric operations, filesystem and XDR I/O, caches, threading utilities, and metrics.'

Add an explicit trigger clause, e.g., 'Use when the user asks about src/util, the util subsystem, or specific utilities such as VirtualClock, Scheduler, Logging, or bigDivide.'

Include natural keyword variants users would type — 'src/util', 'utilities', 'overview' — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names its domain ("the util subsystem") but offers only one generic action ("token-efficient summary") without enumerating any of the concrete areas it covers (timing, logging, data structures, etc.), matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

The "what" is clear (a token-efficient summary of the util subsystem), but the "when" is only weakly implied by "read this skill for" — there is no explicit "Use when..." clause, which the rubric caps at 3.

3 / 5

Trigger Term Quality

"util subsystem" and "summary" are natural phrases a user would say, but common variations and synonyms are missing — e.g., "src/util", "utilities", "overview", or recognizable file/module names like Timer or Scheduler.

3 / 5

Distinctiveness Conflict Risk

"The util subsystem" is a specific niche within a specific codebase with minimal overlap risk, though it could collide with sibling subsystem-summary skills and lacks explicit trigger phrases to fully disambiguate.

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

Path

.claude/skills/subsystem-summary-of-util/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.