CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

subsystem-summary-of-soroban-env

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

Quality

68%

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-soroban-env/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.

The body is an exceptionally dense, fluff-free technical summary that fully delivers on the description's promise of token efficiency. Its weaknesses are structural and functional: everything lives in one long file with no progressive disclosure, and it is purely descriptive reference material with no executable or usage-oriented guidance.

Suggestions

Split per-crate detail (soroban-env-common types/traits, soroban-env-host internals) into one-level-deep reference files, keeping SKILL.md as a short overview with clearly signaled links.

Add a brief 'how to use this summary' orientation — e.g., which sections to consult for common tasks (tracing a host-function call, budget questions, auth checks) — to convert descriptive content into actionable navigation.

Move version-sensitive facts (MIN_LEDGER_PROTOCOL_VERSION = 26, protocol ≥22 constructor rule) into a clearly labeled version/protocol section so future protocol bumps don't silently invalidate the summary.

DimensionReasoningScore

Conciseness

The body is a dense, factual reference — every line carries codebase-specific detail (tag ranges, struct fields, method signatures like 'Host::try_finish() consumes the host', fuel-bridge semantics) that Claude cannot know from general knowledge. There is no padding, no tutorial prose, and no explanation of concepts Claude already knows, matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

Concrete anchors are plentiful — file paths ('val.rs', 'host.rs', 'budget.rs'), exact type/method names ('add_host_object<HOT>', 'Budget::charge(ty, input)'), and numbered control flows — but the document describes the system rather than instructing how to use or act on it; there are no runnable commands, code examples, or usage patterns. This fits 'Some concrete guidance but incomplete' better than 4's 'mostly executable guidance' since nothing here is directly executable.

3 / 5

Workflow Clarity

The 'Key Control Flows' section presents clearly sequenced, coherent step lists (contract invocation 1-10, object lifecycle, budget flow) with correct ordering and causal links. No validation checkpoints are needed for a read-only knowledge skill, so the missing-checkpoint penalty for risky operations does not apply; it is not 5 because there are no feedback/checkpoint patterns at all and the steps describe the system's runtime, not a guided procedure.

4 / 5

Progressive Disclosure

The single SKILL.md has no bundle files (no references/, scripts/, or assets/ exist) and inlines ~290 lines of per-crate detail that could naturally be split (e.g., soroban-env-common vs. soroban-env-host into separate reference files). Section headers are clear and well-organized, but all depth is monolithically inline with no one-level-deep references, fitting 'Some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

15

/

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 identifies a clear, specific niche (the soroban-env subsystem) but does minimal work: it states a single generic action (provide a summary) and completely omits when the skill should be used. It reads more like a file label than a trigger-ready skill description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with the soroban-env crates (soroban-env-common, soroban-env-host), Soroban host internals, Val/host object handling, budgets, or dispatch in the Stellar/Soroban codebase.'

Enumerate 2-3 concrete capabilities instead of the generic 'summary', e.g. 'Summarizes the host-guest ABI (Val, tags, wrappers), the Host runtime (frames, storage, budget, auth), and Wasm dispatch/control flows.'

Include natural synonyms and crate names users would actually type — 'soroban environment', 'soroban-env-host', 'Stellar smart contract runtime' — to improve trigger matching.

DimensionReasoningScore

Specificity

The description names the domain ("the soroban-env subsystem") but the only action is the generic "read this skill for a token-efficient summary" — it enumerates no concrete capabilities (e.g., what aspects of the subsystem it covers). This matches the anchor 'Names the domain but actions are minimal or generic' ('Processes PDF files'), and falls short of score 3 because no specific actions beyond 'summary' are listed.

2 / 5

Completeness

The 'what' is present and clear ('a token-efficient summary of the soroban-env subsystem'), but there is no 'when' clause or equivalent trigger guidance — per the judging guidelines, a missing 'Use when...' clause caps completeness at 3. It is not 4 because nothing indicates when Claude should load this skill.

3 / 5

Trigger Term Quality

It contains a relevant, specific keyword ('soroban-env') plus 'summary', but misses natural variations and synonyms a user might say ('soroban environment', 'Stellar smart contracts', 'env host', 'soroban-env-host'). This fits 'Some relevant keywords but missing common variations or synonyms'; not 4 because coverage of natural phrasings is thin, not 2 because 'soroban-env' is far more targeted than generic language like 'Works with files'.

3 / 5

Distinctiveness Conflict Risk

'soroban-env subsystem' is a distinct niche with minimal conflict risk against unrelated skills. It is not 5 because the description lacks explicit trigger phrases that would cleanly distinguish it from other codebase-summary skills, and not 3 because the named domain is highly specific rather than merely 'somewhat specific'.

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-soroban-env/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.