How to Install Claude Code Skills: A Step-by-Step Guide

--- Installing a Claude Code skill takes about two minutes. A skill is just a SKILL.md file (sometimes bundled with helper scripts and reference docs). "Installing" means putting that file somewhere Claude Code can discover it: as a plugin from a marketplace, as a global skill in ~/.claude/skills/, or scoped to one project in <project>/.claude/skills/. Below are all three methods, step by step, plus the exact skills worth installing first.

What installing a skill actually does

Claude Code discovers skills automatically at startup. Each skill has a SKILL.md file with YAML frontmatter containing a name and a description. Claude reads those descriptions to decide which skill to activate when your request matches — you don't call most skills manually. The rest of the file (the step-by-step workflow, plus any scripts/ or references/ folders) loads on demand, which keeps token usage low until the skill is actually needed.

A quick note for orientation: skills are workflow knowledge (markdown files, zero runtime cost). MCP servers are tools (background processes that connect to APIs and databases). If you want the longer comparison, our guide What Are Agent Skills? covers skills vs. prompts vs. MCP servers in depth. For this tutorial, just remember: installing a skill never involves running a server or giving Claude new permissions.

Method 1: Install through a plugin marketplace (easiest)

Many skill collections are packaged as Claude Code plugin marketplaces. Inside Claude Code, run:

/plugin marketplace add anthropics/skills

This registers the official Anthropic marketplace. Then install individual skills from it:

/plugin install document-skills@anthropic-agent-skills

The pattern is /plugin install <skill-name>@<marketplace-name>. Community marketplaces work the same way — for example, the open-source collection from stefanoleone adds with /plugin marketplace add stefanoleone/claude-code-skills, after which you pick individual skills to install rather than taking the whole repo.

When to use this method: you want a vetted collection and you don't want to touch the filesystem. Downsides: you're dependent on the marketplace maintainer for updates — run /plugin marketplace update <name> periodically to pull the latest versions. You can review what's installed with /plugin list.

Method 2: Manual install — copy the skill into your config

Manual install is the most flexible method and the one to learn, because it works with skills from anywhere — a GitHub repo, a ZIP download, or a file a colleague sends you.

Install globally (available in every project):

mkdir -p ~/.claude/skills/systematic-debugging
# copy the skill's folder here so the path becomes:
# ~/.claude/skills/systematic-debugging/SKILL.md

Install for one project only (shared with your team):

mkdir -p .claude/skills/systematic-debugging
# path becomes: <project-root>/.claude/skills/systematic-debugging/SKILL.md

Project-scoped skills are worth highlighting: because they live inside your repo, you can commit them to git and every teammate gets the same workflow. Global skills are for your personal toolkit.

One edge case: some older single-file skills are written as slash commands. Those go in ~/.claude/commands/<name>.md and are invoked by typing /<name> in the chat. Modern bundled skills (a folder with SKILL.md plus supporting files) belong in ~/.claude/skills/<name>/.

After copying, restart Claude Code (or start a new session) so it picks up the new skill. The skill name must be lowercase with hyphens, and the description in its frontmatter should clearly state when the skill applies — that's how Claude decides to activate it.

Method 3: Install a curated skill from SkillStack

The first two methods assume the skill you're installing is well-made. In practice, skill quality on GitHub varies wildly — unclear trigger descriptions mean skills that never fire, and undocumented scripts mean surprises at runtime.

SkillStack's coding skills take a different approach: each one is built around a real, battle-tested workflow, ships with full documentation, and is tested before release. Every purchase is a ZIP containing the skill folder (ready to drop into ~/.claude/skills/), the original license, and an attribution file.

Installing one is Method 2 with a head start:

1. Pick a skill from the catalog — for example, Systematic Debugging.
2. Download the ZIP after purchase (or grab a free skill instantly).
3. Unzip it, then copy the skill folder into ~/.claude/skills/ (global) or your project's .claude/skills/.
4. Restart Claude Code. Done — no marketplace registration, no install scripts to audit.

Which skills should you install first?

Don't install twenty skills on day one. Start with four that cover the daily coding loop, and add more only when you feel a gap:

• Systematic Debugging — a structured debug workflow: reproduce the bug, form a hypothesis, verify with evidence, then fix. This is the single highest-ROI skill for most developers, because unstructured debugging is where agent sessions burn the most time and tokens.
• Test-Driven Development — the red-green-refactor loop as an enforceable protocol. It turns "write tests" from a suggestion Claude half-follows into a workflow it actually completes.
• Code Review and Quality — a review checklist Claude applies to its own output and your pull requests: correctness, edge cases, readability, and consistency with project conventions.
• Diagnosing Bugs — the companion to systematic debugging, focused on root-cause analysis: tracing symptoms back through layers instead of patching the first suspicious line.

For something outside the coding loop, try Brag (free) — it turns a project into a polished release video workflow. A good reminder that skills aren't only for code.

If you're deciding between the subscription and single purchases: one premium skill covers one workflow; the subscription unlocks the whole catalog including the premium packs like Debug Like a Pro and Ship Quality. Install the four above first, then expand by pain point.

Keeping your skills updated

• Plugin-marketplace skills: run /plugin marketplace update <marketplace-name> now and then. No version pinning on most community marketplaces — every commit can be a new version.
• Manually installed skills: there is no auto-update. Re-download or re-copy when the author ships a fix. Tip: keep a skills/ note in your dotfiles repo listing where each skill came from, so future-you knows what to refresh.
• Project-scoped skills: update them like any other dependency — pull, test, commit. Your team gets the change through normal code review.

FAQ

Do skills run automatically, or do I have to invoke them? Mostly automatic. Claude matches your request against each skill's description and loads the skill when it fits. Slash-command-style skills (in ~/.claude/commands/) are the exception — you invoke those manually with /<name>.

Can I share skills with my team? Yes — that's what project-scoped installs are for. Put the skill folder in <project>/.claude/skills/, commit it, and everyone on the repo gets it. This is also how teams standardize workflows: the same debugging protocol, the same review checklist, every session.

Skills vs. MCP servers — which should I install? Different jobs. Install a skill when the problem is knowledge: how to debug, how to review, how to write a release note. Install an MCP server when the problem is access: reading from a database, calling an API, driving a browser. Most serious setups end up with both.

Are paid skills worth it when GitHub has thousands of free ones? Free skills are abundant; reliable ones are not. What you're paying for in a curated skill is the testing: a trigger description that actually fires, steps that work across projects, and documentation that explains the "why." Try the free skills first — if one saves you a single debugging session, the math on a premium one is obvious.

Conclusion

Installing a Claude Code skill is a two-minute job with three paths: the plugin marketplace for convenience, manual copy for full control (global or per-project), or a curated download when you want the skill to just work. Pick one method, install the four workflow skills above, and you'll feel the difference in your very next session — fewer meandering agent loops, more completed work. When you're ready to expand, the catalog is sorted by workflow, not hype. ---