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

81%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 delivers an exceptionally well-sequenced protocol with explicit validation gates, error-recovery loops, and concrete tool signatures, but it is a ~430-line monolith that inlines material (receipt schemas, executor transport contract, a dated incident report) that belongs in separate reference files, and its repetitive truthfulness restatements inflate token cost. Structure and actionability are high; organization across files and tightness are the gaps.

Suggestions

Split the detailed material into one-level-deep reference files and link them from the body — e.g. references/receipt-schema.md for the section 7 field list and references/host-executor.md for the stdin/stdout transport contract — keeping SKILL.md as a lean overview with the tool sequence and decision rules.

Cut the dated incident anecdote ('Measured 2026-09-24: a Codex session...') and inline version pins down to the durable rule they illustrate, or move them to a dedicated 'old patterns / known pitfalls' section, and consolidate the repeated never-fabricate/never-echo constraints into one truthfulness section referenced from the workflow steps.

Add one complete worked example of a compact decision object (selectionSessionId, decisionAuthor, assignments with candidateOrdinal and reason codes) and the resulting acceptance, so the most common authoring path is demonstrated rather than only specified.

DimensionReasoningScore

Conciseness

The body is dense, domain-specific protocol with no explanations of concepts Claude already knows, but it could be meaningfully tightened: truthfulness constraints ('never fabricate', 'do not echo') are restated across sections 3, 6, and 7, and it carries time-sensitive material — the dated incident anecdote 'Measured 2026-09-24: a Codex session probed the invented ... runtime 1.2.49' and version pins like '2026-08-20.1' — outside any deprecated/old-patterns section, which the guidelines say to penalize. This fits anchor 3 (mostly efficient, some tightening needed) rather than anchor 4, where only minor trims would be required.

3 / 5

Actionability

Guidance is largely executable: the exact typed MCP call sequence with signatures, a copy-paste bash runner-resolution script, the 'workforce execute' command, enumerated turn postures, and prescribed reason codes. It stops short of anchor 5 because there is no complete worked example of a compact decision/assignments payload or a filled receipt — the common cases are specified by signature and constraint rather than demonstrated end-to-end.

4 / 5

Workflow Clarity

The process is clearly sequenced in ordered sections (job analysis → menu retrieval and decision → validation and release pinning → goal binding → model policy → execution → truthful receipts) with explicit validation gates (validate_selection, digest recompute with fail-closed, validate_execution_receipt, the independent verifier) and genuine feedback loops ('Re-plan on rejection', resend the original decision when a receipt cannot restore bytes, the workforce_protocol_upgrade_required boundary path). This matches anchor 5.

5 / 5

Progressive Disclosure

There are no bundle files at all, so everything — including the full execution-receipt field list in section 7 and the host-executor transport contract — is inlined in one ~430-line SKILL.md. The clear '##' section headers and numbered steps keep it navigable (above anchor 2's headerless monolith), but content that clearly belongs in separate reference files is inline with no references, matching anchor 3.

3 / 5

Total

15

/

20

Passed

Description

82%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 an explicit and multi-form trigger clause and a clear, distinctive niche. The main weakness is specificity: it conveys one jargon-heavy core action and its properties rather than a comprehensive set of concrete capabilities a user could match against their needs.

Suggestions

Name 2-3 additional concrete capabilities in plain language (e.g. searching agent catalogs across Local/Cloud/Hub sources, validating and pinning exact agent releases, executing the staffed roster through the host runtime) so the 'what' is comprehensive rather than a single action.

Reduce internal jargon in the description ('durable goal', 'goal-bound roster') or pair each term with a plain-English equivalent so users outside the Agentlas ecosystem can recognize their need.

DimensionReasoningScore

Specificity

The description names the domain and one core concrete action — 'staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams' — plus mechanism statements like 'The active host LLM staffs each turn' and 'the exact roster remains goal-bound until explicit completion', but these are properties of one action rather than a list of several distinct actions, and they are wrapped in jargon ('durable goal', 'goal-bound'). It matches anchor 3: not the single comprehensive action catalog of anchor 4, but clearly more concrete than anchor 2's generic domain naming.

3 / 5

Completeness

It explicitly answers 'when' with concrete trigger phrases ('Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal...') and 'what' with the staffing action, the source scopes (Local/Cloud/Hub), the per-turn host-LLM staffing model, and the goal-bound roster lifetime. Both halves are explicit, matching anchor 5 rather than anchor 4's weaker 'when'.

5 / 5

Trigger Term Quality

Triggers include three command spellings ('$hephaestus-network, /hep-network, or /agentlas-network'), an '@Hephaestus' mention, and a natural phrase ('asks Agentlas to staff a durable goal'), giving good synonym coverage for command-based invocation. It falls short of anchor 5 because plain natural-language variants users might say — e.g. 'agent workforce', 'recruit/assemble a team', 'hire agents' — are absent, and it exceeds anchor 3 since multiple command forms and a natural phrase are covered.

4 / 5

Distinctiveness Conflict Risk

Exact command names and unique brand terms ('@Hephaestus', 'Agentlas', 'hephaestus-network') establish a clear niche with distinct triggers and minimal conflict risk against generic skills, matching anchor 5.

5 / 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

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