team-builder-packaging
/team-builder-packaging
Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters.
- Author
- agentlas-ai ↗
- Repository
- Agentlas-OS ↗
- Licence
- Apache-2.0
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters.
Original author description
Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters.
How it works
- Procedure
- Output
SKILL.md preview
---
name: team-builder-packaging
description: "Use when generating or auditing a multi-role agent team package with orchestrator, PM Soul, Memory Curator, Policy Gate, workers, eval, QA, handoffs, and runtime adapters."
---
# Team Builder Packaging
## Procedure
1. Start with the orchestrator/HQ.
2. Run `contracts/builder-interview-research-gate.md` before writing the roster:
ask an 8-12 question first batch, 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.
3. Add PM Soul or project owner.
4. Add Memory Curator and Memory Ticket handoff.
5. Add Policy Gate, eval judge, and QA/evidence gate.
6. Add workers only for real domain ownership proved by interview or research.
7. 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.
8. Encode handoff and return contracts.
9. 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:
```json
{
"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.
10. Emit runtime adapters and package verification.
11. 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.
## Output
Return `team_topology`, `nodes`, `edges`, `memory_architecture`, `gates`,
`runtime_adapters`, `global_commands`, and `verification`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · agentlas-ai/Agentlas-OS | 100 | Apache-2.0 |
| agentlas-ai/Agentlas-OS | 100 | Apache-2.0 |
Identical content appears in 4 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 51a60f82e327 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90dev_team
Orchestrate a multi-agent dev/agency team with shared memory, handoffs, and OpenClaw sessions. Use when (1) First-time onboarding — follow references/OPENCLAW_TEAM_SETUP_GUIDE.md (guided variables + master prompt) and references/SKILL-SETUP.md, (2) Running specialized agents… - 96team-coding-workflow
Use when building a multi-role AI coding team pipeline. - 100skill-bundle-curator
Summarize bundle components from agent-bundle.json and repo skill/agent counts. Use when packaging or auditing distributable bundles. NOT for live plugin installs. - 86agent-identity-setup
Use when setting up or resetting agent SOUL, memory, skills. - 100hermes-bot-team-design
Use this skill when an agent needs to design a team of specialist Hermes bots from a project specification. Covers role assignment, SOUL.md authoring, MCP wiring, and group chat setup. - 100soul-create
Generate a SOUL.md identity file from source material, interactive prompts, or an existing voice profile. Use when authoring a persona / soul identity.