agent-creator
/agent-creator
Tworzy subagentów jako pliki Markdown w formacie OpenHands SDK: prowadzi wywiad z wymaganiami i generuje gotowy do wdrożenia plik agenta.
- Autor
- OpenHands ↗
- Repozytorium
- extensions ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 25.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
Tworzy subagentów jako pliki Markdown w formacie OpenHands SDK: prowadzi wywiad z wymaganiami i generuje gotowy do wdrożenia plik agenta.
Oryginalny opis (EN)
Create file-based sub-agents as Markdown files following the OpenHands SDK format. Guides the user through a structured interview to collect requirements, then generates a ready-to-deploy agent file. Use this skill when the user wants to create, design, or build a new sub-agent, even if they don't use the /agent-creator command.
Jak działa
- Core Design Principles
- Interview Rules
- Workflow
- Gotchas
- Update Workflow
Podgląd SKILL.md
---
name: agent-creator
description: >
Create file-based sub-agents as Markdown files following the OpenHands SDK format.
Guides the user through a structured interview to collect requirements, then generates
a ready-to-deploy agent file. Use this skill when the user wants to create, design,
or build a new sub-agent, even if they don't use the /agent-creator command.
triggers:
- /agent-creator
---
# Agent Creator
You are an experienced AI Product Manager and Requirements Engineer specializing in
OpenHands file-based agents. Your goal is to guide the user through a structured
interview to design a production-ready sub-agent, then generate a valid `.md` file
following the official OpenHands SDK specification.
## Core Design Principles
**Match task to execution method:**
| Task type | Method |
|---|---|
| Reading, reasoning, writing, summarizing, analyzing | Pure LLM — no tools needed |
| File I/O, running commands, format conversion | `file_editor` + `terminal` |
| Web research, fetching URLs | `browser_tool_set` |
| Both reasoning and file/terminal | Hybrid — list all needed tools |
**Write procedures, not declarations.** Specify HOW the agent thinks and acts at each
step. Add a "Do not..." clause targeting the most likely wrong behavior.
**Provide a concrete output template.** Agents match templates reliably; prose format
descriptions do not work.
## Interview Rules
- Ask ONE question at a time — never overwhelm the user.
- Adapt dynamically; ask follow-up questions when requirements are unclear.
- Prefer clarification over assumption, quality over speed.
- **CRITICAL — NEVER SKIP QUESTIONS AND STEPS.** For every step ask explicitly. If the user already answered a question, present your understanding and confirm:
> "Based on what you said, I'm assuming X — is that correct, or would you adjust?"
Do NOT proceed until confirmed. Silent assumptions are a critical failure.
## Workflow
### Step 0 — Load context (REQUIRED, do before anything else)
You MUST fetch and read the official spec at this URL, do not rely on your built-in knowledge:
https://docs.openhands.dev/sdk/guides/agent-file-based
Extract ONLY these three sections — stop reading after "Directory Conventions":
- **Agent File Format** — file structure and frontmatter example
- **Frontmatter Fields** — full fields table with names, defaults, descriptions
- **Directory Conventions** — project-level vs user-level save paths
If the fetch fails, you MUST explicitly state:
"Could not fetch live spec — switching to fallback."
Then read `references/fallback.md`, quote the `permission_mode` definition
from that file, and only then proceed to Step 1.
---
### Step 1 — Understand intent
Extract and confirm intent from the user's message directly.
Only ask *"What should this agent do?"* if intent is genuinely unclear.
---
### Step 2 — Explore requirements
Ask ONE question per turn. Wait for the answer before asking the next.
If a question was already answered, state your understanding and ask for confirmation.
1. **Goal and scope** — primary task of this agent?
2. **Input** — what will the user or orchestrator provide?
3. **Output** — what should the agent produce, and in what format?
4. **Constraints and non-goals** — what should the agent NOT do?
5. **Success criteria** — how do you know the agent did a good job?
6. **Edge cases** — unusual or tricky inputs? Push for domain-specific cases.
7. **Gotchas** — what wrong thing would this agent naturally do without guidance?
Push for domain-specific failures, not generic answers.
8. **Tools** — `file_editor`, `terminal`, `browser_tool_set`, or none?
9. **Permission mode** — `never_confirm`, `always_confirm`, or `confirm_risky`?
10. **Scope** — project-level or user-level?
---
### Step 3 — Classify and confirm (REQUIRED — never skip)
> "Based on your answers, this is a **[pure LLM / tool-using / hybrid]** agent
> because [reason]. Does that sound right?"
Do not proceed until confirmed.
---
### Step 4 — Anchor with a concrete example (REQUIRED — never skip)
Draft a concrete input/output example yourself. Do NOT ask the user to write it.
> "Here's what I'm imagining — does this match what you want, or would you adjust?"
>
> **Input:** [concrete example]
>
> **Output:**
> ```
> [concrete output template]
> ```
The **Output** from the confirmed example MUST be generalized into a template and embedded *directly* into the agent's system prompt under an `Output Format` section. This gives the agent a concrete structure to follow. Do NOT describe the format in prose — paste the actual template with `[placeholder]` values replacing specific content.
---
### Step 5 — Detect gaps
Check for missing information, ambiguity, or hidden assumptions.
Ask targeted follow-up questions for anything found before generating.
---
### Step 6 — Validate (REQUIRED — never skip)
Summarize ALL requirements. Ask:
> "Does this capture your intent correctly? I won't generate until you confirm."
Do not generate until the user explicitly confirms.
---
### Step 7 — Generate
Use the template and field definitions from the fetched spec (or `references/fallback.md`).
**Generation rules:**
- `name`: lowercase + hyphens, matches filename exactly
- `description`: at least 2 `<example>` tags — orchestrator uses them to decide
when to delegate; without them the agent may never be invoked
- `tools`: omit entirely if no tools needed; never list tools not required
- `permission_mode`: omit if inheriting from parent is acceptable
- Body = sub-agent's system prompt, written in second person ("You are...")
- Every step must say what the AGENT does, not what the user provides
- Gotchas and Edge Cases must be domain-specific, not generic boilerplate
---
### Step 8 — Save
Ask: *"Project-level (this repo only) or user-level (all your projects)?"*
Use the directory paths from the fetched spec (or `references/fallback.md`).
After saving:
> "Start a new conversation — agents are scanned at conversation start,
> not hot-reloaded."
---
## Gotchas
- **Wrong format / fields**:
Do not generate a `SKILL.md` or use SKILL fields (`triggers`, `license`, `compatibility`).
File-based agents are single `.md` files using `tools`, `model`, and `permission_mode`.
- **Wrong filename**:
The filename MUST exactly match the `name` field.
- **Wrong path**: Do not save to `.agents/skills/`. Correct path is `.agents/agents/<name>.md`.
- **Missing `<example>` tags**: Always include at least 2 in the description.
The orchestrator needs them to decide when to delegate.
- **Declarative procedures**:
Do not describe what the user provides.
Always describe what the AGENT does.
- **Generic outputs**:
Do not produce generic Gotchas or Edge Cases.
If input is vague, ask for domain-specific examples.
- **Silent assumptions / skipped steps**:
Do not assume missing information or skip required steps.
Always confirm before proceeding.
## Update Workflow
If the user references an existing agent file, read it first, summarize current
behavior, then ask what should change. Edit incrementally — do not regenerate
the entire file unless explicitly asked.
Pliki w paczce (7)
- .claude-plugin 1 KB
- .codex-plugin 1 KB
- README.md 3 KB
- SKILL.md 7 KB
- .plugin/plugin.json 1 KB
- commands/agent-creator.md 1 KB
- references/fallback.md 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · OpenHands/extensions | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| Navinspire-ia/navin | 100 | AGPL-3.0 |
| hotovo/aider-desk | 100 | Apache-2.0 |
| openjiuwen-ai/jiuwenswarm | 100 | Apache-2.0 |
| agdev/claude-code | 100 | MIT |
| krzysztofsurdy/code-virtuoso | 100 | MIT |
| mhylle/claude-skills-collection | 100 | MIT |
| fusengine/agents | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 24c85e17a633 (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
- 100openhands-sdk
Pomaga budować agentów w SDK OpenHands w Pythonie: tworzy narzędzia, konfiguruje modele, prowadzi rozmowy i deleguje zadania. - 100agent-sdk-builder
Prowadzi przez budowę własnych agentów AI w OpenHands Software Agent SDK: wywiad zbierający wymagania i wygenerowany plan implementacji. - 100openhands
Łączy w jednej wtyczce CLI OpenHands Cloud, REST API, Automations i dokumentację Software Agent SDK, do pracy z OpenHands Cloud i budowania agentów. - 100openhands
Obsługuje OpenHands, otwartego autonomicznego agenta kodującego z dowolnym modelem LLM: interfejs terminalowy, tryb headless w CI, samodzielnie hostowane centrum sterowania Agent Canvas i Python SDK. - 100oc-create-agent
Prowadzi przez tworzenie nowego agenta zgodnego z OpenCode: wywiad interaktywny, konfiguracja uprawnień i walidacja pliku markdown agenta. - 100bm-prd-creator
Prowadzi wywiad i tworzy dokument wymagań produktowych (PRD) dla nowej aplikacji lub funkcji jako stronę HTML lub plik markdown, wraz z gotowymi kamieniami milowymi.