skill-builder

Create Claude Code Skills with SKILL.md drafting and validation.

37|4|Updated Dec 6, 2025
One-click install
npx skills add https://github.com/mike-coulbourn/claude-vibes --skill skill-builder-mike-coulbourn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-builder
Source: https://github.com/mike-coulbourn/claude-vibes/tree/main/plugins/vibes/skills/skill-builder
Command: npx skills add https://github.com/mike-coulbourn/claude-vibes --skill skill-builder-mike-coulbourn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and frustration of creating effective Claude Skills that activate reliably and follow best practices. It provides a structured approach to build production-quality skills, ensuring they are discoverable and robust.

Core Features & Use Cases

  • Guided Skill Creation: Follow a step-by-step workflow from requirements gathering to testing for robust skill development.
  • Description Optimization: Craft discoverable descriptions using a proven formula, ensuring your skills activate precisely when needed.
  • Structure & Best Practices: Learn proper naming conventions, multi-file organization, and tool restriction for secure and maintainable skills.
  • Use Case: You want to create a new Claude Skill to automate your daily report generation. This skill guides you through defining its purpose, crafting a description that ensures it activates when you ask for "daily report," and structuring it with any necessary scripts or templates.

Quick Start

Ask the skill-builder to help you create a new skill for generating daily reports.

Frequently Asked Questions about skill-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Skill that activates reliably when users need it?

Create a Claude Skill by following a structured workflow: gather requirements, craft a discoverable description using proven formulas, validate naming conventions (lowercase, hyphens, max 64 chars), plan your file structure, implement with proper YAML frontmatter, and test activation triggers. This ensures your skill activates precisely when users search for it.

What's the best way to write skill descriptions for discovery and activation?

Write skill descriptions under 1024 characters following a clear pattern: state what the skill does, when to use it, and trigger terms users would search for. This formula ensures Claude activates your skill at the right moment and makes it discoverable through natural language queries.

What are the naming and structure requirements for production Claude Skills?

Claude Skills require lowercase names with hyphens only (max 64 characters), proper YAML frontmatter with opening/closing delimiters and no trailing spaces, optional tool restrictions for security, and organized multi-file structures. These constraints ensure skills activate reliably and follow best practices.

Can I use best practices to debug why my skill isn't activating?

Yes. Validate your YAML frontmatter syntax, check naming constraints (lowercase, hyphens, length), review your description for clear trigger terms and when-to-use patterns, and test against Claude's activation logic. Following the phase-driven validation workflow identifies and resolves activation failures.

How do I plan a multi-file skill structure that stays maintainable?

Plan your skill structure by defining components upfront, organizing related logic into separate files, applying tool restrictions where needed for security, and documenting each file's role. This approach keeps complex skills maintainable and prevents common design pitfalls.