Tutorial··6 min
How to install Claude Code skills in 60 seconds
A step-by-step guide to finding, installing, and managing Claude Code skills using the SKILL.md standard — with working examples.

Claude Code skills let you extend your AI coding agent with specialised knowledge — a frontend style guide, a SQL reviewer, a deployment checklist — without rewriting your system prompt every session. Here's how to find one and get it running in under a minute.
Step 1 — Find a skill
----------------------
Browse the ClaudeSkill marketplace at claudeskil.com/explore. Use the search bar to find skills by keyword ("react", "sql", "seo") or filter by category. Each skill page shows:
- A description of what it does and when to use it
- The install command (one line)
- Stars, installs, and last updated date
- The raw SKILL.md file so you can review it before installing
Step 2 — Install it
--------------------
From the skill detail page, copy the install command. It looks like:
claude skills add frontend-shadcn-builder
Run it in your terminal inside any project directory. Claude Code fetches the SKILL.md from GitHub, validates it, and saves it locally. The whole operation takes under 5 seconds.
Step 3 — Use it
----------------
Start a new Claude Code conversation in the same project. The skill is now active. Try one of its triggers — the exact phrases are listed in the SKILL.md and shown on the skill detail page.
For the `frontend-shadcn-builder` skill, you might type:
Build a pricing section with three tiers using shadcn Card components
The skill injects its rules, style preferences, and component conventions into the context automatically. You don't need to say anything extra.
Step 4 — Manage your skills
-----------------------------
To see all installed skills:
claude skills list
To remove one:
claude skills remove frontend-shadcn-builder
To update to the latest version:
claude skills update frontend-shadcn-builder
Installing multiple skills
---------------------------
Skills are composable. You can install a frontend skill, a testing skill, and a documentation skill at the same time. Claude Code applies whichever one is most relevant to the current task based on the triggers.
If two skills conflict (both want to handle "write a test"), the last-installed one takes priority. You can also pin a specific version:
claude skills add qa-playwright-pro@1.2.0
Tips for picking good skills
------------------------------
- Check the "last updated" date — skills that haven't been touched in 6 months may be stale
- Look at the SKILL.md source before installing (it's one click away on the skill page)
- Prefer skills with evals or example outputs listed in the README
- Start with one skill per category and add more only when you feel the gap
The full list of available skills is at claudeskil.com/explore.