Agent skill

Team Builder Packaging

by agentlas-ai in agentlas-ai/Agentlas-OS

A skill your agent uses 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.

Apache-2.0Auto-check passedAgent Workflows

Install Team Builder Packaging

skills CLI

$ npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install agentlas-ai/Agentlas-OS team-builder-packaging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/team-builder-packaging .claude/skills/team-builder-packaging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "team-builder-packaging" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/team-builder-packaging into .claude/skills/team-builder-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder-packaging", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/team-builder-packaging

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install agentlas-ai/Agentlas-OS team-builder-packaging --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/team-builder-packaging .agents/skills/team-builder-packaging && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "team-builder-packaging" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/team-builder-packaging into .agents/skills/team-builder-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder-packaging", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install agentlas-ai/Agentlas-OS team-builder-packaging --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/team-builder-packaging .cursor/skills/team-builder-packaging && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "team-builder-packaging" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/team-builder-packaging into .cursor/skills/team-builder-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder-packaging", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/agentlas-ai/Agentlas-OS.git --path skills/team-builder-packaging

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install agentlas-ai/Agentlas-OS team-builder-packaging --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/team-builder-packaging .gemini/skills/team-builder-packaging && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "team-builder-packaging" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/team-builder-packaging into .gemini/skills/team-builder-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder-packaging", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install agentlas-ai/Agentlas-OS team-builder-packaging

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/team-builder-packaging .github/skills/team-builder-packaging && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "team-builder-packaging" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/team-builder-packaging into .github/skills/team-builder-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder-packaging", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install agentlas-ai/Agentlas-OS team-builder-packaging --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/team-builder-packaging .opencode/skills/team-builder-packaging && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "team-builder-packaging" agent skill from https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/team-builder-packaging into .opencode/skills/team-builder-packaging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder-packaging", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: team-builder-packaging
GitHub stars: 1.6k
Token cost: ~642 tokens
SKILL.md length: 265 words
Files: 1
Skills in repo: 53
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses 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.

Works in 9 steps: Start with the orchestrator/HQ. → Run… → Add PM Soul or project owner. → …
Auditing a multi-role agent team package with orchestrator
SKILL.md covers Procedure and Output
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Team Builder Packaging is an agent skill from agentlas-ai/Agentlas-OS. 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.

Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Agent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model. The licence is Apache-2.0.

When your agent uses it

Auditing a multi-role agent team package with orchestrator
Runtime adapters

Example prompts

“/team-builder-packaging”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

Start with the orchestrator/HQ.
Run contracts/builder-interview-research-gate.md before writing the roster
Add PM Soul or project owner.
Add Memory Curator and Memory Ticket handoff.
Add Policy Gate, eval judge, and QA/evidence gate.
Add workers only for real domain ownership proved by interview or research.
Add docs/builder-interview.md, docs/research-sources.md,
Encode handoff and return contracts.
Emit one orchestrator/HQ global command in .agentlas/global-commands.json

What it can do on your machine

Read from SKILL.md and the folder at commit 6254906. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Team Builder Packaging loads about 642 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 265 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~49
When it runs · the whole SKILL.md, loaded when a task matches: ~642

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from agentlas-ai/Agentlas-OS at commit 6254906, republished under its Apache-2.0 licence (© agentlas-ai). 265 words, ~642 tokens.

Download SKILL.mdSave it as .claude/skills/team-builder-packaging/SKILL.md (or your agent's skills folder).

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

Start with the orchestrator/HQ.
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.
Add PM Soul or project owner.
Add Memory Curator and Memory Ticket handoff.
Add Policy Gate, eval judge, and QA/evidence gate.
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:
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.
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.

Output

Return team_topology, nodes, edges, memory_architecture, gates, runtime_adapters, global_commands, and verification.

Files

Just SKILL.md in skills/team-builder-packaging of agentlas-ai/Agentlas-OS.

Open the folder on GitHubat commit 6254906

Compare with similar skills

Team Builder Packaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Team Builder Packaging compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Team Builder Packaging this skillagentlas-ai/Agentlas-OS	1.6k	—	~642	Automated safety check: Pass	Apache-2.0	yesterday
MCP Server Builderanthropics/skills	180k	63 repos	~2.3k	Automated safety check: Pass	Apache-2.0	today
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	38k	10 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today
Using Superpowersfarm-fe/farm	5.6k	35 repos	~1.4k	Automated safety check: Pass	MIT	17 days ago
Executing Plans Inlineobra/superpowers	297k	2 repos	~5.1k	Automated safety check: Pass	MIT	today
Skill CreatorAzure/azqr	795	89 repos	~8.2k	Automated safety check: Pass	Apache-2.0	today

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 63 repos~2.3k tokens
Agent WorkflowsAuto-check passed
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
38k GitHub starsUsed in 10 repos~4.1k tokens
Agent WorkflowsAuto-check: notes
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
5.6k GitHub starsUsed in 35 repos~1.4k tokens
Agent WorkflowsAuto-check passed
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
297k GitHub starsUsed in 2 repos~5.1k tokens
Agent WorkflowsAuto-check passed
Skill Creator
Azure/azqr
Official
Create new skills, modify and improve existing skills, and measure skill performance.
795 GitHub starsUsed in 89 repos~8.2k tokens
Agent WorkflowsAuto-check passed
Claude Code Agent Development
anthropics/claude-plugins-official
Official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
38k GitHub starsUsed in 7 repos~2.8k tokens
Agent WorkflowsAuto-check passed

More from agentlas-ai/Agentlas-OS

All 53 skills in this repo

Agentlas Security Scan
agentlas-ai/Agentlas-OS
A skill your agent uses when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to…
1.6k GitHub stars~822 tokensUpdated yesterday
Auto-check passed
Hephaestus Build
agentlas-ai/Agentlas-OS
A skill your agent uses when the user types /prompts:hep-build or /agentlas-build, mentions @Hephaestus for build work, asks to create a single Agentlas agent, create a multi-agent team, or package…
1.6k GitHub stars~2.2k tokensUpdated yesterday
Auto-check passed
Hephaestus Graph
agentlas-ai/Agentlas-OS
A skill your agent uses when the user types /hep-graph or asks to create, list, inspect, or request a run of an Agentlas automation graph.
1.6k GitHub stars~498 tokensUpdated yesterday
Auto-check passed
Hephaestus Upload
agentlas-ai/Agentlas-OS
A skill your agent uses when the user types $hephaestus-upload, /hep-upload, or /agentlas-upload, or asks to upload, publish, or list an Agentlas agent or team.
1.6k GitHub stars~1.3k tokensUpdated yesterday
Auto-check passed
Routing Card Authoring
agentlas-ai/Agentlas-OS
A skill your agent uses 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.
1.6k GitHub stars~2.7k tokensUpdated yesterday
Auto-check passed
Hephaestus Network
agentlas-ai/Agentlas-OS
A skill your agent uses when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner…
1.6k GitHub stars~5.8k tokensUpdated yesterday
Auto-check passed

Questions about Team Builder Packaging

What does Team Builder Packaging do?

A skill your agent uses 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 is an agent skill from agentlas-ai/Agentlas-OS. 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.

When should I use Team Builder Packaging?

Team Builder Packaging fits situations like: auditing a multi-role agent team package with orchestrator; runtime adapters.

How do I install Team Builder Packaging in Claude Code?

Run `npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a claude-code`. Or copy the skill folder (skills/team-builder-packaging in agentlas-ai/Agentlas-OS) into .claude/skills/team-builder-packaging in your project. Claude Code loads it when a task matches its description.

How do I install Team Builder Packaging in Codex?

Run `npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a codex`. Or copy the skill folder (skills/team-builder-packaging in agentlas-ai/Agentlas-OS) into .agents/skills/team-builder-packaging in your project. Codex loads it when a task matches its description.

Can I use Team Builder Packaging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentlas-ai/Agentlas-OS --skill team-builder-packaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-builder-packaging, .gemini/skills/team-builder-packaging, .github/skills/team-builder-packaging and .opencode/skills/team-builder-packaging in your project.

What does Team Builder Packaging need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Builder Packaging is instructions for the agent only.

Does Team Builder Packaging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Team Builder Packaging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Team Builder Packaging use?

Team Builder Packaging is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Team Builder Packaging use?

About 642 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Team Builder Packaging?

Skills that share tags, products or a category with Team Builder Packaging: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Builder Packaging?

agentlas-ai (a GitHub organization) maintains it in agentlas-ai/Agentlas-OS, which has 1,582 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 8, 2026.

Source: agentlas-ai/Agentlas-OS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Team Builder Packaging

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Team Builder Packaging

Procedure

Output

Files

Compare with similar skills

Similar skills

More from agentlas-ai/Agentlas-OS

Related

Questions about Team Builder Packaging