12 Best Claude Skills, Sorted By Job

Most "awesome Claude skills" roundups are a wall of links with no context on which ones are worth your five minutes of setup. This list is twelve, chosen by the job they solve — writing, research, ops, design, document work, and LinkedIn content — with exactly what each one does and how to install it, so you can skip the ones that do not apply to you.

If you have not used skills before, start with our what are Claude Skills guide for the basics. This article assumes you know the concept and want the shortlist.

What makes a skill worth installing

A skill is a folder of instructions Claude loads only when the task calls for it, so a good one does something Claude would otherwise do inconsistently by default — not something a single well-written prompt already handles. The twelve below meet that bar: they either ship from Anthropic's own public skills repository or they are a pattern worth building yourself with the skill-creator skill covered in category six.

A quick note on scope: some of these are built for Claude Code, some work in the Claude.ai app, and several work in both. Each entry says where it runs. For the full browsing experience — categories, search, and new additions — see our Claude skills marketplace guide.

How to install any skill in two minutes

Installation differs slightly between Claude.ai and Claude Code, but both are fast once you have done it once. Here is the process for each.

Claude decides on its own when a relevant skill applies to your request — you do not need to invoke it by name, though naming it explicitly ("use the PDF skill to...") helps on the first try while you are getting a feel for what each one does.

Skill, Project, or a good prompt — which do you actually need

Not every repeated task needs a skill, and installing one for something a well-written prompt already handles just adds clutter to your skills list. The three tools solve different problems, and knowing which one you need saves you from over-engineering a task that was never the bottleneck.

A good prompt is the right tool when the task is a one-off, or when the instructions fit comfortably in a paragraph you are willing to retype. A Claude Project is the right tool when the task repeats but the thing that changes is context — client documents, past conversations, a knowledge base you want Claude to draw on every time. A skill is the right tool when the task repeats and what changes is not the context but the output format or process itself — a spreadsheet that always needs the same structure, a document that always needs tracked-changes editing, a LinkedIn post that always needs the same voice rules applied. If you are not sure which applies, start with a prompt; only graduate to a skill once you have typed roughly the same instructions three or four times.

1. Writing: doc-coauthoring and internal-comms

Writing is where most people spend the most Claude time, and these two skills fix the two most common failure modes: documents that degrade the longer you edit them, and internal messages that do not sound like your company.

doc-coauthoring keeps Claude working like a real co-writer across a long document — it tracks what has already been drafted, edits in place instead of regenerating the whole piece, and preserves your structure and voice through multiple revision rounds. Use it for anything longer than a page that you plan to revise more than once: reports, proposals, strategy docs.

internal-comms is built for company-facing writing — announcements, policy updates, all-hands recaps — where tone and format consistency matter more than creative flair. Load your past announcements once and every future one matches the house style automatically. Marketers writing external copy instead should start with our Claude for marketers guide, which covers ad copy, landing pages, and email specifically.

2. Research: xlsx and web-artifacts-builder

Research work has two bottlenecks — turning raw numbers into an analysis, and turning that analysis into something a stakeholder can actually explore instead of a static page of text.

xlsx reads, builds, and edits real spreadsheets: formulas, pivot-style summaries, and formatted output, not just a table pasted into chat. Feed it a messy export and ask for a clean summary workbook with the calculations already built in.

web-artifacts-builder turns findings into an interactive artifact — a filterable dataset, a small dashboard, a calculator — instead of a wall of paragraphs. For research you present more than once, an artifact a stakeholder can click through beats a report they skim once and forget.

3. Ops: webapp-testing and mcp-builder

Ops work is repetitive by nature, which is exactly what skills are for. These two cover the two ends of that spectrum: checking that something still works, and connecting Claude to the tools your operations actually run on.

webapp-testing drives a real browser to click through a web app the way a user would, then reports back what broke. Useful for anyone who owns a site, form, or internal tool and wants a standing check instead of manually clicking through it before every release.

mcp-builder is the skill that helps Claude build the connectors — MCP servers — that link it to your CRM, ticketing system, or internal database. It is more technical than the rest of this list, but it is the difference between Claude answering questions about your ops stack and Claude actually acting inside it.

4. Design: brand-guidelines and theme-factory

Design skills solve the same problem from two directions: making sure Claude's output matches your brand, and making sure a visual artifact has a coherent look before you spend time polishing it by hand.

brand-guidelines loads your colors, fonts, logo rules, and voice once, then applies them automatically to anything Claude produces afterward — decks, one-pagers, social graphics — instead of you correcting the same three things every time.

theme-factory generates a consistent visual theme — palette, spacing, type scale — for a page or artifact in one pass, so a first draft looks intentional instead of like unstyled boilerplate you have to dress up afterward.

5. Documents: pdf and docx

This is the category most people mean when they search "best Claude skills" — the two that make Claude genuinely useful for the document formats an office actually runs on.

pdf extracts text, tables, and form fields from PDFs and can also generate new PDFs from scratch — contracts, reports, filled forms — with real formatting instead of a markdown dump you have to convert yourself.

docx creates and edits Word documents natively: headings, styles, tracked changes, and comments that open correctly in Word, not a plain-text file with the formatting stripped out. Between pdf and docx, most weekly document requests — read this contract, draft this report, fill this form — are covered.

6. LinkedIn and social: pptx and skill-creator

There is no official Anthropic skill named "LinkedIn" — and any marketplace listing claiming one should be treated with suspicion. What actually works for LinkedIn and social content is one official skill used slightly sideways, plus the one skill built for exactly this situation.

pptx builds and edits slide decks — and a LinkedIn carousel is, structurally, a slide deck. Ask for a 6-slide carousel on your topic and pptx will produce properly formatted slides you export as images, instead of you fighting Canva for twenty minutes.

skill-creator is the meta-skill: it helps Claude build a new skill from a description of what you want repeated consistently. For LinkedIn specifically, that means turning your voice, hook style, and formatting rules into a skill Claude applies to every post — instead of you re-explaining your voice in every new chat. Here is the starting prompt:

Use the skill-creator skill to build me a "linkedin-voice" skill.

What it should enforce every time I ask for a LinkedIn post:
- Hook in the first line, no question openers
- First person, my actual opinions, no corporate "we"
- 150-250 words, short paragraphs, no more than 2 hashtags
- No buzzwords: "unlock," "game-changer," "delve," "leverage"
- Always end with a plain statement or a genuine question, not a CTA

Voice reference (paste 2-3 of my actual past posts below):
"""
[paste your best-performing LinkedIn posts here]
"""

Package this as a skill I can reuse across every future LinkedIn
post, and tell me how to install it.

Which one to install first

Do not install all twelve today. Pick the one skill that matches the task eating the most of your week right now, install it, and use it on a real piece of work before adding a second one.

Once the first skill has earned its place in your workflow for a week or two, add the next one from the category that matters most to your job. This is the same install-one-at-a-time approach we recommend across every Claude workflow — it is slower than installing everything at once, but it is the reason people actually keep using skills instead of forgetting they installed them.

The most common mistake with any "best skills" list, including this one, is treating it as a checklist to install in full on day one. A skill you never invoke is not a productivity gain, it is one more menu item to scroll past. Twelve skills used well beats thirty installed and forgotten — pick based on the table above, not on which name sounds most impressive.

Frequently asked questions

Are these skills free?

Yes. Skills are available on Free, Pro, Max, Team, and Enterprise Claude plans — the plan changes your usage limits, not which skills you can install. Claude.ai skills do require code execution to be enabled in settings.

Do I need Claude Code to use any of these?

No. Most of the twelve — doc-coauthoring, internal-comms, xlsx, brand-guidelines, theme-factory, pdf, docx, pptx, skill-creator — run fine in the Claude.ai web app. webapp-testing and mcp-builder are more developer-oriented and are typically installed inside Claude Code instead.

Can I write my own skill instead of using these?

Yes, and skill-creator is built for exactly that. A skill is just a folder with a SKILL.md file describing what Claude should do consistently — if none of these twelve match a repetitive task you have, describe that task to skill-creator and it will package one for you. This is also the better long-term move for anything highly specific to your business, since a skill you build yourself can encode rules — your exact approval process, your specific client list, your house style guide — that a general-purpose skill from a public repository never will.

Where do I find more skills beyond this list?

Our Claude skills marketplace guide covers browsing the full catalog, and Anthropic's own claude.com lists official skills directly. Treat third-party marketplace sites claiming skills Anthropic has not published with the same skepticism you would any unverified plugin.