mcpbeat Sign in

Hephaestus Cloud Agent Skill

Use when the user types /hep-cloud or asks to find/route to one of THEIR OWN Agentlas cloud packages (보관함, 내 클라우드, 내 보관함, my cloud, my own agents). This is the owner-scoped leg of the three-scope model — it searches ONLY the signed-in user's own cloud packages, not the public marketplace (use hephaestus-network for that) and not local cards. The user's own cloud packages are restorable/owned by them and call-priced at a flat 1 credit.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1165
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/agentlas-ai/Agentlas-OS --skill hephaestus-cloud

The instruction itself

7 sections, as written by the author

Hephaestus Cloud Routing (my own cloud / 보관함)

Route the request through the signed-in user's OWN Agentlas cloud packages only.

Never guess an agent yourself when this skill is active — the router/Hub decides.

0. Scope rule

/hep-cloud is owner-scoped: it queries ONLY the authenticated owner's

own cloud packages (보관함) via the Hub owner filter (cargo.*). It does not

search the public marketplace and does not search local private/plugin

cards.

  • The user's own cloud packages are restorable/owned by them, call-priced at a

flat 1 credit per call.

  • For the public marketplace (others' published, per-call-priced agents), use

the hephaestus-network skill / --hub-only instead.

  • For the combined search (local + own cloud + Hub, each priced by origin), use

plain-language routing (hephaestus route).

1. Resolve the runner

Run this resolution in a shell and use the first hit:

RUNNER=""
for c in \
  "$HOME/.agentlas/runtime/current/bin/hephaestus" \
  ./bin/hephaestus
do [ -x "$c" ] && RUNNER="$c" && break; done
if [ -z "$RUNNER" ]; then
  for cache in \
    "$HOME/.claude/plugins/cache/agentlas-core-engine/hephaestus" \
    "$HOME/.codex/plugins/cache/agentlas-core-engine/hephaestus"; do
    newest="$(ls -d "$cache"/*/bin/hephaestus 2>/dev/null | sort -V | tail -1)"
    [ -n "$newest" ] && [ -x "$newest" ] && RUNNER="$newest" && break
  done
fi

If no runner exists, tell the user to run the one-touch installer:

curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/main/scripts/install-all-runtimes.sh | bash

If shell execution is unavailable in this harness but MCP is, call the

agentlas_authenticate tool first, then call the hephaestus_cloud_search tool

from the hephaestus-network MCP server instead.

2. Agentlas sign-in (required)

The owner cloud is sign-in-gated. Before routing, ensure Agentlas is signed in:

if [ "${HEPHAESTUS_AUTH_AUTOPOPUP:-1}" != "0" ]; then
  "$RUNNER" auth ensure --timeout 180 >/dev/null 2>&1 || true
fi

This opens the user's default browser only when there is no valid local sign-in

yet, and reuses a saved sign-in silently. For CI/headless checks only, set

HEPHAESTUS_AUTH_AUTOPOPUP=0 and skip this step.

3. Route (owner cloud only)

"$RUNNER" cloud "<the user's request>" --project .

hephaestus cloud is shorthand for hephaestus route "<request>" --scope cloud

(owner-scoped Hub query; implies --hub-only). Via MCP, call

hephaestus_cloud_search instead.

4. Act on the JSON decision (scope: "cloud")

  • action: "hub_candidates" — these are the user's OWN cloud packages

(hub.results[].slug, name). Report them, and on the user's pick invoke that

package with the original request (call-priced at 1 credit).

  • action: "clarify" — ask clarify_question with the candidate list and

re-route with the answer (still cloud-scoped).

  • action: "propose_new" — no matching package in the user's cloud. Offer to

search the public marketplace (hephaestus-network / --hub-only) or to build

a new agent via /hep-build.

  • action: "refuse" — explain reasons (for example, loop guard). Do not retry.

5. Hard rules

  • Never report public marketplace agents or local private/plugin cards as if

they were the user's own cloud packages.

  • The router only chooses a package or fetches a BYOM bundle; it does not

execute payments, deletes, publishes, file writes, or external submissions.

  • For actual tool execution, follow the host runtime's safety and permission

model. Report the routing receipt_id in your final message.

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

56k tokens scripts
Skill Creator
by vercel-labs
vendor ×10

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

12k tokens scripts
Skill Creator
by JayZeeDesign
×9

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

10k tokens scripts
Template Skill
by JayZeeDesign
×7

Replace with description of the skill and when Claude should use it.

35 tokens
Dispatching Parallel Agents
by ZhanlinCui
×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

2k tokens
Skill Development
by anthropics
vendor ×4

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

9k tokens
Find Skills
by sanity-io
vendor ×4

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

1k tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take agentlas-ai/agentlas-os-openclaw-hephaestus-cloud from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.