agent-development

Malicious tool definition detected

Tool: SKILL.md [1/2] Description: --- name: agent-development description: This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins. version: 0.1.0 --- # Agent Development for Claude Code Plugins ## O

Tool: SKILL.md [2/2] Description: namespaced automatically: - Single plugin: `agent-name` - With subdirectories: `plugin:subdir:agent-name` ## Testing Agents ### Test Triggering Create test scenarios to verify agent triggers correctly: 1.

Malicious tool definition detected

Tool: examples/agent-creation-prompt.md [1/2] Description: # AI-Assisted Agent Generation Template Use this template to generate agents using Claude with the agent creation system prompt. ## Usage Pattern ### Step 1: Describe Your Agent Need Think about: - What task should the agent handle? - When should it be triggered?

Tool: examples/agent-creation-prompt.md [2/2] Description: code review agent.

Malicious tool definition detected

Tool: examples/complete-agent-examples.md [1/2] Description: # Complete Agent Examples Full, production-ready agent examples for common use cases. Use these as templates for your own agents.

Tool: examples/complete-agent-examples.md [2/2] Description: has written code needing documentation, API endpoints requiring docs, or explicitly requests documentation generation. Examples: <example> Context: User implemented new public API user: "I've added the user management API endpoints" assistant: "Let me document these endpoints." <commentary> New public API needs documentation.

Malicious tool definition detected

Tool: references/agent-creation-system-prompt.md [1/2] Description: # Agent Creation System Prompt This is the exact system prompt used by Claude Code's agent generation feature, refined through extensive production use. ## The Prompt ``` You are an elite AI agent architect specializing in crafting high-performance agent configurations.

Tool: references/agent-creation-system-prompt.md [2/2] Description: cases and error scenarios - Ensure test isolation and cleanup ``` **For documentation agents:** ``` Add after "Design Expert Persona": - Use clear, concise language - Include code examples - Follow project documentation standards from CLAUDE.md ``` ## Best Practices from Internal Implementation ### 1.

Malicious tool definition detected

Tool: references/system-prompt-design.md [1/2] Description: # System Prompt Design Patterns Complete guide to writing effective agent system prompts that enable autonomous, high-quality operation. ## Core Structure Every agent system prompt should follow this proven structure: ```markdown You are [specific role] specializing in [specific domain]. **Your Core Responsibilities:** 1.

Tool: references/system-prompt-design.md [2/2] Description: improper 'any' usage 3.

Malicious tool definition detected

Tool: references/triggering-examples.md [1/2] Description: # Agent Triggering Examples: Best Practices Complete guide to writing effective `<example>` blocks in agent descriptions for reliable triggering.

Tool: references/triggering-examples.md [2/2] Description: triggers the agent. </commentary> </example> ``` ## How Many Examples?

Malicious tool definition detected

Tool: scripts/validate-agent.sh Description: #!/bin/bash # Agent File Validator # Validates agent markdown files for correct structure and content set -euo pipefail # Usage if [ $# -eq 0 ]; then echo "Usage: $0 <path/to/agent.md>" echo "" echo "Validates agent file for:" echo " - YAML frontmatter structure" echo " - Required fields (name, description, model, color)" echo " - Field formats and constraints" echo " - System prompt presence and length" echo " - Example blocks in description" ex