Full Transcript

·YouTLDR

I Scraped 85,000 Claude Skills. These Are The Most Popular

14:48EnglishTranscribed Jul 19, 2026
0:00

The number one most downloaded Claude

0:01

skill on the planet has been installed

0:04

829,000

0:05

times. That same skill was just sitting

0:07

at 250,000 installs a couple months ago.

0:11

So now while you've been using Claude

0:12

like a fancy chatbot, an entire army of

0:15

vibe coders quietly turned it into an

0:17

automated work system. The problem is

0:19

there are now over 85,000 community

0:21

built Claude skills floating around the

0:23

internet, but 99% of them are actually

0:26

hot garbage. So I spent days digging

0:28

through the entire official Anthropic

0:30

directory to find the latest install

0:33

data and after reviewing over 10 million

0:35

data points, what I found actually

0:37

shocked me. 12 skills were consistently

0:40

showing up more than the rest. This left

0:42

me with two options. We can either adopt

0:45

these or watch everyone around us work

0:47

twice as fast for the rest of the year.

0:49

I know what I'm choosing. So let me

0:50

break down all 12 skills for you

0:52

starting from number 12 and working our

0:54

way up to the most installed skill on

0:56

earth. Then I'll end on the one rule

0:59

that stops you from nuking your own

1:00

setup when using too many of these. And

1:03

no, you do not need to know how to code

1:05

for any of this. We're doing everything

1:07

in natural language. By the end, you'll

1:09

know exactly which skills to install so

1:11

you don't get left behind. Oh, and if we

1:13

haven't met yet, I'm Doobie, former

1:15

marketer turned vibe coder. I made over

1:17

$40,000 in less than 50 days using these

1:19

exact AI tools. So trust me, the skills

1:22

I'm about to share I've been using for

1:24

weeks now. Starting with number 12,

1:27

security guidance. 175,000 installs. Did

1:31

you know that according to a recent

1:32

security audit, roughly 11,000 out of

1:35

the 85,000 skills available are believed

1:38

to contain security issues? That means

1:40

you have a one in eight chance of

1:42

downloading a potentially malicious

1:44

skill. That's why it's more important

1:46

than ever to keep your security tight.

1:48

That's exactly what the security

1:50

guidance skill was built for. It only

1:52

launched a few weeks ago and has since

1:54

skyrocketed straight into the top 12

1:56

most installed skills ever. Here's what

1:58

it does. It checks every file at it,

2:00

every commit, every move Claude makes

2:02

for security holes before they even

2:04

happen. It actually maps the problems to

2:06

real industry frameworks like OWASP, the

2:09

same framework used by billion-dollar

2:11

software companies. Using these

2:13

frameworks, it flags risky operations

2:15

before they ever run. The more

2:16

autonomous Claude gets, the easier it is

2:19

for it to quietly introduce a

2:20

vulnerability you'd never catch. Because

2:22

of this, enterprises are now treating

2:24

this skill as mandatory, [music]

2:26

not optional. And pro tip, there's this

2:28

company called Semgrep that specializes

2:30

in cybersecurity, who have a range of

2:32

free skills around security. If you pair

2:34

the security guidance skill with the

2:36

Semgrep set of skills, you can run much

2:39

deeper reviews that would easily put

2:41

your code security in the top 1% of Vibe

2:43

coders. If you thought that was cool,

2:45

wait till you see number 11, the

2:47

TypeScript LSP, 177,000

2:50

installs. LSP sounds scary, trust me,

2:53

it's not. It just gives Claude a

2:55

real-time map of your entire codebase.

2:57

Every type, every reference, every

2:59

import. Think of it as handing Claude a

3:01

GPS for your project instead of making

3:04

it read every file blind. And this is a

3:06

big deal because it dramatically cuts

3:08

down on Claude's AI hallucinations. And

3:11

honestly, experts say you should install

3:13

the LSP skill for your main language

3:15

before anything else. TypeScript tops

3:18

the list, but there's actually a whole

3:19

family of coding languages.

3:21

>> [music]

3:21

>> You've got Python's Pylance, which sits

3:24

at 91,000 installs, then go Rust, Java,

3:27

all the way down. Whatever you build in,

3:29

there's one for you. Just ask Claude

3:31

what's best for your task. 10, Feature

3:34

Dev, 217,000 installs. This is a full

3:37

agentic workflow for building a new

3:40

feature end-to-end. It runs a clean

3:42

five-step pipeline, explores the

3:43

codebase, designs the architecture,

3:46

writes the code, generates the test,

3:48

then reviews everything. So, So, of one

3:50

Claude juggling everything, you've got a

3:52

little team working in sequence. I

3:54

actually pointed this out a feature for

3:56

one of my apps the other day and I

3:57

walked off to make a coffee. A few

3:59

moments later, I came back to a finished

4:00

tested feature sitting there waiting for

4:02

me. For a solo vibe coder, that's like

4:04

hiring an entire dev squad for the price

4:06

of one prompt. Number nine, Claude.md

4:10

management, 223,000 installs. Now, this

4:13

one solves Claude's most annoying flaw.

4:15

Every new session, Claude forgets your

4:17

stack, your naming rules, your

4:18

conventions, all of it. The Claude.md

4:21

file is basically Claude's long-term

4:23

memory for a project. This skill helps

4:25

keep that memory file updated

4:27

automatically as your project grows. So,

4:30

you stop re-explaining the same thing

4:32

every single morning. Just set it up

4:33

once and Claude remembers who you are.

4:36

All right, between you and me, if you

4:37

thought that was useful, let me tell you

4:39

about number eight, Playwright, 248,000

4:43

installs. This gives Claude the power to

4:45

autonomously control its own headless

4:47

browser, meaning it can literally search

4:49

the web or even better, test out the

4:52

features of your app. It literally spins

4:54

up a browser, clicks through your UI,

4:56

checks everything works, and fixes the

4:58

tests when they break. I'm not going to

5:00

lie, writing tests is the part of

5:02

building I actually hate the most. So,

5:04

handing it off to Claude off the rip

5:06

honestly felt a little wrong. And I'm

5:08

not the only one that hates doing it.

5:10

The creator of Claude, Boris Cherny

5:12

himself, literally created a custom

5:14

skill called {slash}go, so that he can

5:16

quickly tell Claude to use Playwright to

5:19

autonomously test his own code, allowing

5:22

him to focus on the finer things in

5:24

life. Number seven, the GitHub MCP,

5:27

261,000 installs. Quick term, MCP just

5:30

means model context protocol. In plain

5:33

English, it's a bridge that connects

5:34

Claude to a live outside service. This

5:37

one plugs Claude directly into GitHub,

5:39

allowing you to use its features without

5:41

you ever leaving your workspace. This is

5:43

actually the most installed connector of

5:45

all of them, way ahead of Versel, Figma,

5:48

and Slack. It turns Claude from a local

5:50

helper into an actual member of your

5:52

team that can actually make changes on

5:54

your project repo. Fancy that. Number

5:57

six, Skill Creator, 283,000 installs.

6:00

Believe it or not, this one's actually

6:01

my favorite because it's the skill that

6:04

builds skills.

6:05

>> What did he say?

6:07

>> You can imagine how powerful this thing

6:09

is. You describe a task in plain English

6:11

and Skill Creator drafts, tests, and

6:13

packages it into a brand new reusable

6:16

skill. And it's officially backed by

6:18

Anthropic. People are saying it's the

6:19

first skill that you should actually

6:21

ever install. Why? Because you're no

6:23

longer stuck with whatever's pre-built.

6:25

Here's what I recommend. After a good

6:27

session, just tell Claude, "Based on

6:29

this conversation, build me a skill so

6:31

we can do this faster next time." Boom,

6:33

free custom skill. And if you're already

6:34

finding this video useful, do me a favor

6:36

and smash that like button. It genuinely

6:38

helps me out. I have all the links to

6:40

every skill in the description below.

6:42

Number five, Code Simplifier, 284,000

6:45

installs. Here's an uncomfortable truth.

6:48

AI-generated code, including Claude's

6:50

own, is often bloated and

6:52

over-engineered. This skill runs a

6:54

compression pass on it. It strips out

6:56

the redundancy, simplifies the logic,

6:58

and cuts technical debt, all without

7:00

changing what the code actually does.

7:03

Think of it as Claude cleaning up after

7:04

itself. For five coders shipping fast,

7:07

this is how you stop your app from

7:09

turning into spaghetti. Four, Code

7:11

Review, 347,000 installs. This automates

7:14

the entire code review process. Claude

7:17

analyzes your changes, checks them

7:19

against your standards and the original

7:20

task, then spits out a structured review

7:23

report. It catches issues before a human

7:25

ever has to look. It writes your pull

7:27

request descriptions, it flags

7:28

architecture problems early. A lot of

7:30

people stack it with the PR Review

7:32

Toolkit, which adds a confidence score

7:34

to every single finding. genuinely one

7:36

of the biggest time-savers on this

7:38

entire list. Number three, Context

7:40

Seven, 348,000 installs. Remember how I

7:43

said Claude forgets? Context 7 is the

7:45

heavier duty fix. It actually gives

7:47

Claude live documentation lookup and

7:49

smart search across huge code bases. So,

7:52

instead of only knowing what fits in its

7:54

own context window, it can pull the

7:56

exact docs and patterns it needs on

7:57

demand. In big projects, this is the

8:00

difference between Claude following your

8:01

conventions and Claude inventing

8:03

complete nonsense. This is actually one

8:05

of three skills experts say you should

8:07

install globally on every project. Hold

8:10

that thought because the other two are

8:11

coming up right now. The second most

8:14

downloaded skill, Superpowers, 752,000

8:18

installs. This is not a single skill,

8:20

it's actually an entire framework. It

8:22

forces Claude to follow a disciplined

8:24

development methodology like a senior

8:27

engineering team. Here's the problem it

8:29

fixes. AI agents are eager. They jump

8:32

straight into writing code before they

8:33

even understand what you actually want.

8:35

Superpowers actually stops this from

8:37

happening. It makes Claude brainstorm

8:39

first, break the work into tiny atomic

8:41

tasks, and follow strict test-driven

8:44

development. If Claude writes code

8:45

before writing a failing test, the

8:47

framework forces a restart. It was built

8:49

by a developer named Jesse Vincent, and

8:51

the repo is one of the most starred AI

8:53

coding frameworks in the world. Even

8:56

experts like Simon Willison point to it

8:58

as the fix for AI's hallucinated

9:00

enthusiasm problem.

9:03

Hey, I'm curious. Are you already paying

9:05

for Claude or Codex? I recently dropped

9:07

Ace, an app that helps you get more out

9:09

of your AI subscriptions by making them

9:11

work together as a team. Like check this

9:13

out. One AI can research, another can

9:15

build, and another can check the work.

9:18

You can make simple teams like this

9:19

where Claude and Codex work together to

9:21

find the best answer, or you can build

9:23

something much bigger like this

9:25

autonomous app factory that keeps

9:26

building apps while I sleep. Inside Ace,

9:29

you can give tasks to your team in one

9:31

group chat, create loops that run tasks

9:33

again and again, or let one powerful AI

9:36

manage a group of cheaper ones so you

9:38

can spend less on tokens. You no longer

9:41

need to code all of that from scratch.

9:43

Just drag, drop, and connect the dots.

9:46

Now live on Mac and Windows, use code

9:48

Doobie for 10% off. I'll leave a link in

9:51

the description. Back to the video. All

9:54

right. Now, before I reveal a number

9:55

one, I need to give a few honorable

9:57

mentions because not every useful skill

9:59

made it in the official top 12, but some

10:01

of these are genuinely insane. First up,

10:04

Caveman. And yes, it does exactly what

10:06

it sounds like. It makes Claude talk

10:09

like a caveman. But weirdly, this is

10:11

actually useful because Claude loves to

10:13

yap. It explains every tiny step like

10:15

it's writing a thesis. Caveman strips

10:18

all that away. Less filler, less waffle,

10:20

same output. So, instead of Claude

10:22

saying, "I'll now inspect the relevant

10:24

files," it just says, "Me check files"

10:26

like a caveman. The creator claims it

10:28

can cut output tokens by around 75%,

10:31

which means faster sessions, cheaper

10:33

usage, and way less mental clutter. It

10:35

sounds like a meme, but it solves a real

10:37

problem. Next, G-stack. This one was

10:39

made by Garry Tan, the CEO of Y

10:42

Combinator, and it's basically his full

10:44

Claude code setup in one repo. CEO

10:46

review, engineering review, design

10:48

review, quality assurance, security,

10:50

release management, docs, everything.

10:52

Instead of letting Claude randomly build

10:54

and pray, G-stack turns it into a proper

10:56

startup workflow. Think, plan, build,

10:59

review, test, ship, reflect. And that

11:02

matters because once you start building

11:04

real apps with AI, the hard part is not

11:06

getting code written, the hard part is

11:08

actually judgment. Should we build this

11:10

app? Is the scope too big? Does the

11:13

design suck? Did we actually test it?

11:15

G-stack helps Claude think through those

11:17

layers before it cooks your project.

11:19

Next up, Karpathy skills. Andrej

11:21

Karpathy, the co-founder of ChatGPT and

11:24

head of AI at Tesla, once wrote a thread

11:26

complaining about how Claude writes

11:28

code. He mentioned three failure modes.

11:30

Forest Cheng read the thread and

11:31

packaged the complaints into four

11:33

behavioral rules inside a single claw.md

11:36

file and dropped it on GitHub. Currently

11:38

sitting at 160,000 stars, it became the

11:41

fastest growing single file repo of

11:43

2026. The file teaches Claude four

11:45

simple rules. Think before coding, keep

11:47

it simple, make surgical changes, and

11:49

define success before touching anything,

11:51

which sounds obvious. This actually

11:53

fixes one of Claude's biggest problems.

11:55

It's way too confident. It assumes

11:57

things, it over-engineers, it changes

12:00

files you never asked it to touch.

12:01

Karpathy skills slows it down and it

12:04

forces work with more discipline. So,

12:06

those are the honorable mentions.

12:08

Caveman saves tokens, G stack gives

12:10

Claude a startup operating system, and

12:12

Karpathy skills stops Claude from acting

12:14

like an overconfident intern. Now, with

12:16

that out of the way, let's talk about

12:18

number one. The most installed Claude

12:20

skill on the entire planet with 829,000

12:24

installs, it's time to talk about

12:26

front-end design. So, why is this king?

12:29

Two words, AI slop. You know the look,

12:32

purple gradients, the same boring font

12:34

everywhere, generic card layouts, that

12:36

glassy effect slapped on everything. The

12:38

glassy effect does look kind of cool.

12:40

Every AI generated app looks identical

12:43

and developers are sick of it. Front-end

12:44

design forces Claude to commit to a

12:46

bold, distinctive visual style before it

12:48

writes a single line of UI. Brutalist,

12:51

minimalist, retro-futuristic,

12:53

whatever you want. And then it enforces

12:55

it the whole way through. I use this

12:57

across all of my apps and the results

12:59

speak for themselves. Like watch how

13:01

Tariq, the lead developer at Anthropic,

13:04

one-shot a retro music player. Genuinely

13:07

impressive. This is the third member of

13:09

that infrastructure trio I teased,

13:11

front-end design, context seven, and

13:13

superpowers. Install those three

13:16

globally and Claude gets better on

13:18

literally every project you touch. Now,

13:20

before you go around crazily installing

13:21

everything, I have to educate you. These

13:23

skills are not prompts. The best

13:26

builders treat them as standard

13:28

operating procedures for an employee

13:30

that never sleeps. A prompt ask Claude

13:32

to think. A skill actually teaches

13:35

Claude how to work. That's the

13:36

difference and it actually gets bigger.

13:38

These skills run on an open standard

13:41

called agent skill.io,

13:43

which means they're not actually locked

13:44

to Claude at all. The same skill works

13:46

in cursor, in co-pilot, across basically

13:49

every AI agent on the market. You're not

13:51

learning a Claude trick, you're building

13:53

a portable workforce that follows you

13:56

everywhere. But there is a dark side and

13:58

you do need to hear it. Anthropic flat

14:00

out warns that plugins are highly

14:02

trusted components that run code with

14:04

your permissions. Security researchers

14:06

have already documented malicious skills

14:08

trying to silently hijack tool routing

14:10

in the background. So the rule of thumb

14:12

is simple. Only install from the

14:14

official marketplace and treat every

14:16

skill like a dependency you'd actually

14:18

vet. And that brings me to the one rule

14:20

that I promised at the start. Do not

14:22

install all 12. I know, I know, you want

14:25

the whole arsenal, but every skill you

14:27

add eats context window and piles on

14:29

more slash commands. The sweet spot

14:31

experts agree on is three to five skills

14:33

matched to your actual workflow. Start

14:35

with LSP for your language, add the

14:37

infrastructure trio that I talked about,

14:39

then pick one or two more for whatever

14:41

you actually do. Check out this video

14:43

YouTube thinks you'll love it. I'll see

14:44

you over there. Peace.

More transcripts

Explore other videos transcribed with YouTLDR.

Get the TLDR of any YouTube video

Transcribe, summarize, and repurpose videos in 125+ languages — free, no signup required.

Try YouTLDR Free