/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.
$ 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`.
Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
Other skills on agentlas-os.
- /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.
Open skill - /hephaestus-cloud
Use when the user types /hep-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.
Open skill - /hephaestus-network
Use when the user types $hephaestus-network or /hep-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until
Open skill - /hephaestus-storm
Use when the user types /hep-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each
Open skill - /hephaestus-upload
Use when the user types $hephaestus-upload or /hep-upload, or asks to upload, publish, or list an Agentlas agent or team. Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate.
Open skill - /routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching
Open skill