CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

subsystem-summary-of-test

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

Quality

66%

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

Quality

Content

71%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 dense, well-sectioned, fact-rich reference that is highly actionable for codebase-specific test work, with a clear numbered test-construction workflow and validation embedded via typed exceptions and framework assertions. Its main weakness is structural: it is a monolithic single-file API digest with no progressive disclosure into reference files, plus minor cross-section redundancy.

Suggestions

Split the per-component API listings (TxTests, TestAccount, TestUtils, fuzzing) into references/ files, keeping SKILL.md as an overview with clearly signaled one-level-deep links.

Trim the "Ownership and Relationships" section, which restates facts already covered in the earlier component sections.

Add one minimal copy-paste example of a canonical test (getTestConfig -> VirtualClock -> createTestApplication -> getRoot -> applyTx) to make the stated workflow fully executable.

DimensionReasoningScore

Conciseness

Nearly every line is codebase-specific fact Claude cannot know (e.g., "`applyCheck(tx, app, checkSeqNum)` — The core test-apply function. Closes a ledger, then in a `LedgerTxn`: validates tx...") with no padding explaining general concepts — anchor 4. Not 5 because there is minor redundancy: "Ownership and Relationships" restates facts already given ("`TestAccount` holds a reference to `Application&`" appears in both the TestAccount section and the ownership section), and "How Tests Are Structured and Run" partially repeats earlier helper descriptions. Not 3 because there is no concept over-explanation to trim.

4 / 5

Actionability

Concrete, specific guidance throughout: "get config via `getTestConfig()`, create `VirtualClock`, create `TestApplication` via `createTestApplication()`" and "Build operations (e.g., `payment()`, `createAccount()`), wrap in `transactionFromOperations()`, apply with `applyTx()` or `closeLedger()`" give exact API names in executable sequences — anchor 4. Not 5 because there is no copy-paste-ready code example of a canonical test; not 3 because the guidance names real functions and behaviors rather than pseudocode.

4 / 5

Workflow Clarity

The "How Tests Are Structured and Run" section gives a numbered 1-8 sequence from setup through version iteration, error testing, and Soroban, with a validation checkpoint in "Operations that should fail throw typed exceptions from `TestExceptions.h`; use `REQUIRE_THROWS_AS(...)`" plus framework-embedded verification ("`applyTx`... Calls `throwIf` on failure") — anchor 4. Not 5 because there is no explicit verify-before-proceeding guidance or error-recovery loop for the reader. Not 3 because checkpoints are present (typed-exception assertions, framework-thrown errors) and the sequence is well defined.

4 / 5

Progressive Disclosure

The skill is a monolithic single file (~280 lines, no references/, scripts/, or assets/ exist), and full per-component API listings such as the entire "## TxTests" catalog of operation builders are inlined in SKILL.md rather than split into one-level-deep reference files — matching anchor 3 (some structure, content that should be separate is inline). Not 4 because none of the detailed material is externalized; not 2 because the ##/### section structure is strong and navigable, not minimal or buried.

3 / 5

Total

15

/

20

Passed

Description

45%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 its domain and deliverable but provides only a generic action ("summary") and no explicit trigger guidance, capping completeness at 3. It is serviceable for disambiguating among sibling subsystem summaries but weak as a standalone trigger description.

Suggestions

Add an explicit trigger clause, e.g., "Use when asked about stellar-core's test framework, test helpers (TestAccount, TxTests, TestMarket), Catch2 integration, or how tests are structured and run."

Replace the generic "summary" with concrete scope: "Summarizes the src/test/ utilities: Catch2 integration, TestAccount account wrapper, TxTests operation builders and apply helpers, TestMarket, TestExceptions, and fuzzing infrastructure."

Include natural trigger variations users would actually say ("tests", "test utilities", "write a test", "Catch2", "applyTx") so the description surfaces on real queries.

DimensionReasoningScore

Specificity

The only action stated is a generic deliverable: "a token-efficient summary of the test subsystem" — it names the domain ("test subsystem") but lists no concrete capabilities (test framework, helpers, utilities, Catch2, TestAccount, TxTests are all absent from the description). It matches anchor 2 ("Names the domain but actions are minimal or generic") rather than 3, which requires 1-2 concrete actions, and is above 1 because a specific domain is named.

2 / 5

Completeness

The "what" is stated ("a token-efficient summary of the test subsystem") but the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because no "when" is present even weakly; not 2 because the "what" is explicit rather than vague.

3 / 5

Trigger Term Quality

"summary" and "test subsystem" include the natural term "test", but the description misses common variations users would actually say: "tests", "test utilities", "test helpers", "how tests work", "Catch2", or "applyTx". "token-efficient" is a benefit claim no user would utter as a trigger. Some relevant keywords exist (anchor 3) but coverage of synonyms is missing, so not 4.

3 / 5

Distinctiveness Conflict Risk

"the test subsystem" scopes the skill to one specific subsystem of the codebase (distinguishing it from sibling subsystem-summary skills), but the keyword "test" is broad and risks triggering on general test-writing or test-debugging questions that this infrastructure summary does not serve. Somewhat specific with residual overlap risk (anchor 3); not 4 because the generic "test" term creates real overlap with other test-related skills.

3 / 5

Total

11

/

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