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 orchestration protocol with explicit validation gates, bounded retry semantics, and runnable commands — its workflow clarity is the standout strength. The weaknesses are token-hungry jargon narrative that pads the protocol, and verification guidance that names the requirement but rarely shows a concrete executable check.

Suggestions

Trim jargon-heavy narrative (the 'Core-owned Goal + UltraCode harness' preamble, 'first-contact contract' internals like 'soul memory / ontology runtime / CareerGraph', and the §6 'why this beats a one-shot loop' framing) to cut tokens without losing operational guidance.

Add one concrete example of the §5 'verify' step — e.g., a sample independent-verifier command or what 'hash-validated artifact evidence' looks like in practice — so executors can act rather than interpret.

Merge the overlapping §5 loop description and §6 loop invariants into a single section, keeping the stall/backoff/iteration-ceiling rules stated once.

DimensionReasoningScore

Conciseness

The body is mostly an efficient protocol with tight, runnable bash blocks, but it carries jargon-heavy narrative padding ('Core-owned Goal + UltraCode harness', 'canonical private project soul memory, code map, ontology runtime, CareerGraph') and a redundant 'why this beats a one-shot loop' section that restates §5 invariants. Tightening these would cut meaningful tokens without losing guidance.

3 / 5

Actionability

Concrete, copy-paste-ready bash for runner resolution, auth ensure, the hep-storm invocation, and hep-call borrowing, plus a specific action per route_decision.action branch. Minor gaps: the verify step describes 'an independent verifier and hash-validated artifact evidence' abstractly without a concrete command or example of what verification looks like.

4 / 5

Workflow Clarity

The workflow is clearly sequenced (resolve runner → sign-in → route/materialize → branch → run loop) with a 7-step loop containing explicit validation checkpoints (verify step, final-gate with can_report_success, 'No fake pass' rule) and genuine feedback loops (bounded repair/retry with backoff, stall detection, journal-based resume).

5 / 5

Progressive Disclosure

No bundle files exist; the ~175-line body is self-contained with clear numbered sections and a consistent structure, which suits a workflow protocol. It stays just under monolithic, though sections like the loop invariants and hard rules are borderline candidates for a reference file if the skill grows.

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 with explicit, concrete trigger phrases and a clear what/when split, including a useful trivial-vs-loop-worthy exclusion. Its main weakness is reliance on internal product jargon and a broad use-case list that slightly raises conflict risk.

DimensionReasoningScore

Specificity

The description 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' — but they are wrapped in product jargon ('force-robust', 'verifier-first hardened loop') rather than plain concrete verbs, leaving minor gaps in comprehensiveness.

4 / 5

Completeness

Both 'what' and 'when' are explicitly and concretely answered: an explicit 'Use when the user types /hep-storm...' trigger clause with concrete trigger phrases, a clear statement of what the loop does, and a scoping sentence ('Use it for loop-worthy work — ... Trivial questions are answered directly, not stormed').

5 / 5

Trigger Term Quality

Triggers are explicit and natural for this niche: '/hep-storm', '/agentlas-storm', '@Hephaestus storm <goal>', plus plain-language use cases ('apps, sites, agents, automations, debugging, multi-step research, data/report generation'). A few natural synonyms (e.g., 'storm a goal', 'run to done') are absent, keeping it just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The named slash commands and '@Hephaestus storm' phrase form a clear, distinct niche with minimal conflict risk, but the broad domain enumeration ('apps, sites, agents, automations, debugging, multi-step research') overlaps generic orchestration and delegation skills.

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

codex/plugins/agentlas-core-engine-meta-agent/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.