Claude Skills: Custom Commands That Do More

Most people using Claude Code are doing it wrong.

Not wrong as in incorrect — wrong as in slow. They’re typing the same complex prompts over and over, hoping they remember the exact framing that worked last time, and losing 10–15 minutes per workflow because there’s no repeatability built into how they work.

Skills fix that. They’re the feature most Claude Code users don’t know exists — and once you build a few, you won’t work without them.

This guide walks you through exactly what Skills are, how to use the ones that ship with Claude Code, and how to build your own custom workflows triggered by a single slash command.

---

Step 1: What Skills Actually Are

A Skill is a markdown file that defines a reusable workflow. Store it in .claude/skills/ inside your project (or globally), and it becomes a slash command you can invoke from anywhere in Claude Code.

Type /commit and Claude doesn’t just write a commit message — it follows a specific workflow: checks staged changes, reads recent commit history to match your style, drafts a message, and creates the commit. That entire workflow is defined in a Skill file.

Here’s what a Skill file looks like:

---
name: review
description: Check content against house style guide and flag issues
---

You are reviewing content against the following style guide rules:
[your style guide here]

When invoked, ask for the content to review if not already provided.
Then check against each rule and return a structured report:
what passes, what flags, and specific suggested edits for each flag.

That’s it. A YAML header with a name and description, followed by whatever instructions you want Claude to execute. When you type /review in Claude Code, Claude loads those instructions and runs the workflow.

The .claude/skills/ directory is just a folder. Files in it become commands. The command name is the filename without the .md extension — so review.md becomes /review.

Skills can include:

• Multi-step workflow instructions

• Specific output formats Claude should produce

• Domain knowledge and context Claude should carry into the task

• Tool use patterns (read these files, run these commands, check this)

• Conditional logic — “if the content type is X, apply format Y”

• Parameters — /competitive-brief Salesforce passes “Salesforce” as an argument to the skill

They’re not macros. They’re not shortcuts. They’re saved playbooks — the same level of precision you’d give a new hire walking through a task for the first time, available on demand, every time.

---

Step 2: Your First Skill (Built-In)

Claude Code ships with several built-in Skills. The most useful one to understand first is /commit — not because it’s the most impressive, but because it demonstrates exactly what makes Skills valuable.

Before Skills: you’d manually stage your files, think about what changed, write a commit message that may or may not match your project’s conventions, and hope it was good enough.

With /commit: you type one command. Claude checks what’s staged, reads your recent commit history to match the style, drafts a message, and executes. The whole thing takes about 10 seconds instead of 2 minutes.

Try it now. Make a change to any file in a project, stage it with git add, then type /commit in Claude Code.

Watch what happens. Claude doesn’t just string words together — it follows the workflow defined in its Skills file. It checks git status, runs git diff, reads git log to see how you’ve written messages before, then drafts something consistent with your history.

That’s a Skill doing its job.

---

Step 3: Understanding the Mental Model

Here’s the shift that makes Skills click: stop thinking about prompts and start thinking about workflows.

Every repetitive task you do in Claude Code has a shape. A content review has the same steps every time: load the content, check against the rules, flag the issues, suggest edits. A competitive brief has the same structure every time: company overview, product positioning, pricing, strengths, weaknesses, how to beat them in a deal. A weekly summary pulls from the same sources every time: commit history, notes, decisions made.

The problem isn’t that Claude can’t do these things. The problem is that every time you describe the workflow from scratch, you’re introducing variability. You’ll forget a step. You’ll frame it slightly differently. You’ll get a slightly different result.

A Skill locks the workflow down. The instructions are the same every time. The output format is the same every time. The quality floor doesn’t move.

Think of it this way: you don’t explain to a good employee how to do the same task from scratch each time they do it. You document the process once, they follow it reliably. Skills are that documentation — except Claude executes it automatically every time you call it.

Built-in Skills give you the pattern. Custom Skills give you the leverage.

---