hephaestus-cloud

Use when the user types /hep-cloud or asks to staff from THEIR OWN Agentlas cloud packages (보관함, 내 클라우드, 내 보관함, my cloud, my own agents). This exact source scope searches only the signed-in owner's Cloud inventory, never public Hub or registered Local inventory.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

67%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-structured, actionable routing skill with concrete shell and MCP tooling and clear validation checkpoints. Its main weaknesses are repeated restatement of the same boundary rule across sections and placeholder arguments in the tool sequence that keep it from being fully copy-paste ready.

Suggestions

Consolidate the 'never fall back to legacy cargo / report source_not_supported' rule into one Hard Rules section instead of restating it in sections 0, 1, 3, and 5.

Replace the 'workOrder=..., selection=...' placeholders in the section 3 tool sequence with a minimal concrete example or a clear note that the host LLM authors these from the prior step's output.

Tighten section 1.5 ('Core project first-contact contract') into a checklist so the bootstrap requirements read as verifiable items rather than a prose paragraph.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean shell commands and typed tool sequences, but the 'never fall back to legacy cargo search / report source_not_supported' boundary is restated across sections 0, 1, 3, and 5, which is tightening-eligible padding; not a 4 because the repetition is noticeable rather than minor.	3 / 5
Actionability	Provides complete executable shell snippets (runner resolution, auth ensure) and a concrete ordered MCP tool-call sequence with typed parameters; falls short of 5 because WorkOrder/selection args are shown as '...' placeholders rather than copy-paste-ready values.	4 / 5
Workflow Clarity	Clear 0→5 sequence with explicit validation gates (validate_selection, validate_execution_receipt) and stop/report feedback loops (bootstrap blocked, source_not_supported); not a 5 because some error-recovery steps are described abstractly rather than as concrete fix-and-retry loops.	4 / 5
Progressive Disclosure	Well-organized into numbered sections with content appropriately kept inline for a routing skill and no nested or buried references; not a 5 because no bundle files exist and a few dense prose blocks (sections 1.5, 5) could be tighter rather than relying purely on sectioning.	4 / 5
	Total	15 / 20 Passed

Description

95%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, explicit description that cleanly states both the trigger conditions and the scoped action, with multilingual synonyms and a sharp boundary against adjacent skills. Minor room to enumerate more discrete capabilities, but it already exceeds the typical good-example bar.

Dimension	Reasoning	Score
Specificity	Names the concrete action ('staff from THEIR OWN Agentlas cloud packages', 'searches only the signed-in owner's Cloud inventory') and the source boundary, leaving only minor coverage gaps; not a 5 because it describes essentially one action rather than multiple distinct concrete operations.	4 / 5
Completeness	Explicitly answers both — 'Use when the user types /hep-cloud or asks to staff...' (when) and 'This exact source scope searches only the signed-in owner's Cloud inventory, never public Hub or registered Local inventory' (what) — with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including the slash command, English phrases ('my cloud', 'my own agents') and Korean synonyms (보관함, 내 클라우드, 내 보관함); matches the 'comprehensive coverage including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche (owner's own Cloud only) with an explicit boundary against public Hub and Local inventory, minimizing conflict with sibling routing skills like /hep-hub or /hep-network.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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-cloud/SKILL.md
Commit: 7032c0b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.