Skill
agentlas-build
Use when the user types /agentlas-build, /agentlas build, or /hep-build to design, build, and package a single agent or multi-agent team.
@agentlas-aiView SkillDevelopment
Skill
/agentlas-core-engine-meta-agent
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
Install
$ npx -y skills add agentlas-ai/Agentlas-OS --skill agentlas-core-engine-meta-agent --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agentlas-core-engine-meta-agent
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.
SKILL.md
agentlas-core-engine-meta-agent.SKILL.mdname: agentlas-core-engine-meta-agent
description: "Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests."
Agentlas Core Engine Meta-Agent
Procedure
1. Read `AGENTS.md`. 2. Read `.agentlas/mode-map.json`. 3. Run mode classification. 4. Ask clarify questions when missing details change files, adapters, or public/private boundary. 5. Pick one team member:
- Single Agent Builder;
- Multi Agent Team Builder;
- Agentlas Packager.
6. Load only the matching support skills. 7. Emit or repair the Agentlas contracts, including `.agentlas/global-commands.json`. Include `.agentlas` auto-activation seed files when local continuity is part of the output. 8. Write all generated or repaired runtime agent instructions in English, including adapters, role prompts, skills, handoff contracts, return contracts, and operating docs. Translate Korean or other-language source material into English agent behavior. Localized public copy and routing trigger examples may use the target user language. 9. Add the generated command to Claude Code, Codex, Gemini CLI, generic AGENTS.md, and terminal adapters. For teams, expose the orchestrator/HQ command and route workers through HQ unless direct worker commands were requested. 10. Verify with `scripts/verify-package.sh`.
Output
Return `status`, `evidence`, `output`, `global_commands`, and `blockers`.
Read more
name: agentlas-core-engine-meta-agent description: "Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests."
Agentlas Core Engine Meta-Agent
Procedure
1. Read `AGENTS.md`. 2. Read `.agentlas/mode-map.json`. 3. Run mode classification. 4. Ask clarify questions when missing details change files, adapters, or public/private boundary. 5. Pick one team member:
- Single Agent Builder;
- Multi Agent Team Builder;
- Agentlas Packager.
6. Load only the matching support skills. 7. Emit or repair the Agentlas contracts, including `.agentlas/global-commands.json`. Include `.agentlas` auto-activation seed files when local continuity is part of the output. 8. Write all generated or repaired runtime agent instructions in English, including adapters, role prompts, skills, handoff contracts, return contracts, and operating docs. Translate Korean or other-language source material into English agent behavior. Localized public copy and routing trigger examples may use the target user language. 9. Add the generated command to Claude Code, Codex, Gemini CLI, generic AGENTS.md, and terminal adapters. For teams, expose the orchestrator/HQ command and route workers through HQ unless direct worker commands were requested. 10. Verify with `scripts/verify-package.sh`.
Output
Return `status`, `evidence`, `output`, `global_commands`, and `blockers`.
Ships withagentlas-os
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
Get the whole plugin
Other skills on agentlas-os.
@agentlas-aiView SkillSkill
agentlas-cloud
Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.
@agentlas-aiView SkillSkill
agentlas-graph
Use when the user types /agentlas-graph, /agentlas graph, or /hep-graph to create, list, inspect, or run Agentlas automation graphs.
@agentlas-aiView SkillSkill
agentlas-network
Use when the user types /agentlas-network, /agentlas network, $hephaestus-network, or /hep-network to staff a durable goal from registered Local, owner Cloud,…
@agentlas-aiView SkillSkill
agentlas-storm
Use when the user types /agentlas-storm, /agentlas storm, /hep-storm, or says @Hephaestus storm <goal> to drive a goal through the force-robust Stormbreaker…
@agentlas-aiView SkillSkill
agentlas-upload
Use when the user types /agentlas-upload, /agentlas upload, $hephaestus-upload, or /hep-upload to scan, gate, and publish an agent/team package to Agentlas…
@agentlas-aiView Skill