My Claude skills starter list

What a skill actually is

A skill is a folder with a SKILL.md file inside it. That file holds three things: a short name, a one-line description of when to use it, and the instructions. Claude keeps only the name and description in view, then pulls the full skill into context the second your request matches it. That is why they stack. You can have fifteen installed and Claude only loads the one the task needs, so nothing gets slower and nothing gets confused.

This is the upgrade over keeping a notes file of giant prompts. You stop re-pasting the same instructions every session, and you stop relying on remembering to. Anthropic's Agent Skills overview is the official version if you want the deeper read.

The 3 ways to install one

1. 🌐 Upload a zip, no terminal. In the Claude app or on claude.ai, open Customize, then Skills, then Add, then Upload a skill. The zip needs the SKILL.md at the top level of the folder. This is the route if you have never opened a terminal, and it works on any plan, Free included. Anthropic's creating custom skills article walks the same path.
2. 💻 The skills CLI, in Claude Code. The general route for anything living in a GitHub repo. From your project folder, run npx skills add owner/repo. It detects which agents you have, asks where to install, and drops the folder into .claude/skills/. The CLI is maintained at vercel-labs/skills.
3. 🔌 The plugin marketplace, in Claude Code. Some repos ship as a plugin, which is a bundle of several skills at once. You add the repo as a marketplace, then install the plugin from it. Two lines, no folder wrangling, and updates come down with the marketplace.

1. marketingskills, a marketing department

If you market anything, this is the first one to install. It is a library of 60 plus separate marketing skills covering conversion optimisation, copywriting, SEO and AI search, paid ads, analytics and testing, retention, growth engineering, and pricing and launches. Each one is a focused instruction set rather than a vague "act like a marketer" prompt, which is the whole reason the output stops being generic. It lives at coreyhaines31/marketingskills, MIT licensed, around 44.7k stars.

npx skills add coreyhaines31/marketingskills -a claude-code

# or only the ones you will use
npx skills add coreyhaines31/marketingskills --skill cro copywriting -a claude-code

# read the menu first
npx skills add coreyhaines31/marketingskills --list

Once installed you do not call a skill by name. You describe the job and Claude reaches for the right one.

I am rewriting the landing page for [what you sell, who it is for, and the one action you want them to take]. Use your conversion and copywriting skills on this properly instead of giving me general advice.

Start by telling me what you need from me to do this well and ask for it: the current page, where the traffic comes from, the objection that kills most deals, and the proof I actually have. Wait for my answers. Then diagnose the page section by section and name the specific conversion problem in each one, rather than saying it could be stronger.

Then rewrite it. Give me two versions of the headline and opening paragraph built on genuinely different angles, tell me which angle you would test first and why, and list the three numbers I should watch to know whether it worked.

2. stop-slop, so you sound like you

One SKILL.md file that teaches Claude to catch and strip the patterns that give AI writing away. It works in three layers: banned phrases (throat-clearing openers, business jargon, vague declarations), structural clichés (binary "not X but Y" contrasts, passive voice, false agency), and sentence-level rules (em dash overuse, fragment habits, Wh- starters). Then it scores the result across five dimensions, directness, rhythm, trust, authenticity and density, and rewrites again if the total falls short. It is at hardikpandya/stop-slop, MIT, around 15.8k stars.

npx skills add hardikpandya/stop-slop -a claude-code

No terminal? Download the repo as a zip from GitHub, keep the folder containing SKILL.md, and upload it under Customize, then Skills, then Add, then Upload a skill.

Use the stop-slop skill on the text below, and show your working rather than handing me a clean paragraph.

First list every AI tell you found, quoting the exact phrase and naming which category it falls into. Then give me the rewritten version. Then score it on the five dimensions and tell me which one is weakest and what you would change to lift it.

Rules for the rewrite: keep every fact and every number exactly as they are, keep my meaning intact, and only change the voice. If a sentence was already fine, leave it alone instead of rewriting it to prove you did something.

Here is the text: [paste it]

3. UI UX Pro Max, interfaces that look designed

This one gives Claude an actual design database instead of taste it does not have. The repo ships 79 searchable UI styles (50 active), 192 product colour palettes with reasoning profiles, 74 font pairings, 119 UX guidelines, 25 chart types and a set of motion presets. Under the hood it runs a small search script that queries those datasets across style, colour, typography and layout, then hands Claude a full design system to build against, including the anti-patterns to avoid. It is at nextlevelbuilder/ui-ux-pro-max-skill, MIT, with its own docs site.

/plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill
/plugin install ui-ux-pro-max@ui-ux-pro-max-skill

Use the UI UX Pro Max skill to design the [landing page / dashboard / signup flow] for [what the product is and who uses it]. Search the style and palette databases first and show me what you picked before you write any code.

I want you to come back with: the style direction and why it suits this audience, the exact palette with hex values and what each colour is for, the font pairing with sizes for headings and body, and the three UX guidelines from the library that matter most for this specific screen.

Then flag the anti-patterns you are deliberately avoiding for this kind of interface. Only once I have approved that direction should you build the page, and when you do, keep every colour and size as a variable at the top so I can retheme it without touching the layout.

4. Remotion, video written as code

Remotion is a framework for making videos in React, which turns a video into a file you can version, template and re-render. The official bundle at remotion-dev/skills teaches Claude the framework's real rules across 12 skills: creating projects, markup, captions, rendering, multimedia handling, maps, interactivity and safe upgrades. Remotion documents it on their Agent Skills page.

Honest framing, because the short-form version of this always oversells it: one prompt does not hand you a finished ad. It hands you a working animated composition that you then direct. That is still a big jump from keyframing by hand, and re-rendering it later with new text or a new logo takes seconds.

npx create-video --yes --blank my-video
cd my-video
npm install
npx skills add remotion-dev/skills -a claude-code

Using the Remotion skills in this project, build me a 15 second vertical composition at 1080x1920 that I can re-render later with different words.

The content is: [your hook line, two supporting lines, and a closing line]. Animate the text in line by line on the beat rather than all at once, use one accent colour throughout, and make every string, colour and duration a prop at the top of the file so I can change them without going near the animation code.

Add a short comment above each sequence explaining the timing choice. When you are done, give me the exact command to preview it in the studio and the exact command to render it to an MP4.

5. Context engineering, so Claude lasts longer

The least glamorous one, and the one that quietly changes your day. Every message, file and tool result spends part of a finite context window, and when it fills up quality drops and you burn through usage faster. Context engineering is the practice of curating what goes in there. Anthropic call it the natural progression of prompt engineering in their own write-up. The collection at muratcankoylan/Agent-Skills-for-Context-Engineering packages it into 17 skills Claude activates on its own, including context-compression, context-optimization, context-degradation, filesystem-context and memory-systems.

/plugin marketplace add muratcankoylan/Agent-Skills-for-Context-Engineering
/plugin install context-engineering@context-engineering-marketplace

Before we carry on, run a context audit of this session and be blunt with me about what I am wasting.

Tell me what is taking up the most room in your context right now, which parts of it are no longer useful for the task in front of us, and what you would drop or compress if you could. Point out the habits of mine that made it worse, for example pasting entire files when one section would have done, or switching topics without closing the previous one.

Then give me a plan for the rest of this session: what to keep in context, what to move into a file you read on demand instead, and the point at which I should start a fresh conversation rather than continuing this one.

4 more I keep installed

The two Anthropic ones install together from the official marketplace:

/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skills
/plugin install document-skills@anthropic-agent-skills

Which one to install tonight

Then write the one nobody else has

Installed skills get you competent quickly. The ones you write yourself are what make Claude feel built for your job, because they hold the decisions only you make: your formats, your standards, the same correction you keep typing. Once two of the above are running, spend twenty minutes turning your most repeated task into a skill of your own.

I want to turn a task I repeat every week into a Claude skill so I stop re-explaining it. The task is: [describe it, including what goes in, what comes out, and what makes a good version different from a bad one].

Ask me the three or four questions you need answered before you can write this properly, for example my format, my tone, the inputs I usually have, and what I always check before calling it finished. Wait for my answers before writing anything.

Then write the SKILL.md: a short lowercase-hyphenated name with no "claude" or "anthropic" in it, a description saying exactly what it does AND when it should trigger, and step-by-step instructions in my voice. Finish by telling me how to save it as a zipped folder I can upload under Customize, then Skills, then Add, then Upload a skill.

Everything in one place

coreyhaines31/marketingskills
hardikpandya/stop-slop
nextlevelbuilder/ui-ux-pro-max-skill
remotion-dev/skills and the Remotion Agent Skills docs
muratcankoylan/Agent-Skills-for-Context-Engineering
anthropics/skills, the official ones
ComposioHQ/awesome-claude-skills
The npx skills CLI
Agent Skills, official overview
Creating custom skills, Claude Help Center
Using skills in Claude, Claude Help Center