Hephaestus Graph

SkillDev tools

agentlas-graph gives your AI the ability to work with Agentlas automation graphs. Once added, it can create new graphs, list the ones you already have, inspect their details, and run them when you ask.

Available today. Use it from your connected AI after setup.

After adding it, type /agentlas-graph or /agentlas graph and tell your AI what you want to do, such as listing your graphs or running one.

Then ask your AI: use the Hephaestus Graph skill

What your AI can do with it

  • Create Agentlas automation graphs
  • List your existing automation graphs
  • Inspect the details of a graph
  • Run a graph when you ask

What this skill tells your AI

The instructions your AI receives, as published by agentlas-ai/agentlas-os in skills/agentlas-graph/SKILL.md and read by ahel’s review.

Saved graphs live in the local Agentlas database shared with Agentlas Desktop. This skill may create, list, inspect, or request a graph run; it does not execute the graph itself.

Resolve the independent Agentlas CLI

Use the first executable path:

CLI=""
for candidate in \
  "$(command -v agentlas 2>/dev/null)" \
  "$HOME/.agentlas/runtime/current/bin/agentlas" \
  "./bin/agentlas"
do
  if [ -n "$candidate" ] && [ -x "$candidate" ]; then CLI="$candidate"; break; fi
done
[ -n "$CLI" ] || { echo "Agentlas CLI not found. Install it with: npm i -g agentlas" >&2; exit 1; }

Do not substitute Gemini CLI, Hephaestus routing, or Hub search when the Agentlas CLI is missing.

Commands

  • No arguments or list: run "$CLI" graph list and report each graph's trigger, step count, and on/off state.
  • show <name>: run "$CLI" graph show "<name>". Preserve the tree wiring, external-effect and ask-first marks, branch sides, repeat edges, verification checklist, code steps, and any required input in the summary.
  • new <request>: run "$CLI" graph new "<request>" as an interview. Relay every unanswered question and never invent schedule, external-effect, repetition, or checklist answers. The final save confirmation is the graph's approval. A new graph starts switched off.
  • run <name>: the user's direct run request is sufficient authority. Do not ask for a second approval. Show the graph first; if it requires an input, obtain that missing value without inventing it. Then run "$CLI" graph run "<name>" -y, adding --input "<value>" when required.

Report exactly that a run was requested and will be picked up by Agentlas Desktop. Never claim the graph executed. On any non-zero exit, relay the exact refusal and stop; do not retry with a guess.

Signals

GitHub stars
1k
Forks
103
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
agentlas-graph
Source
github.com/agentlas-ai/agentlas-os