CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hephaestus-cloud

Use when the user types /hep-cloud or /agentlas-cloud, or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.

Quality

76%

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 ./codex/plugins/agentlas-core-engine-meta-agent/skills/hephaestus-cloud/SKILL.md

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

SKILL.md
Quality
Evals
Security

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.

The body delivers a well-sequenced, mostly executable routing workflow with genuine validation checkpoints and clear failure modes. Its weaknesses are repetition — the scope-isolation rule is stated four times — and placeholder-laden core call signatures that leave the central staffing operation not fully copy-paste ready.

Suggestions

State the owner-scope/no-Hub/no-legacy-fallback rule once (e.g., in Hard rules) and reference it elsewhere, cutting roughly 15-20% of the body.

Replace the ellipsis placeholders in the workforce call sequence with a minimal concrete example of a WorkOrder/selection payload, or point to a reference file containing one.

Show the actual 'cloud ... --project .' command line referenced in section 1.5, since the first-contact contract depends on it.

DimensionReasoningScore

Conciseness

The owner-scope/no-Hub/no-legacy-cargo rule is restated four times ("does **not** search the public marketplace" in §0, "never fall back to the legacy cargo search path" in §1, "do not silently query public Hub or legacy cargo search" in §3, "Never report public marketplace agents" in §5) and receipt preservation is repeated across §3 and §4, so the body could be meaningfully tightened rather than just trimmed at the edges.

3 / 5

Actionability

The runner-resolution and auth snippets are copy-paste ready and the Workforce call sequence names concrete typed parameters, but §3 uses ellipsis placeholders ("workOrder=..., selection=...") and §1.5 references a "cloud ... --project ." call whose actual command line is never shown, leaving minor gaps.

4 / 5

Workflow Clarity

Sections 0-5 give a clear sequence (resolve runner → sign in → search → validate → prepare → validate receipt) with explicit checkpoints and error paths ("report source_not_supported", installer fallback, headless env var), but there is no fix-and-retry feedback loop for validation failures, so it stops short of the 5 anchor.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with no bundle files (no references/, scripts/, or assets/ exist and none are cited) and clear numbered sections; at ~112 lines with all content inline, structure is good but it exceeds the under-50-line simple-skill case and has minor organization gaps (e.g., the runner script could live in a scripts/ file).

4 / 5

Total

15

/

20

Passed

Description

73%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 has strong trigger clarity and excellent distinctiveness thanks to explicit slash commands and an explicit Cloud-vs-Network scope boundary. Its main weakness is specificity: it states only one concrete action and leans on scope disambiguation rather than describing what the skill actually does.

Suggestions

Add 1-2 more concrete capability statements (e.g., what happens on a successful route: search the owner's cloud menu, validate a selection, prepare a pinned execution) so the 'what' goes beyond a single action.

Include natural synonym triggers users might say, such as "my cloud packages", "my Agentlas storage", or "보관함", to broaden keyword coverage.

DimensionReasoningScore

Specificity

"staff from THEIR OWN Agentlas cloud packages only" names the domain and one concrete action, but the remaining text ("Cloud is one exact source scope; Network means Local + owner Cloud + public Hub") is scope disambiguation rather than a list of capabilities, matching the 1-2-concrete-actions anchor.

3 / 5

Completeness

The "when" is explicit ("Use when the user types...") and a "what" is present (route staffing through the owner's own cloud packages), but the what is thin on concrete capability detail, matching 'both present, when/what could be more specific' rather than the fully explicit 5 anchor.

4 / 5

Trigger Term Quality

"Use when the user types /hep-cloud or /agentlas-cloud" plus "asks to staff from THEIR OWN Agentlas cloud packages" gives good natural trigger coverage, but common variations like "my cloud", "my packages", or "보관함" are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Distinct slash-command triggers ("/hep-cloud or /agentlas-cloud") and the explicit scope disambiguation ("Cloud is one exact source scope; Network means Local + owner Cloud + public Hub") carve out a clear niche with minimal overlap against sibling skills.

5 / 5

Total

16

/

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

codex/plugins/agentlas-core-engine-meta-agent/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.