CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hephaestus-network

Use when the user asks OpenClaw to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM chooses the exact roster, which remains goal-bound until explicit completion.

Quality

70%

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 ./openclaw/skills/hephaestus-network/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 explicit, well-gated workflow with concrete tool calls, commands, and fail-closed validation loops — genuinely actionable for an orchestrator. Its weaknesses are verbosity (heavy repetition of do/not rules and dated version anecdotes) and a monolithic structure with no reference files despite length.

Suggestions

Deduplicate the repeated policy negations (never-fabricate, never-substitute, Core-owns rules appear in multiple sections) into a single short policy section, and move dated incident notes like the 2026-09-24 Codex probe into a changelog/old-patterns reference to cut token cost.

Split the ~440-line body into one-level-deep reference files (e.g., references/receipts.md for the execution-receipt field list, references/host-executor.md for the adapter stdin/stdout contract) and keep SKILL.md as a compact overview with clearly signaled links.

Add one complete worked example of the MCP sequence with realistic filled-in arguments (a small taskBrief, roles, and decision) so the placeholder signatures become copy-paste ready.

DimensionReasoningScore

Conciseness

The ~440-line body is noticeably verbose: the same constraints are restated repeatedly across sections ("Never replace or silently remove an incumbent release", "Never fabricate telemetry or claim accepted validation", "do not invent… Core owns…"), and it embeds dated specifics ("Measured 2026-09-24… runtime 1.2.49") that will rot. While it avoids explaining concepts Claude already knows, substantial trimming and deduplication is needed.

2 / 5

Actionability

Concrete guidance dominates: the exact typed MCP call sequence with named parameters (workforce.preflight_work_order(taskBrief=..., roles=..., edges=...)), executable bash for runner resolution and `workforce execute`, explicit reason codes, and named schemas. Falls short of 5 because parameters are elided placeholders and no complete worked example is shown.

4 / 5

Workflow Clarity

A clear seven-phase numbered sequence (job analysis → menu/decision → validate/pin → bind to goal → model policy → execute → receipts) with explicit validation gates and feedback loops: "Re-plan on rejection", "recompute its canonical digest before execution and fail closed on mismatch", the five turn postures, and strict receipt verification after execution.

5 / 5

Progressive Disclosure

Section headers and ordered phases give real structure, but no bundle files exist (references/, scripts/, assets/ are absent) and everything — receipt field lists, digest rules, the host-executor contract (pointing only at the installed engine's agentlas_cloud/workforce/host_executor.py) — is inlined in a single ~440-line file that should be split into one-level-deep references.

3 / 5

Total

14

/

20

Passed

Description

66%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 answers both what and when with an explicit trigger clause and a distinctive niche, but is written in internal system vocabulary ("staff a durable goal", "goal-bound") rather than natural user phrasing, limiting trigger-term quality and specificity. Rewriting triggers around what a user would actually say would raise it.

Suggestions

Rewrite the trigger clause using natural user phrasing and synonyms, e.g., "Use when the user asks to build, hire, or staff a team of agents for an ongoing goal, or to find agents/teams from local, cloud, or public hub inventories."

Replace internal jargon such as "durable goal", "goal-bound", and "staff" with plain-language equivalents (e.g., "long-running task", "keeps the team assigned") so the what is concrete without body context.

Add one or two more distinct concrete actions (e.g., searching candidate agents, validating and pinning exact releases) to broaden capability coverage beyond the single staffing action.

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete elements — "staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams" plus roster selection and binding — but does not list several distinct concrete actions, and internal jargon ("durable goal", "goal-bound") blurs concreteness.

3 / 5

Completeness

Both parts are present: the what ("staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams… the active host LLM chooses the exact roster") and an explicit when ("Use when the user asks OpenClaw to…"). The when-clause largely restates the what rather than offering concrete, varied trigger phrases, so it falls short of a 5.

4 / 5

Trigger Term Quality

Relevant keywords like "agents or teams" and an explicit "Use when the user asks OpenClaw to staff a durable goal" clause exist, but the trigger phrasing is system jargon users would not naturally say, and common variations (e.g., "build a team", "find agents") are absent.

3 / 5

Distinctiveness Conflict Risk

The scoped source model ("registered Local, owner Cloud, and public Hub agents") plus durable goal binding is a clear niche with minimal conflict risk, though "agents or teams" mildly overlaps generic agent-orchestration and delegation skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

agentlas-ai/Agentlas-OS

Path

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