Agent skill · AI & Agents

hephaestus-upload

Use when the user types $hephaestus-upload or /hep-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.

Agentlas1,166★ · +196/wk · 1 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-upload --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/hephaestus-upload/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,165
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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: ```text 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. Resolve the runner in this host Run the preflight inside this host app; never ask the user to open a separate terminal. ```bash RUNNER="" f

What's inside
Steps it walks through
  1. 1. Ask the destination first — always
  2. 2. Resolve the runner in this host
  3. 3. Validate through the bundled gate
  4. 4. Publish
  5. 5. Workforce résumé repair loop
  6. 6. Report honestly
Commands it runs
for candidate in "$HOME/.agentlas/runtime/current/bin/hephaestus" "./bin/hephaestus"; do
done
More from Agentlas-OS
All skills →
About this skill
What does the hephaestus-upload skill do?

Use when the user types $hephaestus-upload or /hep-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.

How do I install it?

Run `npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-upload --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From agentlas-ai/Agentlas-OS, a repository with 1,165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going