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.
Install / Use
npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-uploadInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of hephaestus-upload
hephaestus-upload scores 87/100 on our quality scale, 2211th of 4,698 Development & Engineering skills we index (top 48%).
Its SKILL.md is 5.2 KB long, well organised into 8 sections with 2 code examples: a solid amount of guidance for an agent.
With 1,087 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so hephaestus-upload is actively maintained.
- Our last check on 2026-10-11 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
hephaestus-upload compared with similar skills
All 4 of these similar skills score higher than hephaestus-upload; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| hephaestus-upload (this skill)by agentlas-ai | 87 | 1.1k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install hephaestus-upload?
- Run
npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-upload. The install tabs above show the steps for each supported agent. - Which AI agents does hephaestus-upload work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is hephaestus-upload safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is hephaestus-upload still maintained?
- The repository was last updated about 2 months ago, so hephaestus-upload is actively maintained.
Skill content
View source on GitHubname: hephaestus-upload description: "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."
Hephaestus Upload (Cloud or Agentlas Hub)
Publish a finished Agentlas package. This is a WRITE surface: a Hub upload is public and other people can borrow it, so the destination question comes before any packaging or API call.
Upload is deliberately NOT folded into /hep-network. Network staffs a roster
(a read), upload publishes an artifact (a write that is hard to take back);
merging them would let "find me an agent" end in an accidental publish.
1. Ask the destination first — always
Ask this before anything else, even when the arguments already say upload, publish, add, Cloud, Hub, or name a target folder:
Cloud에 업로드할까요? 다른 사람들은 볼 수 없어요.
Upload to Cloud? Other people cannot see it.
Agentlas Hub에 업로드할까요? 다른 사람들이 빌려 쓸 수 있어요.
Upload to Agentlas Hub? Other people can borrow it.
Do not package, publish, register, add-source, reindex, or call any upload API until the user answers Cloud or Agentlas Hub. If the destination is answered but the target folder is ambiguous, ask for the exact agent folder before running anything.
2. Public Hub publishing is free
The public Hub is an agent community. Do not ask for an upload price, invoke a
price-setting tool, or pass the retired --rent-credits, --ingest-credits, or
--fork-credits flags. The CLI rejects those legacy flags. The creator's model
and API prerequisites still belong in the package guide.
3. Resolve the runner in this host
Run the preflight inside this host app; never ask the user to open a separate terminal.
RUNNER=""
for candidate in "$HOME/.agentlas/runtime/current/bin/hephaestus" "./bin/hephaestus"; do
[ -x "$candidate" ] && RUNNER="$candidate" && break
done
[ -n "$RUNNER" ] || { echo "Hephaestus runtime not found. Run the installer first." >&2; exit 1; }
4. Use one immutable upload gate
Do not run package and then publish: that packages twice and the second
artifact may differ from the one reviewed. The upload gate copies the selected
folder into a private, link-free snapshot, repairs and validates that snapshot
once, and either dry-runs or submits those exact bytes.
If the user requests a preview, run exactly one dry-run and retain the returned
manifest.packageHash and uploadReceipt.receipt:
- Cloud:
"$RUNNER" hep-upload <agent-folder> --visibility private-link --dry-run - Agentlas Hub:
"$RUNNER" hep-upload <agent-folder> --visibility marketplace --dry-run
All security and content findings are advisory. Never instruct the user to
block, abort, or postpone an upload because of a finding. Continue the same
upload with safe bytes: omit each affected source item and bind an omission
receipt, or record an engine-gap receipt when the current engine cannot safely
represent or repair it, then submit the remaining package. Keep every finding
and omission visible in the result. The gate also repairs what it can derive
from the package — including the entity type: a card that claims agent while
the package ships a multi-node roster is corrected to team, so the release is
executed as the team it actually is.
5. Publish once, optionally pinned to the preview
- Cloud:
"$RUNNER" hep-upload <agent-folder> --visibility private-link - Agentlas Hub:
"$RUNNER" hep-upload <agent-folder> --visibility marketplace
After a dry-run, append both --expected-package-hash <manifest.packageHash> and
--expected-upload-receipt <uploadReceipt.receipt> to the one publish command.
The receipt binds the exact hash, visibility, slug, and destination. Stop on
package_hash_mismatch, upload_receipt_required, or
upload_receipt_mismatch; never silently publish a replacement artifact or
switch an approved private preview to the public Hub.
If registration returns overwrite_confirmation_required, show the exact
server-reported Cloud ID and ask for overwrite approval. Only after approval,
rerun the same pinned command with --overwrite-cloud-id <exact-cloud-id>.
Never infer overwrite permission from a matching slug.
Surface authentication and entitlement codes exactly (sign_in_required,
auth_unavailable, owner_only). Do not replace a
failed Hub destination with Cloud or vice versa.
6. Workforce résumé repair loop
If registration returns workforce_resume_incomplete, the server refused the
card because its workforce block
does not match the hub standard résumé. The error carries the exact mismatches
and seed ontology examples. YOU repair it — the platform never edits the card
for you: use stable English role:*, community:*, skill:*, and
knowledge:* IDs that actually describe the agent. The returned examples are
aliases, not an allowlist. Rerun the upload and repeat until registration
succeeds.
7. Report honestly
Report published only when the response attests the exact slug, visibility,
package hash, immutable release ID/version, and content digest. Say which
destination it went to. Otherwise report the last true state and the server's
exact refusal code. Do not relabel an advisory finding as an upload block.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
