Claude Code skills for beginners: what they are, how to install one and how to write your own

A beginner-friendly guide to Claude Code skills: what a SKILL.md is, how Claude decides to use it, how to install a skill and how to write your first one in five minutes.

SkillNest ·

If you keep typing the same instructions into Claude Code — “write tests like this”, “format commits like that” — a skill lets you write them down once.

What is a skill?

A skill is a folder containing a SKILL.md file. The file starts with a short frontmatter block and then plain instructions in Markdown. Claude Code always knows each skill's description, and loads the full instructions only when your request matches it — so you can install many skills without filling up the context.

Install your first skill

  1. Pick one from the topic guides — each skill page shows its install command.
  2. Run the command; it places the skill in ~/.claude/skills/<name>/.
  3. Back in Claude Code, just ask for the task. If the skills folder is brand new, run /reload-skills first.

On Windows? Follow the Windows install guide.

Write your own in five minutes

Create ~/.claude/skills/changelog-entry/SKILL.md:

---
name: changelog-entry
description: Write a CHANGELOG entry for the current changes. Use when the user asks for a changelog or release notes entry.
---

1. Read the staged diff (git diff --cached).
2. Group changes under Added / Changed / Fixed.
3. One line per change, user-facing language, no file names.
4. Show the entry; do not edit CHANGELOG.md unless asked.

That is a complete skill. Only the description really matters for triggering: it tells Claude what the skill does and when to use it. If you leave out name, the folder name is used.

Tips that make skills work better

  • Be specific in the description. “Use when the user asks for X” triggers far more reliably than a vague summary.
  • Say when not to use it. It prevents the skill from hijacking unrelated tasks.
  • Give one short example of the output you want.
  • Share with your team by putting the folder in the project's .claude/skills/ and committing it.
  • Review before installing anyone else's skill — you are giving instructions (and sometimes scripts) to your agent.

Where to find good skills

SkillNest lists hundreds of open-source skills with install commands, organised by category and in topic guides such as Python, testing and SEO. Curious how skills relate to MCP servers? Read skills vs MCP servers.