CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hephaestus-network

Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./hermes/skills/hephaestus-network/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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, expert-level protocol skill with a genuinely clear seven-step workflow, explicit typed tool calls, and unusually strong fail-closed validation discipline throughout. Its weaknesses are length and shape: ~440 lines of inline prose with repeated boundary restatements, and everything — including contract details and receipt schemas that belong in reference files — lives in a single monolithic body with no progressive disclosure.

Suggestions

Split contract-level detail into one-level-deep reference files (e.g. references/receipt-schema.md for the agentlas.workforce-execution-receipt.v2 field list, references/host-executor.md for the adapter stdin/stdout contract) and keep SKILL.md as the workflow overview with clear pointers.

Tighten the repeated boundary restatements: rules like 'do not echo the compiled WorkOrder', 'Core will not choose for you', and 'never fabricate telemetry' each appear multiple times across sections — state each once in the section where it applies.

Add one short worked example showing a complete decision object (compact decision with reason codes) or a minimal receipt, so the placeholder-heavy tool sequence becomes copy-paste-usable for the common case.

DimensionReasoningScore

Conciseness

The body is composed almost entirely of domain-novel protocol rules rather than concepts Claude already knows, so it is not padding in the anchor-1/2 sense. However, ~440 lines of dense prose repeatedly restate the same boundaries ('do not echo', 'Core will not choose for you', 'never fabricate') and stack many rules into single long paragraphs that could be materially tightened.

3 / 5

Actionability

Concrete guidance is strong: an exact typed MCP call sequence with parameter names, an executable runner-resolution bash block, and a copy-pasteable workforce execute command. It stops short of 5 because arguments are placeholders (taskBrief=..., roles=...) and reason codes / receipt fields are described but never shown in a worked example.

4 / 5

Workflow Clarity

The seven numbered sections give a clear pipeline (job analysis → menu retrieval → validation/pinning → goal binding → model policy → execution → receipts) with explicit fail-closed checkpoints and re-plan loops ('Re-plan on rejection', 'recompute its canonical digest before execution and fail closed on mismatch'). Not a 5 because the mainline sequence is frequently interrupted by long inline policy digressions, making the critical path harder to follow.

4 / 5

Progressive Disclosure

There is real section structure, which lifts it above a 2, but no bundle files exist at all — the detailed receipt schema field list, the host-executor stdin/stdout contract, and the model-allocation policy rules are all inlined in one monolithic SKILL.md instead of split into one-level-deep reference files.

3 / 5

Total

14

/

20

Passed

Description

73%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 strongly distinctive description with explicit, concrete 'Use when…' triggers based on literal command aliases, which is exactly what an invocable command skill should provide. Its weakness is on the 'what' side: the capability description is compressed into ecosystem jargon (durable goal, goal-bound roster, Local/Cloud/Hub sources), so a reader outside this system cannot tell what the skill concretely does.

Suggestions

Add one plain-English sentence naming the concrete actions the skill performs, e.g. 'searches federated agent catalogs, selects a roster, and runs it as native sub-agents', instead of only 'staffs each turn'.

Pair the command-name triggers with one or two natural-language phrasings a non-expert user might say (e.g. 'hire/find agents for a long-running task') to broaden trigger coverage beyond users who already know the command names.

DimensionReasoningScore

Specificity

The description names the domain ('staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams') and one or two concrete actions ('The active host LLM staffs each turn'), but never plainly enumerates the concrete operations the skill performs. It is not a 4 because there is no list of several specific actions, only a jargon-dense characterization.

3 / 5

Completeness

Both parts are present: an explicit 'Use when…' clause with concrete trigger phrases (strong 'when') and a 'what' ('the active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion'). Not a 5 because the 'what' is jargon-heavy and does not clearly convey what the skill actually does for someone outside this ecosystem.

4 / 5

Trigger Term Quality

Command-alias coverage is excellent and literal ('$hephaestus-network, /hephaestus-network, /agentlas-network, @Hephaestus'), matching exactly what a user would type. It falls short of 5 because beyond the command names, natural everyday phrasings are missing — an uninitiated user would not naturally say 'staff a durable goal' or know the Local/Cloud/Hub vocabulary.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive: unique command names ($hephaestus-network, /agentlas-network) and a narrow niche (agent workforce staffing with goal-bound rosters) mean minimal risk of triggering for the wrong skill. The neighbor anchor 4 ('minor overlap risk') fits less well because no other skill would plausibly share these triggers.

5 / 5

Total

16

/

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