agent-development
Design and build custom Claude Code agents with effective descriptions, tool access patterns, and self-documenting prompts. Covers Task tool delegation, model selection, memory limits, and declarative instruction design. Use when: creating custom agents, designing agent descriptions for auto-delegation, troubleshooting agent memory issues, or building agent pipelines.
npx skills add majiayu000/claude-skill-registry --skill agent-development-brendadeeznuts1111-tier-1380-omega --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent Development for Claude Code Build effective custom agents for Claude Code with proper delegation, tool access, and prompt design. ## Agent Description Pattern The description field determines whether Claude will automatically delegate tasks. ### Strong Trigger Pattern ```yaml --- name: agent-name description: | [Role] specialist. MUST BE USED when [specific triggers]. Use PROACTIVELY for [task category]. Keywords: [trigger words] tools: Read, Write, Edit, Glob, Grep, Bash model: sonnet --- ``` ### Weak vs Strong Descriptions | Weak (won't auto-delegate) | Strong (auto-delegates) | |---------------------------|-------------------------| | "Analyzes screenshots for issues" | "Visual QA specialist. MUST BE USED when analyzing screenshots. Use PROACTIVELY for visual QA." | | "Runs Playwright scripts" | "Playwright specialist. MUST BE USED when running Playwright scripts. Use PROACTIVELY for browser automation." | **Key phrases**: - "MUST BE USED when..." - "Use PROACTIVELY for..." - Include trigger keywords ### Delegation Mechanisms 1. **Explicit**: `Task tool subagent_type: "agent-name"` - always works 2. **Automatic**: Claude matches task to agent description - requires stron
- Agent Description Pattern
- Strong Trigger Pattern
- Weak vs Strong Descriptions
- Delegation Mechanisms
- Tool Access Principle
- Allowlist Pattern
- Model Selection (Quality First)
- Memory Limits
- Root Cause Fix (REQUIRED)
- Parallel Limits (Even With Fix)
- Recovery
- Sub-Agent vs Remote API
- Declarative Over Imperative
- Wrong (Imperative)
export NODE_OPTIONS="--max-old-space-size=16384" grep -n "Next:.*→\|Then.*runs next" .claude/agents/*.md source ~/.bashrc && claude
What does the agent-development skill do?
Design and build custom Claude Code agents with effective descriptions, tool access patterns, and self-documenting prompts. Covers Task tool delegation, model selection, memory limits, and declarative instruction design. Use when: creating custom agents, designing agent descriptions for auto-delegation, troubleshooting agent memory issues, or building agent pipelines.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-development-brendadeeznuts1111-tier-1380-omega --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.