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

90%

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, executable runbook: exact commands and flags, an explicit secret-review protocol, receipt-pinned publishing with hard failure stops, and error-code-by-error-code recovery guidance for a hard-to-reverse public write. Validation checkpoints and feedback loops are exemplary. The only soft spots are minor over-explanation in the design-rationale passages and a single-file structure that is slightly long for a SKILL.md overview.

DimensionReasoningScore

Conciseness

The body is dense and operational — exact commands, flags, and error codes — with only minor trimmable passages such as the design rationale ("Upload is deliberately NOT folded into /hep-network...") and repeated advisory-safety emphasis. Not a 3 because nothing explains general concepts Claude already knows (all rationale is project-specific policy), and not a 5 because a few sentences could still be tightened.

4 / 5

Actionability

Fully executable guidance throughout: a copy-paste runner-resolution bash loop, exact CLI invocations with flags ("--visibility private-link --secret-review <file> --dry-run"), a concrete JSON verdict schema with enumerated kind values, and exact server error codes with prescribed responses. Placeholders like <agent-folder> are appropriate parameterization, matching the 5 anchor.

5 / 5

Workflow Clarity

A clear numbered 1-7 sequence (ask destination → resolve runner → gate/secret review → dry-run → publish → repair loop → report) with explicit validation checkpoints for a hard-to-reverse write: "Stop on package_hash_mismatch, upload_receipt_required, or upload_receipt_mismatch", overwrite approval gating, and a feedback loop ("Rerun the upload and repeat until registration succeeds"). This matches the 5 anchor including error-recovery loops.

5 / 5

Progressive Disclosure

No bundle files exist, and the single file is well organized into numbered phase sections that are easy to navigate. It scores 4 rather than 5 because at ~155 lines, self-contained detail blocks (the secret-review JSON schema and the résumé repair spec) could plausibly live in one-level-deep reference files, though keeping them inline in the core flow is defensible. Not a 3: structure is genuinely good, not merely present.

4 / 5

Total

18

/

20

Passed

Description

87%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 with an explicit 'Use when' trigger clause covering exact commands and natural request verbs, a concrete what (ask Cloud vs Hub, then publish via the Hephaestus gate), and highly distinctive domain nouns. Voice is imperative/consistent with skill conventions, and it is concise without padding. The only minor gap is a few missing natural synonyms such as 'share' or 'make public'.

DimensionReasoningScore

Specificity

Names several concrete actions — "upload, publish, or list an Agentlas agent or team", "Ask Cloud (private) vs Agentlas Hub (public) FIRST", "publish through the bundled Hephaestus gate" — with only minor gaps (dry-run pinning, secret review, résumé repair unmentioned). Not a 5 because coverage is not comprehensive, and not a 3 because more than 1-2 specific actions are explicitly listed.

4 / 5

Completeness

Explicitly answers both: when — "Use when the user types $hephaestus-upload, /hep-upload, or /agentlas-upload, or asks to upload, publish, or list..." with concrete trigger phrases, and what — "Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate". Clear what-and-when with concrete triggers matches the 5 anchor; the 4 anchor's 'when could be more explicit' does not apply here.

5 / 5

Trigger Term Quality

Good keyword coverage: exact commands "$hephaestus-upload, /hep-upload, /agentlas-upload" plus natural verbs "upload, publish, or list" with the domain noun "Agentlas agent or team". A few natural terms a user might say are missing (e.g., "share", "deploy", "submit", "make public"), which keeps it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Proper nouns "Agentlas" and "Hephaestus" plus exact slash/dollar commands give it a clear niche with minimal conflict risk against generic upload or publishing skills. It matches the 5 anchor ('clear niche with distinct triggers') rather than the 4 anchor's minor overlap risk.

5 / 5

Total

18

/

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

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