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 rigorous, well-sequenced protocol with concrete commands and validation at every gate, but it is a monolith: ~440 lines of dense inline contract detail with no progressive disclosure, notable repetition of policy boundaries, and dated version/incident material embedded in the main flow. Splitting reference material into bundle files and consolidating repeated guardrails would cut its context cost significantly without losing actionability.

Suggestions

Move the receipt field inventory (section 7) and the host-executor transport contract (section 6) into references/ files, keeping SKILL.md as a concise overview with clearly signaled one-level-deep pointers.

Consolidate the fail-closed digest rules, 'never picks for you', and no-echo-of-rejected-data statements that recur across sections 2-7 into a single validation-boundaries section to remove redundant tokens.

Relocate dated material ('Measured 2026-09-24...', runtime 1.2.49, protocol 2026-08-20.1) into an old-patterns/compatibility note so the main workflow stays evergreen.

DimensionReasoningScore

Conciseness

Every paragraph is domain-specific contract detail with no padding about concepts Claude already knows, but ~440 lines could be tightened substantially: policy boundaries repeat across sections (e.g. fail-closed digest rules in section 3 reappear in sections 6-7, and 'Core... never picks for you' is restated in sections 3 and 4), and time-sensitive material ('Measured 2026-09-24: a Codex session...', 'runtime 1.2.49', '_meta.protocolVersion is at least 2026-08-20.1') sits in the main flow rather than a notes/deprecated section. Not 4 because the redundancy and length go beyond minor trimming; not 2 because none of it explains general knowledge.

3 / 5

Actionability

Two fully executable bash blocks (the runner-resolution loop and the 'workforce execute --project ... --goal-id ...' command) plus an exact ordered MCP call sequence with named parameters ('workforce.preflight_work_order(taskBrief=..., roles=..., edges=...)') and concrete response fields to read ('unmetRequirementCount', 'pendingExecution'). Not 5 because parameter values are ellipsized placeholders and a fair portion of the guidance is abstract policy assertion ('report a failed action without widening its authority') rather than an executable step; not 3 because the concrete commands, exact tool names, and field-level instructions are far more complete than pseudocode.

4 / 5

Workflow Clarity

A numbered macro sequence ('## 1. Perform job analysis' through '## 7. Truthful receipts') preceded by runner/session setup, with explicit validation gates at every stage (preflight boundary check, validate_selection, 'recompute its canonical digest before execution and fail closed on mismatch', validate_execution_receipt) and genuine feedback loops ('Re-plan on rejection', 'either accept the gap on purpose or pick a different candidate'). Not 4 because checkpoints are not merely 'mostly present' — validation is the spine of the workflow and error recovery is explicit at each gate.

5 / 5

Progressive Disclosure

Section headers give the document real structure, but all ~440 lines live inline in SKILL.md with no bundle files at all (no references/, scripts/, or assets/ directories exist); the receipt field inventory in section 7, the host-executor stdin/stdout contract in section 6, and the stage-role mapping table in section 5 are exactly the content that belongs in one-level-deep reference files. Not 4 because content that clearly should be separate is inline with zero reference pointers (the only external mention, 'agentlas_cloud/workforce/host_executor.py', points into the installed engine, not a bundle); not 2 because headers and a coherent section order provide navigable structure rather than a header-less wall.

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.

The description is exemplary on triggers, completeness, and distinctiveness — explicit 'Use when...' phrasing with exact command aliases and an unambiguous capability statement. Its one weakness is specificity: the 'what' is compressed to a single staffing clause and omits the analysis, selection, execution, and receipt work the skill actually performs.

Suggestions

Lead with one sentence enumerating the core capabilities (analyze the task, search and select candidates across Local/Cloud/Hub, pin exact releases, execute and verify) so the 'what' is as specific as the 'when'.

Replace jargon-bound phrasing like 'The active host LLM staffs each turn' with plain capability verbs a first-time reader can parse without knowing the Agentlas ecosystem.

DimensionReasoningScore

Specificity

The description names the domain and 1-2 concrete actions — 'staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams' and 'The active host LLM staffs each turn' — but never enumerates the skill's actual capabilities (job analysis, candidate search/selection, release pinning, execution, receipts) that the body covers. Not 4 because it does not list several specific actions; not 2 because the actions named are concrete rather than generic ('Processes PDF files'-level).

3 / 5

Completeness

Both questions are answered explicitly: 'Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal...' gives concrete trigger phrases, and the what is stated directly — staffing a durable goal from the three registered sources with 'the exact roster remains goal-bound until explicit completion'. Not 4 because the anchor-4 caveat ('when could be more explicit or specific') does not apply: the when lists exact typed strings.

5 / 5

Trigger Term Quality

Strong trigger coverage across command aliases — '$hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus' — plus the natural phrase 'asks Agentlas to staff a durable goal'. Not 5 because natural terms outside the command family that a user might say (e.g. 'workforce', 'recruit agents', 'agent team') are absent; not 3 because multiple variations and a genuine natural-language trigger are present.

4 / 5

Distinctiveness Conflict Risk

Triggers are exact command tokens and product-specific names ('@Hephaestus', 'Agentlas', '$hephaestus-network'), creating a clear niche with minimal overlap risk against any other skill. Not 4 because no closely related skill could plausibly capture these triggers.

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

cursor/plugin/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.