Run any Skill in Manus with one click

agentlas-core-engine-meta-agent

Stars970

Forks33

UpdatedJuly 8, 2026 at 08:43

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

agentlas-ai

agentlas-ai/Agentlas-OS

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

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

Read AGENTS.md.
Read .agentlas/mode-map.json.
Run mode classification.
Ask clarify questions when missing details change files, adapters, or public/private boundary.
Pick one team member:
- Single Agent Builder;
- Multi Agent Team Builder;
- Agentlas Packager.
Load only the matching support skills.
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.
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.
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.
Verify with scripts/verify-package.sh.

Output

Return status, evidence, output, global_commands, and blockers.

More from this repository

same repository

hephaestus-cloud

agentlas-ai/Agentlas-OS

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.

2026-07-16970

hephaestus-network

agentlas-ai/Agentlas-OS

Use when the user types /hep-network, mentions @Hephaestus, or asks Agentlas to staff a task from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM is the temporary orchestrator.

2026-07-16970

hephaestus-network

agentlas-ai/Agentlas-OS

Use when the user asks OpenClaw to staff a task from Agentlas Hub agents or teams. The active host LLM chooses from the Agent Workforce Ontology.

2026-07-15970

hephaestus-build

agentlas-ai/Agentlas-OS

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.

2026-07-14970

hephaestus-storm

agentlas-ai/Agentlas-OS

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 work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.

2026-07-14970

agentlas-auto-activation

agentlas-ai/Agentlas-OS

Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.

2026-07-13970

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

Read AGENTS.md.
Read .agentlas/mode-map.json.
Run mode classification.
Ask clarify questions when missing details change files, adapters, or public/private boundary.
Pick one team member:
- Single Agent Builder;
- Multi Agent Team Builder;
- Agentlas Packager.
Load only the matching support skills.
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.
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.
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.
Verify with scripts/verify-package.sh.

Output

Return status, evidence, output, global_commands, and blockers.