Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentlas-ai/hephaestus-build
Use when the user types /prompts:hep-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package an existing local/external agent into Agentlas architecture.
Passed 9 of 17 test cases with the skill, and 4 of 17 without it.
and 6 more in the full report
8 fixed4 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am unsure whether my proposed AI assistant project needs single agent or multi agent structure. Ask me a question to determine this.
| Checked | Without skill | With skill |
|---|---|---|
| asks mode classification question in plain everyday language | Passed | Passed |
| omits internal technical terms like single-agent or ownership boundary from user question | Missed | Passed |
The instructions your model reads when the skill loads.
Treat this as the public Codex build surface. Do not expose or ask the user to invoke the older internal support skill names.
Resolve the trusted engine root before reading any build contract:
ENGINE=""
for candidate in \
"${CODEX_PLUGIN_ROOT:-}" \
"${CLAUDE_PLUGIN_ROOT:-}" \
"${PLUGIN_ROOT:-}" \
"$HOME/.agentlas/runtime/current/host_adapters/codex/plugins/agentlas-core-engine-meta-agent" \
"$HOME/.agentlas/runtime/current/host_adapters/claude/plugins/agentlas-core-engine-meta-agent" \
"$HOME/.agentlas/runtime/current" \
"."
do
if [ -n "$candidate" ] && [ -f "$candidate/AGENTS.md" ] && [ -f "$candidate/package-contract.json" ] && [ -f "$candidate/contracts/builder-interview-research-gate.md" ]; then
ENGINE="$candidate"
break
fi
done
[ -n "$ENGINE" ] || { echo "Hephaestus engine not found. Run the installer first." >&2; exit 1; }
RUNNER=""
for candidate in "$HOME/.agentlas/runtime/current/bin/hephaestus" "$ENGINE/bin/hephaestus"; do
if [ -x "$candidate" ]; then RUNNER="$candidate"; break; fi
done
[ -n "$RUNNER" ] || { echo "Hephaestus runner not found." >&2; exit 1; }
Take exactly one folder explicitly named or confirmed by the user as
PACKAGE_TARGET. If none was named, or multiple candidates exist, stop and
ask. Never default to ., the cwd, or $ENGINE. Run
"$RUNNER" contract resolve-target "$PACKAGE_TARGET" --base "$PWD" and set
PACKAGE_ROOT only to the status-ok receipt's exact package_root.
Nonzero or error receipts are blockers.
Read $ENGINE/AGENTS.md, $ENGINE/.agentlas/mode-map.json, the selected
test cases passed, vs 4 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.