Use when generating or auditing a multi-role agent team package with orchestrator, workers, handoffs, Memory Ticket outputs, and runtime adapters (PM Soul, Memory Curator, Policy Gate, eval and QA are OS-resident).
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./codex/plugins/agentlas-core-engine-meta-agent/runtime-support/skills/team-builder-packaging/SKILL.mdThe canonical home for this skill is team-builder-packaging in agentlas-ai/Agentlas-OS
Start with the orchestrator/HQ.
Run contracts/builder-interview-research-gate.md before writing the roster:
assess supplied context and ask only material gaps, including zero questions
when sufficient (8-12 only if that many gaps remain); research official sources, similar agent
repositories or comparables, academic/professional theory, and plugin docs,
compare tool/plugin choices, and write the domain-expert synthesis plus
prompt-performance contract.
Add a project owner role if the team needs one.
Add the Memory Ticket handoff (the Memory Curator is OS-resident).
Rely on the OS-resident Policy Gate, eval judge, and QA/evidence gate; do not package them.
Add workers only for real domain ownership proved by interview or research.
Add docs/builder-interview.md, docs/research-sources.md,
docs/tool-selection.md, docs/domain-expert-synthesis.md,
docs/prompt-performance-contract.md, and
.agentlas/capability-eval-plan.json unless explicitly creating a minimal
private scaffold.
Encode handoff and return contracts.
Emit one orchestrator/HQ global command in .agentlas/global-commands.json
and runtime command files. Do not expose worker commands unless requested.
9b. Declare the execution graph in manifest.json. This is what the Hub runtime
reads to build the team; a package that omits it is published, charged for as
a team, and can never be called:
{
"entrypoints": { "orchestrator": "agents/00-orchestrator/agent.md" },
"roster": ["agents/10-<role>/agent.md", "agents/20-<role>/agent.md"]
}Write both keys explicitly. The runtime also accepts older spellings
(entrypoint, orchestrator, entry; workers, members, team) and can
derive the roster from agents/<name>/agent.md, but relying on that leaves
the team's shape implicit and it drifts. Note that entry in agentlas.json
is the PACKAGE entrypoint, not the team manager — never reuse it for that.
Emit runtime adapters and package verification.
Run scripts/verify-team-package.sh <package-root> before reporting
completed. If it fails, do not hand off a result; correct the package by
adding an orchestrator/HQ plus company-blueprint topology or by collapsing
it to a valid single-agent package.
Return team_topology, nodes, edges, memory_architecture, gates,
runtime_adapters, global_commands, and verification.
Canonical home
since Jul 28, 2026
Also appears in
since Oct 7, 2026
since Aug 20, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.