SkillAgentSearch skills...

hephaestus-cloud

Use when the user types /hep-cloud or /agentlas-cloud, or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.

Install / Use

npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-cloud

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of hephaestus-cloud

hephaestus-cloud scores 87/100 on our quality scale, 513th of 950 AI & Machine Learning skills we index.

Its SKILL.md is 5.0 KB long, well organised into 8 sections with 3 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.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so hephaestus-cloud 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

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (1 minor note below). An AI review judged it risky: The skill instructs the agent to run a remote install script via `curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/main/scripts/install-all-runtimes.sh | bash` when no runner is found.

  • noteInstalls by piping a downloaded script into a shellline 51
    `curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/main/scripts/install-all-runtimes.sh | bash`

AI review: risky

  • The skill instructs the agent to run a remote install script via `curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/main/scripts/install-all-runtimes.sh | bash` when no runner is found.
  • It directs the agent to execute shell commands to locate and run the `hephaestus` binary and to call `auth ensure`, which can open a browser and manipulate authentication state.
  • While scoped to the user's own cloud packages, the file gives the agent broad latitude to run external binaries and remote scripts without user confirmation.

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-cloud compared with similar skills

All 4 of these similar skills score higher than hephaestus-cloud; compare them before choosing.

SkillScoreStarsUpdatedFormat
hephaestus-cloud (this skill)by agentlas-ai871.1k53d agoSKILL.md
claude-memby thedotmack100117.6ktodayCLAUDE.md
Understand-Anythingby Egonex-AI10092.8k1d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install hephaestus-cloud?
Run npx skills add agentlas-ai/Agentlas-OS --skill hephaestus-cloud. The install tabs above show the steps for each supported agent.
Which AI agents does hephaestus-cloud 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-cloud safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands (1 minor note below). An AI review judged it risky: The skill instructs the agent to run a remote install script via curl -fsSL https://raw.githubusercontent.com/agentlas-ai/Agentlas-OS/main/scripts/install-all-runtimes.sh | bash when no runner is found. 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-cloud still maintained?
The repository was last updated about 2 months ago, so hephaestus-cloud is actively maintained.

name: hephaestus-cloud description: "Use when the user types /hep-cloud or /agentlas-cloud, or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub."

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

Route the request through the signed-in user's OWN Agentlas cloud packages only. The active host LLM remains the staffing decision-maker; Cloud supplies a content menu and exact BYOM releases.

0. Scope rule

/hep-cloud is owner-scoped: it queries ONLY the authenticated owner's own cloud packages (보관함) through Core's typed sourceScope: "cloud". 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. Entitlement, lease, and charged credits are server-authoritative; do not hard-code a price.
  • For the public marketplace only, use /hep-hub (sourceScope: "hub").
  • For the combined Local + own Cloud + public Hub menu, use /hep-network (sourceScope: "network").

Each unpinned Cloud discovery goes to the owner-scoped source for its current menu; a successful client cache entry must not hide a newly published, replaced, or removed package. Once the host validates and prepares a choice, the exact Cloud release remains pinned for that execution.

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 but the local hephaestus-network MCP is available, use the typed Workforce sequence in section 3. If that server cannot advertise owner-Cloud search plus exact bundle fetch, report source_not_supported; never fall back to the legacy cargo search path.

1.5 Core project first-contact contract

The cloud ... --project . call below is a trusted plugin contact. Agentlas Core must synchronously create or repair the same private project soul memory, code map, ontology runtime, CareerGraph, and full .agentlas/ ignore block used by every other host. If bootstrap is blocked, stop rather than querying Cloud without the project architecture. The adapter never owns a second seed format.

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 >/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. Staff from owner Cloud only

In an MCP-capable host, author the complete redacted WorkOrder, then call the actual local Core tools in this order:

workforce.search_candidates(sourceScope="cloud")
workforce.validate_selection(workOrder=..., selection=...)
workforce.prepare_execution(workOrder=..., selection=..., federatedSelection=..., projectDir=..., goalId=activeGoalId?)
workforce.validate_execution_receipt(receipt=..., executionPlan=..., toolInventory=...)

The host LLM authors the final Selection. If the deployed owner-Cloud Workforce source contract is absent, report source_not_supported; do not silently query public Hub or legacy cargo search. A shell without an active host LLM can only report that orchestration is required.

The default search response is a projected menu. Preserve its Cloud source receipt and selectionSessionId, but do not echo it as a complete federationResult; Core resolves the full pinned result by session. Receipt validation is local and read-only and cannot create execution evidence.

4. Act on the typed result (scope: "cloud")

Preserve the Cloud source receipt, source selection session, candidate-set digest, release id, package hash, and content digest. Validate and prepare in local Core; never send the federated wrapper back to remote validation.

5. Hard rules

  • Never report public marketplace agents or local private/plugin cards as if they were the user's own cloud packages.
  • Deterministic Core validates governance and immutable pins but never chooses the roster. The active host LLM chooses from content evidence.
  • For actual tool execution, follow the host runtime's safety and permission model. Report the exact source receipt plus selectionReceiptId, preparationReceiptId, and validated execution receipt status when present.

Related Skills

View on GitHub
GitHub Stars1.1k
CategoryAI
Updated1mo ago
Forks98

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions