Use existing skills

You already have /wrapup and /startup installed (Module 04). That's 2 skills. The Anthropic ecosystem has dozens more, and as a member you'll get access to a curated library built for marketers. This lesson is about using what's already there.

Types of skills in the ecosystem

Anthropic's official skills

Built-in skills that ship with Claude Code. Run / in any session to see what's loaded. Includes basic utility skills.

Anthropic skills repo

Public repo at github.com/anthropics/skills. Skills Anthropic has published - browse, read, install what's useful.

Community + shared skills

Skills published by Claude Code power users. The Caveman skill (Module 13), superpowers skills, and many others live here.

Your team's shared skills

For teams, there's usually a shared repo of skills specific to how your team works. Brand guides, client-specific workflows, team processes - all as skills.

How to see what's installed

Inside a Claude Code session, type

terminal
/

Claude shows you the full list of available skills with one-line descriptions. Each trigger + description is what you see.

For more detail

List all my installed skills with their full descriptions. Group by category if possible.

How to install a skill

Most skills come from GitHub repos. To install

Install the [skill-name] skill from [repo-url]. After install, confirm the trigger works.

Claude

1. Clones or downloads the skill files
2. Copies them into ~/.claude/skills/skill-name/
3. Restarts the skill loader so it picks up the new skill
4. Tests by running the trigger

For skills shared as standalone files

Here's a SKILL.md file I downloaded. Install it to my skills folder with trigger [name] and confirm it loads.

Skills worth installing early

A few skills are genuinely worth having from day one. Not everything advertised online is safe or useful - these are the ones worth the setup time:

• /wrapup + /startup - already installed in Module 04. Session save + load. Non-negotiable.
• /skill-creator - attached to Lesson 3. The meta-skill that helps you build new skills properly. Install when you get there.
• The superpowers pack - community-maintained bundle at github.com/obra/superpowers. Includes /brainstorming, /writing-plans, /executing-plans, /verification-befor e-completion, and more. Module 11 uses several of these for complex-project workflows - install now so they're ready when you need them.
• /caveman - community skill (github.com/JuliusBrussee/caveman). Compresses Claude's output for token savings. Covered in Module 13.
• A brand or voice skill for your main project - you'll build this yourself in Lesson 3. Makes all your copy consistent.

That's enough to start. Most of the value from skills comes from the ones you build yourself, not ones you install.

Installing the superpowers pack

Tell Claude

Install the superpowers pack from github.com/obra/superpowers. Read the repo's README for install instructions. Confirm the core skills (/brainstorming, /writing-plans, /executing-plans) are available as slash commands after install.

Restart Claude Code after install so the new skills load. Type / to see them.

What about other "skill packs"?

Many others exist on GitHub. Evaluate carefully

• Read every SKILL.md before installing (prompt-injection risk - covered in Module 03)
• Check when it was last updated - stale packs often use outdated patterns
• Install only the skills from the pack you'll actually use (skills budget - Lesson 4)

How to update a skill

Skills evolve. When the source updates

Update the [skill-name] skill from its source repo. Back up my local version first in case I've customised it.

Claude pulls the latest, notes any differences, gives you the option to merge changes or discard your local edits.

How to disable a skill

Without deleting it

Disable the [skill-name] skill so it stops loading in new sessions. I might want it back later.

Claude moves it to a disabled folder. To re-enable

Re-enable the [skill-name] skill.

How to customise a skill

Every skill is just a markdown file. You can edit it directly:

Edit the [skill-name] SKILL.md to also do [specific thing]. Show me the before and after.

Claude opens the file, makes the edit, shows you the diff. You approve or reject. For local customisations: create a copy instead of editing the original. Named /my-weekly-report vs /weekly-report. Then you can update the original without losing your customisations.

Power-user tips

• Type / alone to see what's available - instant menu of all skills
• Read SKILL.md files before installing - know what you're running (Module 03 prompt injection concern)
• Group your skills by folder - ~/.claude/skills/marketing/, ~/.claude/skills/thinking/, etc. Easier to browse.
• Symlink team skills - if your team has a shared skills repo, clone it once and symlink folders into your skills directory. Updates propagate automatically.

Action items

☐ Type / in a session to see what skills you have

☐ Bookmark Lesson 3 - download /skill-creator when you get there

☐ Practice running a skill: try /wrapup at end of your next session

☐ Read one SKILL.md file to understand what's inside

Next lesson: Building your first custom skill.

Exercises

1. Review the concepts covered in this lesson: Use existing skills.
2. Write down your key takeaway from this lesson.
3. Practice running any commands or prompts mentioned above inside your terminal.