claudecode-skill-creating

Create Claude Code skills with YAML frontmatter and structured directories.

4|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/tomada1114/tomada-claude-plugins --skill claudecode-skill-creating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claudecode-skill-creating
Source: https://github.com/tomada1114/tomada-claude-plugins/tree/main/claude-dev-kit/skills/claudecode-skill-creating
Command: npx skills add https://github.com/tomada1114/tomada-claude-plugins --skill claudecode-skill-creating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code skill creators often struggle with inconsistent frontmatter, messy directory structures, and unclear activation guidance. This Skill provides a structured blueprint to build scalable, activation-ready skills by enforcing YAML frontmatter, recommended directory layouts, and best practices.

Core Features & Use Cases

  • Enforces mandatory frontmatter: name and description
  • Recommends progressive disclosure with reference.md, templates, and scripts
  • Guides activation integration with CLAUDE.md
  • Useful for new Skill creation, updates, learning patterns, troubleshooting activations

Quick Start

  1. Create a skill directory and add SKILL.md with proper frontmatter
  2. Follow templates in templates/ to structure content
  3. Add reference.md, examples.md, scripts/ as needed
  4. Enable Skill tool permissions and CLAUDE.md integration

Frequently Asked Questions about claudecode-skill-creating

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

FAQPage Schema
How do I structure a Claude Code skill with proper YAML frontmatter?

Claude Code skills require YAML frontmatter with mandatory name and description fields at the top of SKILL.md. This metadata enforces consistent skill registration, enables discovery, and ensures activation readiness. Follow the frontmatter template provided in the skill creation guide to validate structure before deployment.

What's the best directory layout for organizing a Claude Code skill?

Organize skills with a scalable structure: SKILL.md for core content, templates/ for reusable patterns, reference.md for detailed specs, examples/ for use cases, and scripts/ for automation. Progressive disclosure keeps SKILL.md concise while supporting optional extensions, reducing activation friction and improving maintainability.

How do I integrate CLAUDE.md activation rules into my skill?

CLAUDE.md defines activation conditions and tool permissions for your skill. Add activation rules that match your skill's core task, reference the frontmatter metadata, and specify required permissions. This integration ensures your skill activates correctly within Claude Code and surfaces in relevant contexts.

Can I use templates and best practices to speed up skill creation?

Yes. This skill provides template-based onboarding in templates/ that enforce best practices for frontmatter, directory structure, and documentation patterns. Using templates reduces setup time, ensures consistency across skills, and helps troubleshoot activation issues by following proven patterns.

Why does my Claude Code skill not activate, and how do I debug it?

Activation issues typically stem from malformed YAML frontmatter, missing name or description fields, or incomplete CLAUDE.md integration. Validate frontmatter syntax, confirm all mandatory fields are present, verify CLAUDE.md references are correct, and check tool permissions align with your skill's declared capabilities.

What's the difference between reference.md, examples.md, and SKILL.md in a skill?

SKILL.md provides the concise main guide with frontmatter; reference.md contains detailed technical specs and API documentation; examples.md shows real-world use cases. This layered approach supports progressive disclosure—users find quick answers in SKILL.md and drill into depth only when needed.