Claude Skills: Complete Guide to Creating

What Is a Claude Skill?

A Claude Skill is a modular package that extends Claude's capabilities with specialized knowledge, workflows, and executable scripts. Unlike traditional system prompts that load everything into memory, Skills use progressive disclosure: instructions are only loaded when the conversation context triggers them.

Skill Components

📁 my-skill/
├── SKILL.md          → Main instructions + trigger
├── scripts/
│   └── validate.py   → Executable scripts
├── references/
│   ├── guide.md      → Reference documentation
│   └── examples.md   → Concrete examples
└── templates/
    └── output.md     → Output templates

The honest read on Claude Skills one year after the Skills announcement from Anthropic, tracked across r/ClaudeAI, r/LocalLLaMA, and the Anthropic Skills GitHub examples: Skills are the customization feature that finally makes Claude feel like a real programmable tool, and they are also the feature that most heavily rewards good writing. A Skill with a sloppy description and a bloated SKILL.md body triggers on the wrong tasks and ignores the ones it was built for; a Skill with a precise description field and tight procedures fires reliably. The mechanics are documented well enough; the craft is underdiscussed.

Where the community correctly pushes back on "just dump your workflow into a SKILL.md" advice: Skills work on the same attention substrate as every other prompt. Stuffing 3,000 tokens of procedure into one file degrades Claude's ability to follow any single step. The emerging patterns from power users favor small Skills that do one thing well, compose with other Skills, and defer heavy reference material to references/ loaded on demand rather than inlined.

Pragmatic rule from people building Skill libraries that survive: write the description field as if your only job is to help a future Claude decide whether to trigger this Skill. Then write the procedure as if the reader has the attention span of a tired junior engineer. If either of those doesn't read clearly, the Skill will not fire when you need it.

Anatomy of the SKILL.md File

The core of every Skill is the SKILL.md file. It contains a YAML frontmatter followed by Markdown instructions:

---
name: "brand-writer"
version: "1.2.0"
trigger: "When the user asks to write or revise brand content"
description: "Applies brand voice guidelines to any document"
author: "marketing-team"
tags: ["writing", "brand", "marketing"]
---

# Brand Writer

## Procedure

1. Read the document provided by the user
2. Load `references/brand_guide.md`
3. Analyze the current tone of the document
4. Rewrite applying the brand voice
5. Run `scripts/check_tone.py` for validation
6. Present the result with annotated changes

The Trigger System

The trigger determines when Claude activates a Skill. It works through intent matching:

Creating a Skill Step by Step

Step 1: Define the Objective

Before coding, answer these questions:

• →What problem does this Skill solve? (e.g., "standardize code reviews")
• →When should it trigger? (e.g., "when code is shared for review")
• →What resources are needed? (guidelines, validation scripts)
• →What's the expected output format? (Markdown report, corrected file)

Step 2: Structure the Folder

mkdir -p my-skill/{scripts,references,templates}
touch my-skill/SKILL.md

Step 3: Write the SKILL.md

---
name: "code-reviewer"
version: "1.0.0"
trigger: "When the user requests a code review or shares code for analysis"
description: "Performs a structured code review with quality checklist"
tags: ["coding", "review", "quality"]
---

# Code Review

## Review Checklist
1. ✅ Readability and naming
2. ✅ Error handling
3. ✅ Performance
4. ✅ Security
5. ✅ Tests

## Procedure
1. Analyze the submitted code
2. Run `scripts/lint_check.py` if applicable
3. Evaluate each checklist item
4. Generate the report using `templates/review_report.md`
5. Propose priority corrections

Step 4: Add Scripts (Optional)

# scripts/lint_check.py
import subprocess
import sys

def run_lint(filepath):
    """Run basic linting on the file."""
    result = subprocess.run(
        ["python", "-m", "py_compile", filepath],
        capture_output=True, text=True
    )
    if result.returncode == 0:
        return "✅ Valid syntax"
    return f"❌ Errors: {result.stderr}"

if __name__ == "__main__":
    print(run_lint(sys.argv[1]))

Step 5: Test the Skill

Test with different phrasings to verify the trigger:

Sharing Skills

Via the Community Marketplace

The Claude Skills marketplace lets you publish and discover community-created Skills:

1. →Prepare: Add a README.md with description and examples
2. →Publish: Submit via the Skills portal or claude skills publish CLI
3. →Version: Use semantic versioning (1.0.0 → 1.1.0)

Via GitHub

# Recommended structure for a Skills repository
📁 my-skills/
├── code-reviewer/
│   ├── SKILL.md
│   └── scripts/
├── brand-writer/
│   ├── SKILL.md
│   └── references/
└── README.md

Via Claude Enterprise (Teams)

Administrators can deploy Skills organization-wide:

• →Admin Console > Skills > Deploy to Team
• →Permission control by group
• →Centralized versioning

OpenClaw and ClawdBot

OpenClaw, The Open Source Repository

OpenClaw is a community repository that centralizes ready-to-use Skills:

ClawdBot, The Skills Assistant

ClawdBot is an integrated assistant that helps:

• →Discover relevant Skills for your needs
• →Install Skills from OpenClaw in one command
• →Configure triggers and parameters
• →Diagnose activation issues

You: "I need a skill to review my professional emails"
ClawdBot: "I recommend 'professional-email-reviewer' (v2.1.0) — 
           4.8★ on OpenClaw. Install?"

Detailed Use Cases

1. Coding, Review and Refactoring

A code review Skill automatically analyzes quality:

• →Trigger: Code file upload or review request
• →Actions: Lint, complexity analysis, refactoring suggestions
• →Output: Structured report with priorities

2. Writing, Brand Voice

A writing Skill applies brand guidelines:

• →Trigger: Content writing or revision request
• →Actions: Tone analysis, terminology check, rephrasing
• →Output: Revised document with annotations

3. Analysis, Data Profiling

An analysis Skill generates automatic reports:

• →Trigger: CSV/Excel file upload or analysis request
• →Actions: Descriptive statistics, anomaly detection, visualization
• →Output: Report with tables and recommendations

Guidelines

Do's ✅

Don'ts ❌

Summary

Claude Skills represent a major evolution in AI assistant customization. By structuring expertise into modular packages with triggers, instructions, and scripts, they offer a robust, maintainable, and shareable solution for extending Claude's capabilities. Whether you're a developer, writer, or analyst, Skills let you create an assistant truly tailored to your needs.

Next steps:

• →Explore OpenClaw to discover ready-to-use Skills
• →Create your first Skill with the detailed technical guide
• →Compare Skills, Projects, and Plugins in our comparison article