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.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill agent-development96
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly separates 'what' from 'when', and carves out a distinct niche around Claude Code agent development that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design and build custom Claude Code agents', 'effective descriptions', 'tool access patterns', 'self-documenting prompts', 'Task tool delegation', 'model selection', 'memory limits', and 'declarative instruction design'. | 3 / 3 |
Completeness | Clearly answers both what (design/build agents with descriptions, tool access, prompts, delegation, model selection, memory limits) AND when (explicit 'Use when:' clause with four specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'custom agents', 'agent descriptions', 'auto-delegation', 'agent memory issues', 'agent pipelines', 'Task tool', 'model selection'. These cover common variations of how users would describe agent-building tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Claude Code agent creation with distinct triggers like 'auto-delegation', 'agent pipelines', and 'agent memory issues' that are unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive skill for agent development that excels at actionability and conciseness. The content provides concrete patterns, executable templates, and clear anti-patterns throughout. The main weakness is that the document is quite long and could benefit from splitting advanced topics into separate files for better progressive disclosure.
Suggestions
Consider splitting 'Pipeline Agents', 'Workflow Pattern', and 'Signs a Task Fits This Pattern' into a separate ADVANCED_PATTERNS.md file with a link from the main skill
Add a brief 'Quick Start' section at the top with just the essential agent frontmatter template before diving into detailed patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It uses tables for quick comparison, avoids explaining concepts Claude already knows (like what agents are), and every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples (YAML frontmatter, JSON settings, bash commands), specific patterns with copy-paste ready templates, and concrete comparison tables showing exactly what to do vs. what not to do. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation steps. The workflow pattern section shows numbered steps with clear roles (ME vs AGENTS), and the pipeline agents section includes verification commands to catch common bugs. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a long monolithic document (~300 lines) that could benefit from splitting advanced topics (pipeline agents, parallel workflows) into separate reference files with links from the main skill. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
93%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 15 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.