CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hephaestus-storm

Use when the user types /hep-storm, mentions @Hephaestus storm, or asks to force-robustly drive a loop-worthy goal (apps, sites, agents, automations, debugging, multi-step research, data/report generation) to a verified finish. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs a verifier-first loop that does not stall, run away, or claim false success. Trivial questions are answered directly, not stormed.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%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-sequenced execution protocol whose strength is its verifier-first workflow with explicit bounded-repair and final-gate checkpoints, and whose shell commands are largely copy-paste ready. Weaker spots are duplicated rationale across sections and a few operational mechanisms (goal ledger, evidence hashing) left unspecified.

DimensionReasoningScore

Conciseness

Nearly all content is proprietary runner knowledge Claude cannot already know (resolution paths, hep-storm/hep-call invocations, route-decision semantics), so tokens are largely earned. Minor trimmable redundancy: §6 'Loop invariants' restates §5's bounded-retry/stall/ceiling rules, the intro paragraph repeats the description, and 'no fake pass' appears in both §5.5 and §7. Anchor 4 fits; not 5 because of that duplication, not 3 because padding is minor.

4 / 5

Actionability

Copy-paste shell snippets cover runner resolution, auth, fabric generation, and hep-call, and §4 gives a concrete action per route_decision value. Gaps keep it from 5: the 'goal ledger' has no specified location or format, 'hash-validated artifact evidence' has no command, and success/blocked report formatting is only implied.

4 / 5

Workflow Clarity

Sections 1-7 form an explicit sequence (resolve -> bootstrap -> auth -> route -> branch -> loop -> report) with strong validation checkpoints: verify requires an independent verifier and hash-validated evidence, repair is bounded with stall detection and an iteration ceiling, and the final gate gates success on can_report_success with §7 mandating 'blocked or unverified with the exact next step'. This matches the anchor-5 validate-fix-revalidate pattern with feedback loops.

5 / 5

Progressive Disclosure

The body references no external files and no bundle files exist, so there is no buried or nested-reference problem, and numbered sections make navigation easy. However, at ~175 monolithic lines (runner-resolution script, route table, and full loop protocol all inline), it sits at anchor 4 rather than 5, which would expect either a leaner overview or well-signaled one-level-deep references.

4 / 5

Total

17

/

20

Passed

Description

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

A well-formed description that explicitly covers both what the skill does and when to use it, anchored to a distinctive branded command. Its main weakness is trigger phrasing that leans on internal jargon ("force-robustly", "loop-worthy goal") rather than words a user would naturally type.

Suggestions

Add one or two natural-language trigger phrases users would actually type, e.g. "or asks to build/finish a multi-step project end-to-end with verification" instead of only "force-robustly drive a loop-worthy goal".

Replace or gloss one jargon term in the 'what' sentence, e.g. "materializes a dependency-ordered pipeline fabric" -> "breaks the goal into a dependency-ordered pipeline of work packets", so the capability is concrete to a reader outside the Agentlas ecosystem.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs a verifier-first loop"), but the actions are wrapped in branded jargon like "pipeline fabric" that keeps them from being fully concrete. It is well above anchor 3's 1-2 actions, but below anchor 5's plain-language comprehensive coverage.

4 / 5

Completeness

It explicitly answers 'when' with concrete triggers ("Use when the user types /hep-storm, mentions @Hephaestus storm, or asks to...") and separately answers 'what' (routes, materializes, runs a verifier-first loop, trivial questions answered directly). Both halves are explicit and specific, matching the anchor-5 example pattern; anchor 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

The explicit triggers "/hep-storm" and "@Hephaestus storm" are strong, but the natural-language trigger "asks to force-robustly drive a loop-worthy goal" is jargon no user would actually say, and the domain list (apps, sites, debugging, research) lacks common synonyms. This matches anchor 3 (relevant keywords present, common variations missing); anchor 4 would require natural phrases users genuinely utter.

3 / 5

Distinctiveness Conflict Risk

The branded command and Agentlas/Hephaestus naming give it a clear niche, and "Trivial questions are answered directly, not stormed" limits false triggers. Minor overlap risk remains because the broad domain list (apps, sites, agents, automations, debugging, multi-step research, data/report generation) touches general dev and research skills.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

agentlas-ai/Agentlas-OS

Path

openclaw/skills/hephaestus-storm/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.