AI i agenci · Planowanie
team-builder
/team-builder
Pomaga składać i uruchamiać równoległe zespoły agentów do jednego zadania, wybierając ich z listy.
Dla kogo
- Autor
- SHRIJANAGAIN ↗
- Repozytorium
- Nemo-Cli ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 05.11.2026
Ocena i bezpieczeństwo
100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Przestarzałość
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
Licencja
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Pomaga składać i uruchamiać równoległe zespoły agentów do jednego zadania, wybierając ich z listy.
Oryginalny opis (EN)
Interactive agent picker for composing and dispatching parallel teams. Use when composing and dispatching a parallel team of agents for a task.
Jak działa
- When to Use
- Prerequisites
- Configuration
- How It Works
- Rules
- Examples
Sekcje z nagłówków SKILL.md, w oryginale · 169 linii, 1 021 słów
Podgląd SKILL.md
---
name: team-builder
description: Interactive agent picker for composing and dispatching parallel teams. Use when composing and dispatching a parallel team of agents for a task.
metadata:
origin: community
---
# Team Builder
Interactive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections.
## When to Use
- You have multiple agent personas (markdown files) and want to pick which ones to use for a task
- You want to compose an ad-hoc team from different domains (e.g., Security + SEO + Architecture)
- You want to browse what agents are available before deciding
## Prerequisites
Agent files must be markdown files containing a persona prompt (identity, rules, workflow, deliverables). The first `# Heading` is used as the agent name and the first paragraph as the description.
Both flat and subdirectory layouts are supported:
**Subdirectory layout** — domain is inferred from the folder name:
```
agents/
├── engineering/
│ ├── security-engineer.md
│ └── software-architect.md
├── marketing/
│ └── seo-specialist.md
└── sales/
└── discovery-coach.md
```
**Flat layout** — domain inferred from shared filename prefixes. A prefix counts as a domain when 2+ files share it. Files with unique prefixes go to "General". Note: the algorithm splits at the first `-`, so multi-word domains (e.g., `product-management`) should use the subdirectory layout instead:
```
agents/
├── engineering-security-engineer.md
├── engineering-software-architect.md
├── marketing-seo-specialist.md
├── marketing-content-strategist.md
├── sales-discovery-coach.md
└── sales-outbound-strategist.md
```
## Configuration
Agents are discovered via two methods, merged and deduplicated by agent name:
1. **`nemo agents` command** (primary) — run `nemo agents` to get all agents known to the CLI, including user agents, plugin agents (e.g. `ecc:architect`), and built-in agents. This automatically covers ECC marketplace installs without any path configuration.
2. **File glob** (fallback, for reading agent content) — agent markdown files are read from:
- `./agents/**/*.md` + `./agents/*.md` — project-local agents
- `~/.nemo/agents/**/*.md` + `~/.nemo/agents/*.md` — global user agents
Earlier sources take precedence when names collide: user agents > plugin agents > built-in agents. A custom path can be used instead if the user specifies one.
## How It Works
### Step 1: Discover Available Agents
Run `nemo agents` to get the full agent list. Parse each line:
- **Plugin agents** are prefixed with `plugin-name:` (e.g., `ecc:security-reviewer`). Use the part after `:` as the agent name and the plugin name as the domain.
- **User agents** have no prefix. Read the corresponding markdown file from `~/.nemo/agents/` or `./agents/` to extract the name and description.
- **Built-in agents** (e.g., `Explore`, `Plan`) are skipped unless the user explicitly asks to include them.
For user agents loaded from markdown files:
- **Subdirectory layout:** extract the domain from the parent folder name
- **Flat layout:** collect all filename prefixes (text before the first `-`). A prefix qualifies as a domain only if it appears in 2 or more filenames (e.g., `engineering-security-engineer.md` and `engineering-software-architect.md` both start with `engineering` → Engineering domain). Files with unique prefixes (e.g., `code-reviewer.md`, `tdd-guide.md`) are grouped under "General"
- Extract the agent name from the first `# Heading`. If no heading is found, derive the name from the filename (strip `.md`, replace hyphens with spaces, title-case)
- Extract a one-line summary from the first paragraph after the heading
If no agents are found after running `nemo agents` and probing file locations, inform the user: "No agents found. Run `nemo agents` to verify your setup." Then stop.
### Step 2: Present Domain Menu
```
Available agent domains:
1. Engineering — Software Architect, Security Engineer
2. Marketing — SEO Specialist
3. Sales — Discovery Coach, Outbound Strategist
Pick domains or name specific agents (e.g., "1,3" or "security + seo"):
```
- Skip domains with zero agents (empty directories)
- Show agent count per domain
### Step 3: Handle Selection
Accept flexible input:
- Numbers: "1,3" selects all agents from Engineering and Sales
- Names: "security + seo" fuzzy-matches against discovered agents
- "all from engineering" selects every agent in that domain
If more than 5 agents are selected, list them alphabetically and ask the user to narrow down: "You selected N agents (max 5). Pick which to keep, or say 'first 5' to use the first five alphabetically."
Confirm selection:
```
Selected: Security Engineer + SEO Specialist
What should they work on? (describe the task):
```
### Step 4: Spawn Agents in Parallel
1. Read each selected agent's markdown file
2. Prompt for the task description if not already provided
3. Spawn all agents in parallel using the Agent tool:
- `subagent_type: "general-purpose"`
- `prompt: "{agent file content}\n\nTask: {task description}"`
- Each agent runs independently — no inter-agent communication needed
4. If an agent fails (error, timeout, or empty output), note the failure inline (e.g., "Security Engineer: failed — [reason]") and continue with results from agents that succeeded
### Step 5: Synthesize Results
Collect all outputs and present a unified report:
- Results grouped by agent
- Synthesis section highlighting:
- Agreements across agents
- Conflicts or tensions between recommendations
- Recommended next steps
If only 1 agent was selected, skip synthesis and present the output directly.
## Rules
- **Dynamic discovery only.** Never hardcode agent lists. New files in the directory auto-appear in the menu.
- **Max 5 agents per team.** More than 5 produces diminishing returns and excessive token usage. Enforce at selection time.
- **Parallel dispatch.** All agents run simultaneously — use the Agent tool's parallel invocation pattern.
- **Parallel Agent calls, not TeamCreate.** This skill uses parallel Agent tool calls for independent work. TeamCreate (a Nemo Code tool for multi-agent dialogue) is only needed when agents must debate or respond to each other.
## Examples
```
User: team builder
Nemo:
Available agent domains:
1. Engineering (2) — Software Architect, Security Engineer
2. Marketing (1) — SEO Specialist
3. Sales (4) — Discovery Coach, Outbound Strategist, Proposal Strategist, Sales Engineer
4. Support (1) — Executive Summary
Pick domains or name specific agents:
User: security + seo
Nemo:
Selected: Security Engineer + SEO Specialist
What should they work on?
User: Review my Next.js e-commerce site before launch
[Both agents spawn in parallel, each applying their specialty to the codebase]
Nemo:
## Security Engineer Findings
- [findings...]
## SEO Specialist Findings
- [findings...]
## Synthesis
Both agents agree on: [...]
Tension: Security recommends CSP that blocks inline styles, SEO needs inline schema markup. Resolution: [...]
Next steps: [...]
```
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · SHRIJANAGAIN/Nemo-Cli | 100 | Apache-2.0 |
| curiositech/windags-skills | 100 | Apache-2.0 |
| affaan-m/ECC | 100 | MIT |
| ginaservice/ginaservice-skills | 100 | MIT |
| curiositech/some_claude_skills | 100 | MIT |
| LeoYeAI/openclaw-master-skills | 95 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 3bebdea13f22 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 92dispatching-parallel-agents
Rozdziela zadania niezależne od siebie, bez wspólnego stanu i kolejności, między równoległych agentów, gdy jest ich co najmniej dwa. - 92dispatching-parallel-agents
Rozdziela dwa lub więcej niezależnych zadań bez wspólnego stanu i zależności kolejności na równoległych agentów. - 100team-agents
Uruchamia i koordynuje równoległe zespoły agentów przy zadaniach z co najmniej dwoma niezależnymi strumieniami pracy, od tworzenia do sprzątania. - 100dispatching-parallel-agents
Rozdziela niezależne zadania między równoległe agenty, gdy nie mają wspólnego stanu ani zależności od kolejności. - 100dispatching-parallel-agents
Dzieli niezależne zadania pozbawione wspólnego stanu i kolejności wykonania na równoległe zlecenia dla subagentów. - 100agent-teams
Tworzy zespoły agentów do równoległej współpracy, na przykład zespół recenzentów patrzących na zadanie z różnych perspektyw.