team-builder
Intelligently compose and deploy Claude Code Agent Teams based on user requirements. Auto-selects optimal team composition from all available skills and agents (project, user, global, plugin scopes), generates task dependency graphs, and orchestrates team lifecycle. Use when creating multi-agent teams for complex tasks requiring parallel specialized work.
Install with Tessl CLI
npx tessl i github:sc30gsw/claude-code-customes --skill team-builder88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly articulates specific capabilities and includes an explicit 'Use when' clause. The main weakness is trigger term quality - it relies on technical terminology that users may not naturally use when requesting this functionality. The description would benefit from including more natural language variations.
Suggestions
Add natural trigger terms users might say, such as 'coordinate multiple agents', 'divide complex work', 'team up agents', or 'parallel processing with agents'
Include example task types that would trigger this skill, such as 'large refactoring projects', 'multi-file analysis', or 'coordinated code changes'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'compose and deploy Claude Code Agent Teams', 'Auto-selects optimal team composition', 'generates task dependency graphs', and 'orchestrates team lifecycle'. | 3 / 3 |
Completeness | Clearly answers both what (compose/deploy agent teams, auto-select composition, generate dependency graphs, orchestrate lifecycle) AND when ('Use when creating multi-agent teams for complex tasks requiring parallel specialized work'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'multi-agent teams', 'parallel specialized work', and 'complex tasks', but uses more technical jargon ('task dependency graphs', 'orchestrates team lifecycle') than natural user language. Missing common variations users might say like 'coordinate agents', 'team up', or 'divide work'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around multi-agent team orchestration. The specific focus on 'Agent Teams', 'team composition', and 'task dependency graphs' creates a unique domain unlikely to conflict with single-agent or simpler task skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. The deployment sequences, CLI examples, and mode-specific workflows are concrete and executable. Minor verbosity in tables (Domain Detection, Model Selection) could be tightened, but overall the skill effectively teaches team composition and deployment.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., the Domain Detection table repeats information that could be inferred, and some sections like Model Selection Strategy could be more compact). The tables are useful but verbose. | 2 / 3 |
Actionability | Provides concrete CLI examples, specific deployment sequences, clear argument tables, and executable usage patterns. The deployment sequence is step-by-step with actual commands/tool calls. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows for AUTO, TEMPLATE, and MANUAL modes with numbered sequences. The deployment sequence is explicit with proper ordering. Includes validation via --dry-run and --plan-approval for high-risk work. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, then detailed sections. References external files (team-templates.md, composition-guide.md, discover_resources.py) appropriately with one-level-deep navigation. Content is appropriately split between SKILL.md and reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
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.