mcpbeat

Agentlas Core Engine Meta Agent

agentlas-ai/agentlas-os-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.

385 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1165
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/agentlas-ai/Agentlas-OS --skill agentlas-core-engine-meta-agent

The instruction itself

3 sections, as written by the author

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.

10. Verify with scripts/verify-package.sh.

Output

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

How to use it

Copy the folder

Take agentlas-ai/agentlas-os-agentlas-core-engine-meta-agent from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.