The Complete Claude
Skills Guide

Section 1

What's a Skill, Really?

Skills are folders. That's it.

Inside each folder is a text file with instructions. When you trigger it, Claude reads those instructions and follows them. You're not writing code. You're writing a recipe, and Claude is the chef.

Why does this matter? Because right now, every time you do a repeated task with Claude, you're re-explaining the same thing from scratch. Your voice. Your format. Your workflow. Skills let you teach Claude once and reuse it forever.

Section 2

Install the Skill Creator

You don't have to learn YAML. You don't have to memorize the folder structure. Anthropic ships a skill called Skill Creator that interviews you about the task and writes the file for you.

Same skill, three entry points. Install it in whichever Claude you already use.

Section 3

Your First Skill in 15 Minutes

Once Skill Creator is installed, building a skill is a conversation. No coding, no YAML, no folder wrangling. You answer a few questions. It writes the file. You save it. Done.

That's the full loop. 15 minutes for most skills, start to saved-and-working. You now own a piece of automation that runs the same way every time, forever.

Section 4

Under the Hood

You don't have to understand this to use Skill Creator. But if you want to edit a skill directly, or write one by hand, here's how they actually work.

The folder structure

Every skill in Claude Code lives in .claude/skills/. Each skill gets its own subfolder with at minimum one .md file inside.

.claude/
  skills/
    weekly-report/
      SKILL.md              ← the main skill file
    social-post/
      SKILL.md
      brand-voice.md        ← linked reference file
    client-summary/
      SKILL.md
      template.md

The 3-level loading system

Claude doesn't read everything at once. It loads skill context in three layers, and understanding this is what separates good skills from great ones.

Section 5

Writing Descriptions That Trigger

The frontmatter description is the single most important line in your skill file. Write it wrong and the skill either never triggers or triggers at the wrong time. Skill Creator writes a decent first version. These are the rules for making it great.

---
name: weekly-report
description: "Generate weekly client status report from project notes using the standard 3-section format"
---

Instructions that work vs. instructions that don't

The body of your skill is where the task gets done. Claude follows specific, action-oriented language much better than vague guidance. Rewrite anything abstract into something concrete.

Section 6

The 5 Use Cases That Actually Matter

Skills aren't useful for everything. They're useful for 5 specific kinds of tasks. Ranked by raw payoff, most-to-least. Every example below is a real skill I built and run daily.

Section 7

Testing Your Skill

Built your first one? Run these three checks before you depend on it for real work.

Section 8

Common Mistakes

Section 9

Start Here

Don't try to build your dream skill first. Pick the most boring, most repeatable task you've done 3+ times this week. Something you'd explain to a new hire in under 5 minutes.

Install the Skill Creator using the section above. Open a new conversation. Say "I want to build a skill for [that boring task]." Let it interview you. Save the file.

Test it once. Iterate. Add the second one tomorrow. That's the whole system. Most people never build their first. You'll be further than 90% of Claude users by Friday.

Quick Reference

Skill Builder Cheat Sheet