CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hephaestus-storm

Use when the user types /hep-storm or /agentlas-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.

Quality

83%

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

The canonical home for this skill is hephaestus-storm in agentlas-ai/Agentlas-OS

SKILL.md
Quality
Evals
Security

Quality

Content

73%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-sequenced, verifier-first workflow with executable commands, explicit validation gates, and repair loops that earns top workflow-clarity marks. It loses points on token efficiency from marketing framing, repeated invariants, and an unrelated update note, and it keeps everything in one file where a couple of bundles would ease the load.

Suggestions

Cut the comparative marketing framing ('Unlike a one-shot answer or a generic parallel fan-out', 'why this beats a one-shot loop') and the §6 invariants that restate the description's 'does not stall, run away, or claim false success' verbatim.

Remove or relocate the unrelated Korean 'Update fallback' note at the top of the body — it is off-topic for the storm loop and adds tokens without operational value.

Move the multi-line runner-resolution script and the route-decision reference table into scripts/ or references/ bundle files linked one level deep, slimming SKILL.md to the orchestration overview.

DimensionReasoningScore

Conciseness

Phrases like 'Unlike a one-shot answer or a generic parallel fan-out' and 'why this beats a one-shot loop', plus the invariant list restating 'does not stall, run away, or claim false success' already stated twice, are padding Claude doesn't need; the unrelated Korean 'Update fallback' note at the top adds noise. The operational core (runner resolution, routing, loop steps) is efficient, so this is mostly-tightened-with-excess rather than severely verbose.

3 / 5

Actionability

Concrete, executable bash blocks dominate ('Run this resolution in a shell...', the auth ensure snippet, the hep-storm/hep-call invocations) with copy-paste-ready commands and an installer URL. Minor gaps: engine-output fields like 'loop.goal_command' and 'can_report_success' are consumed but how to inspect them is left implicit, and steps 1–3 of the loop are directive prose rather than commands — fits the 'mostly executable with minor gaps' anchor, not the 5's fully-covered common cases nor the 3's pseudocode.

4 / 5

Workflow Clarity

A clearly numbered §1–§7 sequence with explicit validation checkpoints ('verify — A packet passes only with separately attributable, validated verification', 'final-gate — Report success only if the fabric's final gate clears'), a bounded repair/retry feedback loop with backoff and stall detection, and a checklist-style route-decision branch table. This matches the top anchor; the sequence, error-recovery loop, and checkpoints are all explicit, so it is not the 4 anchor with 'minor validation gaps'.

5 / 5

Progressive Disclosure

The body is well-sectioned with a coherent single-file structure and no nested-reference chains (verified: no references/, scripts/, or assets/ directories exist). Minor gaps keep it below the 5 anchor: ~175 lines with inlinable-heavy blocks like the multi-line runner-resolution script and route-decision table that could live in bundle files, and no one-level-deep references at all — but structure and navigation are solidly good, not 'some structure that could be better organized'.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong description that explicitly answers what and when with concrete, natural trigger phrases and distinct slash-command triggers. Its only deductions are branded jargon in the capability statements and a broad use-domain list that slightly overlaps general orchestration skills.

DimensionReasoningScore

Specificity

It lists several concrete actions — 'routes the goal to real Agentlas specialists', 'materializes a dependency-ordered pipeline fabric', 'runs each work packet as a verifier-first hardened loop' — matching the 'several specific actions; minor gaps' anchor. Not a 5 because the actions are wrapped in branded jargon rather than plain capabilities, and 'Trivial questions are answered directly' is scoping rather than a capability; not a 3 because coverage goes well beyond 1–2 actions.

4 / 5

Completeness

Both halves are explicit and concrete: 'when' opens the description ('Use when the user types /hep-storm or /agentlas-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion') and is reinforced by 'Use it for loop-worthy work — apps, sites, agents, automations, debugging...'; 'what' follows immediately with the routing/fabric/hardened-loop capabilities and the boundary ('Trivial questions are answered directly, not stormed'). This is the top anchor — clear what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrasing is present and specific: '/hep-storm', '/agentlas-storm', '@Hephaestus storm <goal>', plus use-domains like 'apps, sites, agents, automations, debugging, multi-step research, data/report generation' — good keyword coverage. It misses a few natural synonyms a user might say ('run this to completion', 'goal loop', 'agent pipeline'), so it fits the 4 anchor rather than the 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The slash commands and '@Hephaestus storm <goal>' phrasing form a distinct niche with minimal wrong-skill trigger risk. It stays at 4 rather than 5 because the broad use-domain list ('apps, sites, agents, automations, debugging, multi-step research') overlaps with general-purpose development and orchestration skills, creating minor conflict risk if the explicit commands are absent.

4 / 5

Total

17

/

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

agentlas-ai/Agentlas-OS

Path

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