agent-creator
/agent-creator
Projektuje definicję subagenta (specjalista, rola lub team lead) z właściwym frontmatter, narzędziami, izolacją, pamięcią i promptem systemowym.
- Autor
- krzysztofsurdy ↗
- Repozytorium
- code-virtuoso ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 16
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Projektuje definicję subagenta (specjalista, rola lub team lead) z właściwym frontmatter, narzędziami, izolacją, pamięcią i promptem systemowym.
Argumenty
/agent-creator [optional: archetype - specialist, role, team-lead]
Oryginalny opis (EN)
Interactive tool to design a sub-agent definition (specialist, role, or team-lead) with the right frontmatter, tools, isolation, memory, and system prompt. Use when asked to create a sub-agent, write an agent file, or scaffold a role agent.
Jak działa
- Core Principles
- Agent vs skill
- Archetype selection
- Rules that shape every agent
- Workflow
- Reference Files
- Integration with Other Skills
Podgląd SKILL.md
---
name: agent-creator
description: Interactive tool to design a sub-agent definition (specialist, role, or team-lead) with the right frontmatter, tools, isolation, memory, and system prompt. Use when asked to create a sub-agent, write an agent file, or scaffold a role agent.
user-invocable: true
argument-hint: "[optional: archetype - specialist, role, team-lead]"
---
# Agent Creator
Create a sub-agent that earns its context window. Most agents fail because the definition is vague, not because the model is weak: the trigger is unclear, the tool list sprawls, the body mixes persona and procedure, and there is no output contract. This skill researches first, then walks through a six-phase design that produces a focused, least-privileged agent with predictable output.
## Core Principles
| Principle | Meaning |
|---|---|
| **One job, one agent** | An agent that does two things does neither well. Split the responsibility before writing. |
| **Least privilege** | Grant the smallest tool set that lets the agent finish its job. Read-only by default. |
| **Trigger-first description** | The `description` field is the only thing read before delegation. Include keywords and "when to use". |
| **Contract over conversation** | Define explicit input, process, and output. Agents are not chat sessions. |
| **Isolation for source code** | If the agent changes source code, run it in a worktree so the orchestrator can review before merging. Documentation-only writers and planning roles may run in place. |
| **Portable body, platform frontmatter** | Keep the system prompt agent-agnostic. Adapt frontmatter fields per target platform. |
---
## Agent vs skill
Confirm an agent is the right primitive before creating one.
| Use a Skill | Use an Agent |
|---|---|
| Reference material (patterns, checklists, schemas) | Work to perform (investigate, review, implement) |
| Loaded into an existing session | Runs in its own context window |
| Passive knowledge | Active actor with tools and a workflow |
| "Where do I learn about X" | "Do X for me and return a result" |
If the answer is reference material, stop and use the `skill-writer` skill instead. If the answer is work, continue.
---
## Archetype selection
Agents fall into three archetypes. Pick one before designing.
| Archetype | Scope | Memory | Changes source code | Typical examples |
|---|---|---|---|---|
| **Specialist** | Single, repeatable task type | Stateless | Rarely (implementer only) | Investigator, Reviewer, Refactor Scout, Dependency Auditor, Test Gap Analyzer |
| **Role** | Entire domain of responsibility: the agent plus its `roles/<role>/` reference files | Often `project` | Dev roles yes, others no | Product Manager, Architect, Backend Dev, QA Engineer, Project Manager |
| **Team-Lead** | Coordinates multiple workers in parallel | Stateless | No (delegates) | Orchestrator, release-train lead, review dispatcher |
### Decision tree
1. Does the agent do **one repeatable task type** (review this PR, investigate this area, audit dependencies)? -> **Specialist**
2. Does the agent **own a domain** across many task types and benefit from remembering context across sessions (requirements, architecture decisions, risk register)? -> **Role**
3. Does the agent need to **spawn and coordinate other agents** working in parallel (research teams, multi-layer refactors)? -> **Team-Lead**. If the recipe is fixed (same roster, phases, and gates every run), a team workflow fits better than an agent, see the rules below
If the user provided an archetype as an argument, use it. Otherwise present a selectable menu using `AskUserQuestion` (or the platform's equivalent interactive prompt) with the three options from the table above.
See [references/archetypes.md](references/archetypes.md) for worked examples of each archetype and the anti-patterns to avoid.
---
## Rules that shape every agent
These come from the repository specs ([agent-spec](https://github.com/krzysztofsurdy/code-virtuoso/blob/main/spec/agent-spec.md), [team-spec](https://github.com/krzysztofsurdy/code-virtuoso/blob/main/spec/team-spec.md)) and were checked against Claude Code. Apply them in every phase.
| Topic | Rule |
|---|---|
| Edit and Write | Pair them with `isolation: worktree` only when the agent changes source code. Documentation-only writers and planning roles that write only planning documents run in place |
| `memory` | Claude Code enables Read, Write, and Edit for any agent that sets `memory`, so the agent is no longer read-only. Add it only when the agent keeps notes across sessions, and tell the user that it can write |
| Roles | A role is one agent plus reference files in `roles/<role>/` (templates, checklists). The body lists them by path, using `${CLAUDE_PLUGIN_ROOT}/roles/<role>/<file>` with a repository-relative fallback. There is no role skill, and nothing preloads the files |
| `skills` preload | At most four, only skills needed on every run. Use bare names: they resolve across every installed plugin. A missing skill is skipped without an error. Run-by-name skills (`disable-model-invocation: true`) cannot be preloaded. Preloads do not load when the agent is the main session (`claude -p --agent`), so the agent must work without them |
| Plugin agents | `permissionMode`, `hooks`, and `mcpServers` are ignored. Put hooks and MCP servers in the plugin instead |
| `expects` and `produces` | Documentation for orchestrators and teams. Harnesses ignore them, so the body must still handle missing input |
| Teams | A team is a Markdown recipe plus a workflow script (`workflows/<name>.js`), not an agent and not a config file. There is no `TeamCreate` tool. A team-lead agent spawns named agents and needs a pinned `Agent(...)` list |
| Codex | Codex plugins cannot ship agents. After adding or editing an agent run `python3 scripts/build-codex-agents.py`, which generates `codex/agents/<name>.toml`. Never edit the TOML by hand |
| Saved choices | Tuning lives in the layered config under `agents.<name>`, never next to the agent file. See [tuning.md](references/tuning.md) |
---
## Workflow
This skill uses guided phases. Each phase is a separate file, loaded one at a time. Every phase ends with a gate: wait for user confirmation before proceeding. Do not skip or merge phases.
| Phase | File | What it covers |
|---|---|---|
| 0 | [Research gate](phases/00-research.md) | Research the role and the platform agent formats, search for prior art and decide, build the fact ledger and research notes |
| 1 | [Purpose and trigger](phases/01-purpose-and-trigger.md) | What the agent does, when to delegate, out-of-scope, output shape, archetype |
| 2 | [Name and identity](phases/02-name-and-identity.md) | Kebab-case name, collision check, user confirmation |
| 3 | [Capabilities](phases/03-capabilities.md) | Tool permissions, isolation, memory, role reference files, preloaded skills |
| 4 | [System prompt](phases/04-system-prompt.md) | Five-section contract: Input, Process, Rules, Output |
| 5 | [Placement and scope](phases/05-placement-and-scope.md) | Where the file lives: this library, project, personal, plugin, session |
| 6 | [Validate and write](phases/06-validate-and-write.md) | Checklist, file creation, registration, Codex build |
Start by loading Phase 0. After the user confirms each phase, load the next. Never load multiple phases at once and never skip one. Skip Phase 0 only when the user says so in plain words ("no research", "skip research", "I know the role, just write it"). That also skips the prior-art search. Record "research skipped at user request" in the notes and the PR, and do not state specific platform fields, versions, or limits from memory unless marked `(unverified)`.
---
## Reference Files
| Reference | Contents |
|---|---|
| [archetypes.md](references/archetypes.md) | Worked examples of specialist, role, and team-lead agents, plus anti-patterns |
| [frontmatter-fields.md](references/frontmatter-fields.md) | Full field reference, portable vs platform-specific, and examples |
| [tool-selection.md](references/tool-selection.md) | Least-privilege tool allowlists, per-archetype defaults, and denylist patterns |
| [system-prompts.md](references/system-prompts.md) | System prompt patterns: role-input-process-rules-output contract, worked examples |
| [platforms.md](references/platforms.md) | Scope paths, platform-specific frontmatter fields, Codex generation, and team considerations |
| [prior-art.md](references/prior-art.md) | Where and how to search for similar agents, how to compare them, the install-or-design decision rule, license and safety notes |
| [validation.md](references/validation.md) | Pre-publish checklist and common rejection reasons |
---
## Integration with Other Skills
| Situation | Recommended Skill |
|---|---|
| Creating a reference skill instead of an agent | `skill-writer` |
| Researching the role, platform formats, or comparable agents in Phase 0 | `research` |
| Writing AI rules files for an agent platform | `agentic-rules-writer` |
| Designing how multiple agents interact in a workflow | `agent-orchestration` |
| Deciding what belongs in an agent body versus instruction files | `context-engineering` |
| Authoring a ticket or PRD that spawns the agent | `ticket-writer` |
Pliki w paczce (16)
- SKILL.md 9 KB
- phases/00-research.md 4 KB
- phases/01-purpose-and-trigger.md 2 KB
- phases/02-name-and-identity.md 1 KB
- phases/03-capabilities.md 3 KB
- phases/04-system-prompt.md 2 KB
- phases/05-placement-and-scope.md 2 KB
- phases/06-validate-and-write.md 2 KB
- references/archetypes.md 10 KB
- references/frontmatter-fields.md 10 KB
- references/platforms.md 8 KB
- references/prior-art.md 6 KB
- references/system-prompts.md 9 KB
- references/tool-selection.md 6 KB
- references/tuning.md 5 KB
- references/validation.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · krzysztofsurdy/code-virtuoso | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| Navinspire-ia/navin | 100 | AGPL-3.0 |
| hotovo/aider-desk | 100 | Apache-2.0 |
| OpenHands/extensions | 100 | MIT |
| openjiuwen-ai/jiuwenswarm | 100 | Apache-2.0 |
| agdev/claude-code | 100 | MIT |
| mhylle/claude-skills-collection | 100 | MIT |
| fusengine/agents | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f2491a83fbe2 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100cowork
Dodaje do Claude Code warstwę wielu person: osobna rola agenta na czat lub wywołanie CLI (coder, browser, inbox, research) z własnymi narzędziami, serwerami MCP, promptem systemowym i przestrzenią roboczą. - 100agent-development
Projektuje i pisze subagentów Navin (plik z opisem, przykładami, narzędziami, modelem i promptem) oraz testuje, czy Navin do nich deleguje. - 100agent-template
Generuje własnego agenta z szablonu, tworząc nowego subagenta od zera lub plik agenta z poprawnym frontmatter. - 100skill-creator
Prowadzi interaktywnie przez tworzenie skilli zgodnych ze standardem Skills 2.0: definicję przypadku użycia, frontmatter, instrukcje, ewaluacje i walidację. - 100skill-creator
Projektuje i pisze dobre skille od zakresu po frontmatter, strukturę i przegląd bezpieczeństwa, a potem je waliduje. - 100start-team
Uruchamia zespół agentów dla projektu w jednym kroku, sprawdza wymagania i ustawia rolę lidera w sesji.