Best Claude Skills: 17 Picks, Sorted by the Job They Do

November 2, 2026

Pick by the work you give Claude. For code, install Superpowers and use the bundled /code-review. For interfaces, Anthropic's frontend-design; for Word, Excel and PowerPoint files, Anthropic's document skills. Writers get Humanizer, marketers get Corey Haines' Marketing Skills, and anyone starting a project gets grill-me.

A skill is a folder with a SKILL.md file that Claude loads when your request matches its description. The format, and where Claude looks for skills, is explained in how Claude Skills work.

A line like /plugin install name@marketplace runs inside Claude Code and needs that marketplace added first with /plugin marketplace add owner/repo. Anthropic's claude-plugins-official is already there.

Coding

Install a process pack and keep /code-review as the last step before a merge. More starter sets for coding work are on the Claude Code skills page.

/code-review

Bundled with Claude Code, /code-review reads your diff, a branch or a pull request in the background and reports correctness bugs; it can apply the fixes or post them on the PR. There's nothing to install. Style and test coverage stay with your linter and test suite, and at higher effort levels some findings turn out wrong, so read each one before you accept a fix.

Superpowers

Superpowers gives a coding agent a fixed order of work: brainstorm the design, write a plan, build test-first, review, then finish the branch. It suits developers whose agent jumps straight to code on a feature that touches several files. In Claude Code, one line adds it: /plugin install superpowers@claude-plugins-official.

The workflow is mandatory by design, so even a two-line fix gets questions and a plan first. Similar ground is covered by Addy Osmani's agent-skills pack; install one process pack, never both.

Ponytail

Before writing anything, the agent climbs a ladder. Does this need to exist? Is it already in the codebase? Does the standard library or the platform do it?

Add the DietrichGebert/ponytail marketplace, then run /plugin install ponytail@ponytail. Only the GitHub repo and the @dietrichgebert/ponytail npm package are genuine sources, warns the author's README.

Understand Anything

Several agents read the project and save a knowledge graph of its files, functions, classes and dependencies, which opens as a dashboard you can search and question. Reach for it in your first week on an unfamiliar codebase, or to see what a diff touches.

/plugin marketplace add Egonex-AI/Understand-Anything
/plugin install understand-anything

The first /understand reads everything and can use a lot of tokens on a large repo. Scope it to one folder, such as /understand src/frontend.

Design

Start with frontend-design; add Impeccable once there's a page to audit. Landing pages, dashboards, brand themes and motion each get their own pick in the list of Claude skills for design, alongside Taste and Unslop.

frontend-design

Anthropic's frontend-design hands Claude a short design brief for any interface. Claude drafts color, type and layout tokens first, then avoids named AI tells such as rows of identical rounded cards. Use it on a new page or prototype when there's no design system yet.

/plugin install frontend-design@claude-plugins-official adds it. It doesn't know your brand, and its push for distinctive choices can fight strict brand rules.

UI UX Pro Max

Before any code, UI UX Pro Max searches a local database of styles, palettes, font pairings and industry rules, then turns the matches into a design system for your product type. Pick it for a product in a known category, like fintech or booking, where those rules have something to say. Install with /plugin install ui-ux-pro-max@ui-ux-pro-max-skill; matches come from keyword search over fixed tables, so two similar products get similar answers.

Impeccable

Impeccable started from frontend-design and grew into one skill with commands such as critique, audit, polish and typeset, plus rule-based checks that run with no model at all. Run it on an app before launch; its command names also give a team shared words for design feedback.

Run npx impeccable install.

Documents

For Office files and PDFs, start with Anthropic's set.

Anthropic's document skills

Four skills, one install. The set covers Word documents with tracked changes and comments, Excel workbooks with live formulas, PowerPoint decks with native charts, and PDF files to read, fill, merge or split. Claude Code needs /plugin install document-skills@anthropic-agent-skills.

Old .doc files have to be converted to .docx first, per the docx SKILL.md.

doc-coauthoring

For a spec, proposal or decision doc, doc-coauthoring runs three stages: gather context, build each section with you, then test the draft on a fresh Claude that has none of your context. That last step shows where a reader without your background gets lost.

It ships in Anthropic's example set (/plugin install example-skills@anthropic-agent-skills). Expect it to be slow on purpose, with a round of questions before anything is drafted and another for every section.

Frontend Slides

Frontend Slides builds a deck as one HTML file, from a brief or from an existing .pptx, after you choose among three styled preview slides. It suits a talk you present from a laptop or share as a link. Install: /plugin install frontend-slides@frontend-slides. Fonts load from Fontshare or Google Fonts, so the single file still needs a connection to look right.

Writing

Humanizer is the one to run on finished drafts; Prompt Master writes prompts for other tools.

Humanizer

It finds the habits that make a draft read as machine-written, such as staged openers and forced lists of three, and rewrites them while keeping every fact, number and quote. Claude app, Claude Code and Codex all run it; in Claude Code, /plugin install humanizer@humanizer.

Style is all it touches, so a wrong claim comes out wrong in cleaner prose. Passing AI detectors isn't one of its aims, according to the README.

Prompt Master

Say what you want and which tool it's for.

Its tool notes can lag new releases. For a quick prompt with nothing to install, the free prompt generator runs in the browser.

Marketing

Copy and a first audit: Marketing Skills. When the whole site needs checking by parallel agents with Search Console data behind them, Claude SEO. AI search audits and blog workflows are on the longer list of marketing and SEO skills.

Marketing Skills

Corey Haines' set covers SEO audits, landing page copy, conversion, ads, email and launches. A product-marketing skill writes one document about your product and audience, and the other skills read it first. Add it with npx skills add coreyhaines31/marketingskills.

Its seo-audit works from fetched pages. That means no crawl, and no Search Console data unless you paste it in.

Claude SEO

One /seo command runs a full-site audit split across parallel agents, scores the site and sorts the fixes by priority. Connect Google's free APIs and it adds Search Console, PageSpeed and GA4 data.

Several of its agents run on Opus, the README says, so a full audit uses more of your plan than a one-page check. Install with /plugin install claude-seo@agricidaniel-claude-seo.

Productivity

grill-me before a project starts, Claude-Mem if it runs for weeks, skill-creator when you repeat the same routine.

skill-creator

When nothing on this page fits your routine, skill-creator interviews you about the task, drafts the SKILL.md, runs test prompts with and without it, and tunes the description so Claude picks it up. In Claude Code: /plugin install skill-creator@claude-plugins-official.

The Claude app gets a reduced version with no side-by-side comparison. In Claude Code each test runs twice, and that costs usage.

grill-me

Type /grill-me with a loose idea and Claude questions you in rounds until every decision in the plan is made. Run it before a build or a launch, where a skipped question turns into rework.

In a terminal, claude plugins install mattpocock-skills; inside a session, /plugin install mattpocock-skills. Passive answers produce confident nonsense, as the grill-me docs warn.

Claude-Mem

Claude-Mem records each Claude Code session through hooks, compresses it into short observations in a local database, and loads the relevant ones when the next session starts. Use it on long projects where you keep re-explaining yesterday's decisions. Install with npx claude-mem install.

When two skills want the same request

Both can load, and their instructions compete. Superpowers and agent-skills each want to own planning; frontend-design and Taste each want to set the look. After installing a few, paste this into Claude Code to find the clashes:

Read every SKILL.md under ~/.claude/skills/, .claude/skills/ and my
installed plugins. For each skill, give its name and the words in its
description that make it load. Then list every pair whose descriptions
would both match one request, such as "build a landing page" or
"plan this feature". For each pair, say which one to keep for that
request and how to edit the other's description so it stops loading.