creating-skills

Create Claude Code skills with CSO-optimized frontmatter and naming conventions.

121|16|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/pr-pm/prpm --skill creating-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-skills
Source: https://github.com/pr-pm/prpm/tree/main/.claude/skills/creating-skills
Command: npx skills add https://github.com/pr-pm/prpm --skill creating-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create Claude Skills that are easily discoverable, scannable, and actionable, preventing the creation of ineffective or overlooked skills. It ensures your skills provide unique, non-obvious context to Claude, making your AI assistant truly smarter.

Core Features & Use Cases

  • Structured Skill Creation: Guides you on mandatory frontmatter, document structure, and content organization for optimal AI understanding.
  • Claude Search Optimization (CSO): Teaches you how to write descriptions and names that Claude will effectively discover and apply, maximizing your skill's utility.
  • Token Efficiency & Examples: Provides best practices for concise content and high-quality, runnable code examples to maximize impact while minimizing token usage.
  • Use Case: When you have a new best practice or troubleshooting guide you want Claude to consistently apply, this skill ensures you document it in a way that Claude will actually use it, saving you from repeating instructions and ensuring consistent application of expertise.

Quick Start

Frontmatter Example


name: my-new-skill description: Use when [trigger] - [what it does] tags: example, meta

My New Skill

Overview

Core principle in 1-2 sentences.

Frequently Asked Questions about creating-skills

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

FAQPage Schema
How do I structure a Claude Skill so it's actually discoverable and used?

Structure your Skill with required frontmatter (name, description, tags), clear gerund-based naming, and scannable sections including Overview, Core Principle, and Examples. Claude Search Optimization requires descriptions that state the trigger and outcome—for example, 'Use when [situation]—[what it does]'—so Claude recognizes when to apply your Skill.

What makes a Skill description effective for Claude's search?

Write descriptions as conditional triggers: 'Use when [problem or context]—[specific action Claude should take].' This teaches Claude when and how to invoke your Skill. Include relevant keywords from your domain, keep language concise, and provide high-quality runnable examples so Claude can apply the Skill consistently without repeated instruction.

How do I document best practices and troubleshooting guides so Claude will actually use them?

Organize your documentation with mandatory sections: frontmatter (name, description, tags), Overview (core principle in 1–2 sentences), and Examples (runnable, high-quality code). Follow gerund-based naming and CSO keyword coverage so Claude discovers your guide at the right moment and applies it reliably across projects.

What's the difference between a well-structured Skill and one Claude won't find?

Well-structured Skills have compliant frontmatter naming, scannable content organization, and descriptions optimized for Claude Search—stating both the trigger and outcome. Ineffective Skills lack clear structure, vague descriptions, or insufficient keyword coverage, so Claude cannot discover them or understand when to apply them, leaving your expertise unused.

Can I reuse Skill templates across multiple projects?

Yes. Creating reusable Skill templates with clear frontmatter, mandatory sections, and actionable examples lets you apply the same best practice or troubleshooting guide consistently across projects. Proper CSO keyword coverage and token-efficient content ensure Claude recognizes and deploys your template reliably in each context.

How do I minimize token usage while keeping my Skill effective?

Write concise descriptions and Overview sections—1–2 sentences for core principles—and provide high-quality, runnable code examples rather than lengthy prose. CSO-optimized frontmatter and mandatory section structure ensure Claude understands your Skill quickly, maximizing impact per token while meeting discoverability requirements.