šØ Skill Builder Agents
Professional Claude Code Skill development through specialized agent collaboration.
From corenpx claudepluginhub talent-factory/claude-plugins --plugin corešØ Skill Builder Agents
Professional Claude Code Skill development through specialized agent collaboration.
Overview
The Skill Builder agent system provides four specialized agents that work together to create production-ready Claude Code Skills through an elicitation-driven process. Each agent is an expert in its domain, ensuring comprehensive quality at every stage.
The Four Agents
1. šÆ skill-elicitation-agent
File: skill-elicitation-agent.md
Purpose: Requirements gathering and specification creation
Expertise:
- Targeted question-asking to understand user needs
- Converting requirements into detailed specifications
- Planning skill structure and components
- Validating completeness before generation
Tools: Read, Write, Grep, Glob, WebFetch
Triggers: Building new skills, gathering requirements
Output: Comprehensive skill specification document in structured YAML format
Key Process:
- Asks 3-5 targeted questions about:
- Purpose and scope
- Complexity and structure
- Tool permissions
- Context and references
- Success criteria
- Creates detailed specification
- Validates completeness
- Gets user approval
2. šļø skill-generator-agent
File: skill-generator-agent.md
Purpose: Skill file and code creation
Expertise:
- SKILL.md authoring with proper frontmatter
- Directory structure organization
- Script and utility generation
- Progressive disclosure implementation
- Dependency documentation
Tools: Read, Write, Edit, Bash, Grep, Glob, WebFetch
Triggers: Creating skills from specifications
Output: Complete skill directory with all files, scripts, and documentation
Key Process:
- Analyzes specification
- Creates directory structure
- Generates SKILL.md with proper frontmatter
- Creates supporting files (reference.md, examples.md)
- Writes scripts with error handling
- Documents dependencies
- Performs quality checks
3. ā skill-validator-agent
File: skill-validator-agent.md
Purpose: Comprehensive quality assurance and testing
Expertise:
- YAML frontmatter validation
- Structure and organization checks
- Code syntax and execution testing
- Description quality analysis
- Security checks
- Integration testing
Tools: Read, Bash, Grep, Glob, WebFetch
Triggers: Validating new or modified skills
Output: Detailed validation report with scores and actionable fixes
Key Process:
- Validates YAML frontmatter
- Analyzes description for discoverability
- Checks file structure and references
- Tests script syntax and execution
- Verifies progressive disclosure
- Performs security checks
- Tests skill loading and triggering
- Generates comprehensive report
4. š skill-documenter-agent
File: skill-documenter-agent.md
Purpose: Comprehensive documentation creation
Expertise:
- Technical writing
- Example creation (beginner to advanced)
- API documentation
- Troubleshooting guides
- Best practices documentation
Tools: Read, Write, Edit, Grep, Glob, WebFetch
Triggers: Documenting skills
Output: Enhanced documentation including examples, reference docs, and guides
Key Process:
- Enhances SKILL.md content
- Creates reference.md for technical details
- Generates examples.md with comprehensive examples
- Adds troubleshooting section
- Creates README.md if distributing
- Validates documentation quality
Agent Workflow
Sequential Collaboration
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā User Request ā
ā "Create a skill for [task]" ā
āāāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā 1. skill-elicitation-agent ā
ā ⢠Asks 3-5 targeted questions ā
ā ⢠Creates detailed specification ā
ā ⢠Validates completeness ā
ā ⢠Gets user approval ā
āāāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Specification Document
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā 2. skill-generator-agent ā
ā ⢠Creates directory structure ā
ā ⢠Generates SKILL.md + supporting files ā
ā ⢠Writes scripts with error handling ā
ā ⢠Documents dependencies ā
āāāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Skill Files
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā 3. skill-validator-agent ā
ā ⢠Validates structure and syntax ā
ā ⢠Tests code execution ā
ā ⢠Checks discoverability ā
ā ⢠Generates validation report ā
āāāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Validation Report
ā
āāāā ā
PASSED āāāāā
ā ā
āāāā ā ISSUES āāāāā¤
ā ā
ā¼ ā
Fix Issues ā
ā ā
ā¼ ā
Re-validate ā
ā ā
āāāāāāāāāāāāāāā
ā
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā 4. skill-documenter-agent ā
ā ⢠Enhances SKILL.md ā
ā ⢠Creates comprehensive examples ā
ā ⢠Generates reference docs ā
ā ⢠Adds troubleshooting guides ā
āāāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā Production-Ready Skill ā
ā ā
Complete structure ā
ā ā
Validated code ā
ā ā
Comprehensive docs ā
ā ā
Ready for use ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
Agent Communication
Data Flow Between Agents
Elicitation ā Generator:
- Specification document (YAML structured)
- User preferences (location, restrictions)
- Reference materials
Generator ā Validator:
- Skill directory path
- List of created files
- Dependency information
Validator ā Generator (if issues):
- Validation report
- List of errors and warnings
- Specific fixes needed
Generator ā Documenter:
- Skill path
- Original specification
- Current documentation state
Documenter ā User:
- Final skill location
- Usage instructions
- Test scenarios
Usage Patterns
Pattern 1: Simple Instruction Skill
User Request: "Create a skill for commit messages"
Agent Flow:
- Elicitation: Asks about commit style, conventions, examples
- Generation: Creates single SKILL.md with instructions
- Validation: Checks structure, description quality
- Documentation: Adds examples, best practices
Result: Simple, focused skill with clear instructions
Pattern 2: Multi-File Complex Skill
User Request: "Create a skill for PDF processing"
Agent Flow:
- Elicitation: Asks about operations, dependencies, safety
- Generation: Creates SKILL.md + reference.md + scripts/
- Validation: Tests scripts, validates structure
- Documentation: Creates comprehensive examples, API docs
Result: Professional multi-file skill with code execution
Pattern 3: Tool-Restricted Safety Skill
User Request: "Create a security analysis skill"
Agent Flow:
- Elicitation: Determines read-only requirement
- Generation: Creates SKILL.md with allowed-tools restriction
- Validation: Verifies tool restrictions, tests safety
- Documentation: Documents analysis patterns, examples
Result: Safe, read-only skill with proper restrictions
Integration with Commands
Primary Command: /core:build-skill
Located at: .claude/commands/skills/build-skill.md
This command orchestrates all four agents in sequence to build complete skills.
Command Flow:
- Launches skill-elicitation-agent with user request
- Gets user approval on specification
- Launches skill-generator-agent with specification
- Launches skill-validator-agent on generated skill
- Fixes issues if needed (loops back to generator)
- Launches skill-documenter-agent for enhancement
- Delivers final skill with usage guide
Supporting Resources
Templates (.claude/commands/skills/references/templates/):
simple-skill-template.md- For instruction-only skillsmulti-file-skill-template.md- For complex skillstool-restricted-skill-template.md- For safety-critical skills
Scripts (.claude/commands/skills/references/scripts/):
validate-skill.sh- Standalone validation scripttest-skill-trigger.sh- Trigger testing and analysis
Agent Design Principles
1. Single Responsibility
Each agent has ONE clear purpose:
- Elicitation: Understand requirements
- Generation: Create files
- Validation: Ensure quality
- Documentation: Enhance usability
2. Isolated Expertise
Agents work in separate contexts:
- No cross-contamination
- Fresh perspective at each stage
- Specialized knowledge domains
3. Progressive Refinement
Each agent improves on the previous:
- Elicitation ā Clear specification
- Generation ā Working skill
- Validation ā Quality assurance
- Documentation ā User-friendly
4. Human-in-the-Loop
User involvement at key stages:
- Approve specification after elicitation
- Review validation results
- Confirm final deliverable
Quality Standards
Skills created through this system meet:
ā Structure Standards
- Valid YAML frontmatter
- Clear, discoverable descriptions
- Proper file organization
- Progressive disclosure
ā Code Standards
- Syntax validation
- Error handling
- Security checks
- Executable permissions
ā Documentation Standards
- Clear instructions
- Comprehensive examples
- Troubleshooting guides
- Best practices
ā Validation Standards
- Score 8/10 or higher
- No critical issues
- Production-ready quality
Customization and Extension
Adding New Agent Capabilities
To extend an agent:
- Update Agent File: Add new capabilities to the agent's expertise
- Document Tools: Ensure necessary tools are listed
- Update Process: Document new steps in the process
- Test Integration: Verify agent collaboration still works
Creating Custom Templates
To add skill templates:
- Create template file in
.claude/commands/skills/templates/ - Use
{{PLACEHOLDER}}syntax for variables - Document template usage in comments
- Update generator agent to reference new template
Adding Validation Checks
To add new validations:
- Update
validate-skill.shscript - Add check in skill-validator-agent documentation
- Document what it checks and why
- Update validation report format if needed
Best Practices
For Using the Agents
- Always start with elicitation - Don't skip requirements
- Provide context - Share examples, docs, references
- Review specifications - Approve before generation
- Fix validation issues - Don't proceed with errors
- Test thoroughly - Use real-world scenarios
For Maintaining Agents
- Keep agents focused - One responsibility each
- Update documentation - When adding capabilities
- Test changes - Verify agent collaboration
- Maintain isolation - No cross-dependencies
- Version carefully - Document breaking changes
Troubleshooting
Agent Not Triggering
Issue: Agent doesn't activate when expected
Solutions:
- Use explicit invocation: "Launch skill-elicitation-agent"
- Check agent file exists in
.claude/agents/skill-builder/ - Verify YAML frontmatter is valid
- Restart Claude Code if needed
Agent Confusion
Issue: Wrong agent activates
Solutions:
- Be explicit: "Use the skill-elicitation-agent"
- Follow recommended sequence
- Provide clear context about which phase you're in
Validation Failures
Issue: skill-validator-agent reports errors
Solutions:
- Review validation report carefully
- Fix critical errors first
- Use skill-generator-agent to make fixes
- Re-validate after changes
Future Enhancements
Planned Improvements
- Skill version management
- Automated testing framework
- Marketplace integration
- Usage analytics
- Dependency tracking
- Skill templates marketplace
- Inter-skill communication
- Skill composition patterns
Resources
Documentation
- Claude Code Skills: https://docs.anthropic.com/claude-code/skills
- Agent Skills Overview: https://docs.anthropic.com/agents-and-tools/agent-skills/overview
- Best Practices: https://docs.anthropic.com/agents-and-tools/agent-skills/best-practices
Examples
- Anthropic Skills Repo: https://github.com/anthropics/skills
- Sample Skills:
.claude/skills/(if any exist)
Commands
- Build Skill:
/skills:build-skill - Validate: Run
scripts/validate-skill.sh - Test Triggers: Run
scripts/test-skill-trigger.sh
Transform workflows into production-ready skills with professional agent collaboration.