Skip to content

docs(agent-development): enhance content completeness and documentation #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sjnims merged 1 commit into from
Dec 8, 2025
Merged

docs(agent-development): enhance content completeness and documentation #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions plugins/plugin-dev/skills/agent-development/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,6 +156,12 @@ Which model the agent should use.
- `opus` - Claude Opus (most capable, expensive)
- `haiku` - Claude Haiku (fast, cheap)

**When to choose:**

- `haiku` - Fast, simple tasks; quick analysis; cost-sensitive operations
- `sonnet` - Balanced performance; most use cases (default recommendation)
- `opus` - Complex reasoning; detailed analysis; highest capability needed

**Recommendation:** Use `inherit` unless agent needs specific model capabilities.

### color (required)
Expand Down Expand Up @@ -390,6 +396,8 @@ Output: [What to provide]
| color | Yes | Color name | blue |
| tools | No | Array of tool names | ["Read", "Grep"] |

> **Note:** Agents use `tools` to restrict tool access. Skills use `allowed-tools` for the same purpose. The field names differ between component types.

### Best Practices

**DO:**
Expand All @@ -414,9 +422,9 @@ Output: [What to provide]

For detailed guidance, consult:

- **`references/system-prompt-design.md`** - Complete system prompt patterns
- **`references/triggering-examples.md`** - Example formats and best practices
- **`references/agent-creation-system-prompt.md`** - The exact prompt from Claude Code
- **`references/system-prompt-design.md`** - Four system prompt patterns (Analysis, Generation, Validation, Orchestration) with complete templates and common pitfalls
- **`references/triggering-examples.md`** - Example block anatomy, four example types, template library, and debugging guide
- **`references/agent-creation-system-prompt.md`** - The exact prompt used by Claude Code's agent generation feature with usage patterns

### Example Files

Expand All @@ -442,7 +450,7 @@ To create an agent for a plugin:
4. Write frontmatter with all required fields
5. Write system prompt following best practices
6. Include 2-4 triggering examples in description
7. Validate with `scripts/validate-agent.sh`
7. Validate with `./skills/agent-development/scripts/validate-agent.sh agents/your-agent.md`
8. Test triggering with real scenarios
9. Document agent in plugin README

Expand Down
Loading