Claude Skills for Beginners: What They Are & 10 to Install First

Here's the short version for beginners: a Claude skill is a folder holding a plain-text instruction file (SKILL.md) that teaches Claude how you want a specific job done. Claude only reads the skill's name and one-line description up front, then loads the full instructions when your request matches. So it's a saved procedure that switches itself on — not another prompt you have to remember to paste. Below: how skills differ from prompts and Projects, how to turn them on, and the ten to set up first.

What a Claude skill actually is

Strip away the branding and a skill is a folder. Inside it is a Markdown file called SKILL.md with a small header — a name and a description — followed by instructions written in ordinary English. A skill can also carry supporting files: a template document, a reference sheet of rules, a script that does something deterministic like renaming files or building a spreadsheet.

The clever part is when Claude reads it. Loading every instruction file you own into every conversation would waste the context window and dull the model. Instead, Claude keeps a short list of your skills' names and descriptions and only pulls the full text in when a request looks like a match. Ask for a client-ready Word document, and the document skill wakes up. Ask about lunch, and it stays asleep. That "load only when relevant" behaviour is the entire design, and it's why the description line matters more than anything else you write.

Skill vs. prompt vs. Project vs. MCP — the beginner's map

• A prompt is one message. Great for one-off work, but you re-type or re-paste it forever. If your prompts are the weak link, start with our guide to prompting Claude effectively — skills won't rescue vague instructions, they'll just repeat them faithfully.
• A skill is a prompt that grew up: saved as a file, available in every chat, and triggered automatically when the request matches its description. Use it for procedures you repeat.
• A Project holds shared context — documents, custom instructions, chat history — for one body of work. Use it for a thing you're working on. Projects and skills stack happily: the Project supplies the facts, the skill supplies the method.
• MCP (Model Context Protocol) connects Claude to outside systems — your files, a database, a SaaS tool. That's access, not know-how. A skill tells Claude what to do; MCP determines what it can reach.

The simplest test: if you find yourself explaining the same standards to Claude a third time — "always use our headline format," "always flag the assumptions," "always output the table before the summary" — that's a skill.

What you need before skills will work

In the Claude apps, skills live in Settings under Capabilities (look for "Skills"), and they've generally required a paid plan plus the code-execution / upgraded file-creation setting switched on, because most skills do their work in a sandboxed environment. Anthropic's own document skills appear there as toggles; custom skills upload as a .zip of your skill folder. In Claude Code, skills are simpler still — a folder in .claude/skills/ in your project, or in your personal ~/.claude/skills/, no upload step at all.

The 10 to install first

Four of these you switch on. Six you write yourself in about ten minutes each — and honestly, the six you write are where the value is, because they encode your standards, which no public library can guess.

1–4. The document set: Word, Excel, PowerPoint, PDF

Anthropic's first-party skills for creating .docx, .xlsx, .pptx and PDF files are the obvious starting point, and they're the ones most beginners don't realise exist. With them enabled, "summarise this and give me a formatted Word doc" produces a real, downloadable file with working headings — not a wall of chat text you paste into Word and reformat by hand. The spreadsheet skill will build multi-sheet workbooks with live formulas; the PDF skill handles extraction and assembly work. Turn all four on before you touch anything custom. If spreadsheets are your daily reality, pair them with our practical guide to using Claude with Excel, which covers when to upload a file versus when to just paste the numbers.

5. Your voice and style guide

The single highest-value skill for most people. It holds your tone rules, banned words, sentence-length preference, formatting conventions, and two or three samples of your actual writing. Once it exists, everything Claude drafts starts closer to sounding like you. This is the same voice-sample method we describe in the writing guide, made permanent instead of pasted per chat.

6. Meeting notes → decisions and actions

Paste raw notes or a transcript; get back a fixed structure every time: decisions made, open questions, action items with owners, and anything that was said but not resolved. The value isn't summarising — Claude does that unprompted. The value is that the shape never varies, so the output drops straight into your notes system.

7. The weekly status update

Feed it a messy list of what you did; get your organisation's specific report format back. Same argument as above: the format is the product. This one usually pays for the ten minutes it takes to write within a fortnight.

8. Inbox triage and reply drafting

A skill that classifies an email — needs a decision, needs information, needs deflection, needs nothing — and drafts a reply in your register, with a hard rule that it never invents commitments, dates, or numbers you didn't supply. That last rule is the difference between a useful drafting skill and an embarrassing one.

9. Resume and application tailoring

Holds your master resume and the honesty rules: rephrase real experience for the target role, never fabricate responsibilities, never claim tools you haven't used. Feed it a job posting, get a tailored version plus the gaps you should be ready to talk about. Our 50 resume and job-search prompts make a good starting body for this file — a skill is where those prompts go to live permanently.

10. The department workhorse — pick your own

Whatever you personally do most: campaign briefs, discovery summaries, sales follow-ups, sprint retros, invoice chasing. Our 40 business prompts by department is essentially a menu of candidates; find the one you'd run weekly and turn that into your tenth skill.

Writing your first skill (the ten-minute version)

You don't need to hand-write YAML. Describe the job to Claude and have it produce the file, then read what it wrote before you install it:

Create a Claude skill for me. Name it brand-voice. It should trigger whenever I ask you to write or edit anything public-facing — posts, emails to clients, landing-page copy. Rules: short sentences, no em dashes, never use "leverage" or "seamless", British spelling, always give me two headline options. Here are three samples of my writing to match: [paste]. Output the complete SKILL.md with correct YAML frontmatter, and tell me exactly where to put the folder.

What comes back is a file with a header block naming the skill and describing when to use it, followed by your rules as plain Markdown. Zip the folder, upload it in the Claude app's skills settings — or drop it into .claude/skills/ if you're in Claude Code — and it's live. Anthropic also publishes open example skills in its public skills repository on GitHub, including a skill whose whole job is helping you author other skills; worth browsing once you've written one by hand and understand the shape.

The description line is the whole ballgame

Beginners pour effort into the instructions and dash off the description. It's backwards. The description is the only part Claude reads before deciding whether to load your skill, so it needs to state plainly what the skill does and when it should fire. "Writing helper" will never trigger reliably. "Use when drafting or editing any public-facing copy — posts, client emails, landing pages — to apply the house voice rules" will. Write the description last, once you know what the skill really does, and phrase it in the words you'd naturally use when asking.

Five mistakes beginners make

• Making one giant "assistant" skill. A skill that covers everything matches nothing in particular. One job per skill; let them compose.
• Vague trigger descriptions. See above. If a skill never seems to activate, the description is almost always the reason — not the instructions.
• Writing rules that contradict. "Be thorough" plus "keep it under 100 words" produces coin-flip behaviour. Rank your rules or drop one.
• Installing skills you haven't read. A skill is instructions Claude will follow, and some carry scripts. Read the SKILL.md the way you'd check what a browser extension asks permission to do.
• Expecting a skill to fix a bad process. If the workflow is unclear in your own head, automating it just makes the confusion reproducible. Write the steps out for a human first.

Honest limits

Skills make Claude consistent; they don't make it correct. A skill can enforce that every report ends with a source list — it can't guarantee those sources exist, so verification is still yours. Skills that call scripts only run where a code sandbox is available, so behaviour differs between the web app, the desktop app, mobile, and Claude Code. And a skill fires on Claude's judgement of relevance, which means it will occasionally load when you didn't want it or sit out when you did; you can always name it explicitly in your message to force the issue.

One more thing worth saying out loud: skills are not a shortcut past learning to prompt. They're a way to stop re-typing prompts you've already got right. Get the instruction right once — then save it.

Common questions

Do I need to know how to code?

No. A SKILL.md file is Markdown and plain English. Scripts are optional and most useful skills don't have one. If the YAML header intimidates you, have Claude generate it and copy what it produces.

How many skills should I have?

Start with the four document toggles and two you wrote. Add one when you catch yourself explaining the same standard for the third time. People who install thirty skills in week one mostly end up with thirty they never use and fuzzy triggering across the lot.

Can I share skills with my team?

Yes — a skill is a folder, so it travels like any other file, and team and enterprise plans have offered admin-level distribution so everyone works from the same procedure. Shared skills are how a team's standards stop living in one person's head.