CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hephaestus-upload

Use when the user types $hephaestus-upload, /hep-upload, or /agentlas-upload, or asks to upload, publish, or list an Agentlas agent or team. Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate.

Quality

93%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong operational skill: it provides copy-paste-ready commands, explicit validation checkpoints (hash/receipt pinning), and recovery loops for every named failure code. The main improvement levers are trimming a few justificatory asides and the intro/Section-1 redundancy, and considering splitting the secret-review protocol into a reference file.

DimensionReasoningScore

Conciseness

The body is dense with operational detail Claude cannot infer (exact flags, error codes, receipt semantics), but the intro's WRITE-surface rationale duplicates Section 1's "Ask this before anything else, even when the arguments already say upload," and a few justificatory asides ("Pattern checks only find secrets someone wrote a pattern for") could be trimmed. It sits above the mostly-efficient anchor 3 (over-explanation is minor, not structural) but below anchor 5 where every token earns its place.

4 / 5

Actionability

Fully executable guidance: a copy-paste RUNNER resolution loop, exact `hep-upload` commands with flags for both destinations in dry-run and publish forms, a concrete JSON verdict schema with enumerated `kind` values, and precise recovery commands (`--overwrite-cloud-id <exact-cloud-id>`). Specific examples cover the common cases, matching the anchor-5 example.

5 / 5

Workflow Clarity

Clear numbered sequence (ask destination → resolve runner → gate → publish → repair → report) with explicit validation (dry-run, `--expected-package-hash`, `--expected-upload-receipt`) and feedback loops ("Rerun the upload and repeat until registration succeeds"; overwrite approval flow). Validation is present for this hard-to-reverse write, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist, and the single file is well organized into seven numbered sections with no nested or buried references. It scores 4 rather than 5 because the skill exceeds 50 lines (the simple-skill exception) and keeps all content, including the lengthy secret-review protocol, inline.

4 / 5

Total

18

/

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 near-ideal description: it pairs exact command triggers with natural-language verbs, states both what and when explicitly, and is highly distinctive. The only weakness is a minor coverage gap — the "list" action is advertised but not addressed in the skill body.

DimensionReasoningScore

Specificity

Names several concrete actions — "upload, publish, or list an Agentlas agent or team" and "publish through the bundled Hephaestus gate" — plus the distinctive destination-first behavior. It falls short of anchor 5 because "list" is claimed but never covered by the skill body, and "the bundled Hephaestus gate" names a mechanism rather than a concrete action, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both questions: an explicit "Use when the user types… or asks to upload, publish, or list" trigger clause, and a clear what (publish an Agentlas agent or team through the Hephaestus gate, asking Cloud vs Hub first). This matches anchor 5's what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage: exact command triggers ("$hephaestus-upload, /hep-upload, or /agentlas-upload") plus verb synonyms ("upload, publish, or list") and domain nouns ("Agentlas agent or team"), matching anchor 5's synonym-and-variant coverage.

5 / 5

Distinctiveness Conflict Risk

Unique command names ($hephaestus-upload, /hep-upload, /agentlas-upload) and a niche domain (Agentlas/Hephaestus, Cloud vs Hub) give it a clear niche with minimal conflict risk against generic upload or agent skills.

5 / 5

Total

19

/

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

.agents/skills/hephaestus-upload/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.