Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.
SkillScore91Maintained
Automatic
◆AI Engineer pack
Last verified 8/24/2026
What it changes
Passed 20 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill91%
Checks it passed that the model alone missed
Designates the role type as Coordinator.
Identifies the communication pattern as broadcast.
Uses the file path agents/data_scrubber/prompt.md.
and 3 more in the full report
6 fixed14 passed either way1 still failing1 broke
Pass-rate lift
+23 pp
Tokens
-7%
Agent turns
0%
Response time
-46%
Model gemini-3.6-flashMeasured 8/24/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
What is the expected relative directory path and file naming structure for storing an individual agent's system prompt for an agent with ID data_scrubber?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses the file path agents/data_scrubber/prompt.md.
Missed
Passed
case-18 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md52 lines4 files
Agent Team Builder
Design and generate production-ready multi-agent team configurations for business workflows through an interactive discovery session. This skill generates configuration files; it does not execute or deploy agents.
Contents
references/team-templates.md — Sales, Support, Research, and Content team starting points.
references/config-schema.md — Full team-config.yaml schema plus advanced features (A2A messaging, scaling, shared context).
references/output-files.md — Files to generate and the final response format.
Workflow
Always complete discovery before designing. Never generate a team config without understanding the business process first.
Run discovery. Ask the user, one area at a time:
Process name (what to automate).
Current state (who is involved, handoff points).
Pain points (where delays, errors, or bottlenecks occur).
Data — manages retrieval, transformation, and storage.
Pick a communication pattern: hub-and-spoke (sequential), pipeline (linear), mesh (collaborative), or broadcast (notification). Start from a template in references/team-templates.md when one fits.
Specify each agent. Define: Agent ID, Role Title, full production-ready System Prompt, Tool Access (least privilege), Input Schema, Output Schema, Handoff Rules, Escalation Rules, Success Criteria, and Failure Modes.
Generate the configuration files. Produce team-config.yaml, per-agent agents/{id}/prompt.md, workflow.md, and test-scenarios.yaml per references/output-files.md, conforming to references/config-schema.md.
Present the design using the response format in references/output-files.md.