CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/hephaestus-cloud/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 presents a clearly sequenced routing workflow with executable shell snippets and explicit validation checkpoints, but it repeatedly restates the scope rule and leaves the pivotal artifacts (WorkOrder, Selection, receipts) unspecified, which weakens actionability. Organization is good for a single-file skill, though its length argues for splitting detail into reference files.

Suggestions

State the owner-only scope rule once (section 0) and cut its repetitions in sections 3, 4, and 5 to save tokens.

Add a concrete example of the WorkOrder/Selection structure and the expected receipt fields so the workforce.* sequence is executable end-to-end.

Add an error-recovery branch for failed validate_selection/prepare_execution, mirroring the existing 'if no runner exists' fallback.

DimensionReasoningScore

Conciseness

The body is mostly efficient and Agentlas-specific (no generic concepts re-explained), but the owner-only scope rule is repeated across sections 0, 3, 4, and 5 ("never public Hub", "never fall back to the legacy cargo search path"), and dense passages like section 1.5 could be tightened. It fits 'mostly efficient but could be tightened' rather than level 4, where only minor trimming would be needed.

3 / 5

Actionability

The runner-resolution bash block and installer URL are fully executable, and the workforce.* sequence names concrete tools and parameters, but key details are missing: the WorkOrder/Selection content is never specified, receipt handling is described abstractly ("Preserve the Cloud source receipt…"), and there is no example of acting on a result. This sits between 'some concrete guidance but incomplete' and 'mostly executable', landing at 3.

3 / 5

Workflow Clarity

Steps are clearly sequenced (scope → resolve runner → project contract → sign-in → search/validate/prepare → act on result → hard rules) with explicit validation calls (workforce.validate_selection, workforce.validate_execution_receipt) and failure paths ("If no runner exists…", "report source_not_supported"). It falls short of level 5 because there is no error-recovery loop explaining what to do when validation or preparation fails.

4 / 5

Progressive Disclosure

The single-file body is well organized into numbered sections with no bundle files to reference. It scores 4 rather than 5 because the body exceeds 50 lines and inlines all detail (receipt fields, WorkOrder expectations, sign-in mechanics) that could be split into one-level-deep reference files, though the content is coherent enough that the gap is minor.

4 / 5

Total

14

/

20

Passed

Description

81%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, well-scoped description with excellent bilingual trigger terms and explicit use-when guidance plus active disambiguation from sibling skills. Its main weakness is specificity: the 'what' leans on domain jargon ("staff", "source scope") instead of plainly stating the concrete actions it performs.

Suggestions

State the core capability in plain language (e.g., "Routes agent requests to packages from the signed-in user's own cloud inventory") before the scope qualifiers.

Name one or two concrete outcomes or actions the skill performs, not just the search scope it enforces.

DimensionReasoningScore

Specificity

The description names the domain and one to two actions ("staff from THEIR OWN Agentlas cloud packages", "searches only the signed-in owner's Cloud inventory") but expresses them through jargon like "staff" and "source scope" rather than a list of concrete capabilities. It is above level 2 because the domain and actions are named, but below level 4 because no several specific actions are enumerated.

3 / 5

Completeness

It has an explicit "Use when…" clause with concrete trigger phrases and states what it does ("searches only the signed-in owner's Cloud inventory"), but the 'what' is wrapped in scoped jargon rather than plainly stated capabilities. It is above level 3 because 'when' is fully explicit, but below level 5 because the 'what' is not clearly and plainly answered.

4 / 5

Trigger Term Quality

The description covers natural trigger terms comprehensively and in two languages: "/hep-cloud", "보관함", "내 클라우드", "내 보관함", "my cloud", "my own agents" — exactly the phrases a user would say when they need this skill. This matches the top anchor's comprehensive synonym coverage.

5 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche and actively disambiguates ("never public Hub or registered Local inventory"), and its triggers (own-cloud phrases, /hep-cloud) are distinct from sibling marketplace/local skills. Minimal conflict risk matches the top anchor.

5 / 5

Total

17

/

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