Chapter 1

Claude Skills

A Skill is a reusable set of instructions for a specific kind of work. It gives Claude a method to follow. It is not an app, a project, or an autonomous agent.

When to create one

Create a Skill when you repeatedly give Claude the same process, examples, or quality checks.

Good uses include:

  • Writing in a consistent voice
  • Reviewing content against a checklist
  • Researching with a repeatable method
  • Creating the same type of document
  • Using tools in a required order

For a one-time request, write a normal prompt.

What a Skill contains

Every Skill needs a SKILL.md file. It usually contains:

  1. When to use the Skill
  2. What result it should produce
  3. The steps to follow
  4. The definition of done

Examples, templates, references, and scripts are optional. Add them only when the main instructions would otherwise become difficult to use.

skill-name/
├── SKILL.md
├── references/
├── examples/
└── scripts/

Where Skills live

  • Personal Claude Code Skill: ~/.claude/skills/<skill-name>/SKILL.md
  • Shared project Skill: .claude/skills/<skill-name>/SKILL.md
  • Plugin Skill: <plugin>/skills/<skill-name>/SKILL.md
  • Cowork or cloud Skill: enable it through your Claude account

Claude can load a relevant Skill automatically, or you can invoke it directly with /<skill-name>. Local Claude Code Skills do not automatically appear in Cowork or cloud sessions.

Skill versus CLAUDE.md

Use CLAUDE.md for short facts and rules Claude should know in every session. Use a Skill for a procedure or reference Claude needs only for certain work.

Example:

  • CLAUDE.md: “Use our current offer names.”
  • Skill: the complete workflow for researching and writing a case study

Example

A LinkedIn writing Skill can hold the voice rules, hook patterns, post structure, CTA rules, and final review checklist. Your campaign files supply the topic and evidence. The Skill supplies the writing method.

Common mistakes

  • Using a vague description that triggers at the wrong time
  • Combining unrelated workflows into one Skill
  • Copying all company knowledge into every Skill
  • Adding scripts where judgment is required
  • Installing a third-party Skill without reviewing its files and permissions

Keep the main file concise. Test it on real requests and update it when the same failure repeats.

Continue

Next: Claude Cowork.

Official references

Want this set up for your business?

We turn these workflows into working marketing and sales systems.

Book a call