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.

The body is a tight, highly actionable runbook for a risky publish operation: exact commands, an explicit validation/pinning chain, and error-recovery loops for every failure code it names. Its only weaknesses are minor — a few trimmable rationale passages and a single-file layout that inlines two protocol-sized sections that could be split into references.

Suggestions

Trim the rationale passages (e.g., the /hep-network comparison in the preamble and the "Pattern checks only find secrets" framing) to pure imperatives to gain a notch of token efficiency.

Move the host-model secret-review file spec and the workforce résumé repair loop into one-level-deep reference files (e.g., references/secret-review.md), keeping SKILL.md as a shorter overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is dense and imperative with almost no padding of concepts Claude already knows, but a few rationale passages ("Upload is deliberately NOT folded into /hep-network...", "Pattern checks only find secrets someone wrote a pattern for") are over-explanation that could be trimmed, matching anchor 4 rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands with exact flags ("hep-upload <agent-folder> --visibility marketplace --secret-review <file> --dry-run"), an executable runner-resolution bash snippet, and an exact JSON verdict file schema cover the common cases.

5 / 5

Workflow Clarity

Sections 1–7 give a clear sequence with explicit validation checkpoints for a hard-to-reverse write operation: dry-run hash/receipt pinning, stop conditions ("Stop on package_hash_mismatch, upload_receipt_required, or upload_receipt_mismatch"), an overwrite approval loop, and a résumé-repair retry loop ("Rerun the upload and repeat until registration succeeds").

5 / 5

Progressive Disclosure

The body is well organized into seven numbered sections with no nested or buried references, but at roughly 155 lines the inline secret-review protocol (~40 lines of spec) and the résumé-repair details could live in separate reference files; this matches anchor 4's "most content is appropriately placed; minor organization gaps" rather than anchor 5, since the under-50-lines exception does not apply.

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 strong description: it pairs an explicit "Use when..." trigger clause (with three exact command aliases and natural verbs) with a concrete statement of what the skill does and the critical destination-first gating rule. The only weakness is that it doesn't surface secondary capabilities like dry-run preview or secret review, leaving specificity just short of comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("upload, publish, or list an Agentlas agent or team", "publish through the bundled Hephaestus gate") but omits deeper capabilities like dry-run previews, secret review, and overwrite confirmation, which are minor gaps in coverage rather than the comprehensive coverage of anchor 5.

4 / 5

Completeness

An explicit "Use when..." clause with concrete trigger phrases answers "when", and "publish through the bundled Hephaestus gate" with the Cloud-vs-Hub destination question answers "what" — both are clearly and explicitly stated, matching anchor 5.

5 / 5

Trigger Term Quality

It covers three exact command triggers ("$hephaestus-upload, /hep-upload, or /agentlas-upload") plus the natural verbs and nouns users would say ("upload, publish, or list an Agentlas agent or team"), giving comprehensive natural-term coverage that exceeds anchor 4's "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

Product-specific names (Agentlas, Hephaestus, Cloud vs Agentlas Hub) and exact command aliases establish a clear niche with distinct triggers and minimal conflict risk with any generic skill.

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

cursor/plugin/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.