The Best Claude Skills According to Reddit (And What's Overrated)

The Skills Everyone's Installing (and Why the Hype Outruns the Evidence)

Since Anthropic launched skills in October 2025, thousands of SKILL.md packages have flooded GitHub, and a handful of names now dominate every "must-install" list: Grill Me, Karpathy Guidelines, Superpowers, Frontend Design, and Handoff. The numbers cited by practitioners are eye-catching. Grill Me reportedly sits at 1.1 million installs, Superpowers has 280k+ GitHub stars with 25k+ forks, and Anthropic's own Frontend Design skill sees 110k+ weekly installs, according to a detailed practitioner review.

Here's the tension worth sitting with: install counts and star counts are the community's default trust signals, yet popularity tells you nothing about whether a skill actually works, or whether it's safe. In one documented campaign, security researchers confirmed that 5 of the top 7 most-downloaded skills were outright malware at peak infection. The same analysis found 26.1% of 42,447 analyzed skills carry at least one vulnerability.

We'll be honest about our own evidence base here. There's no verified public ranking of "best" skills. What exists is practitioner testing from people who run these skills daily, plus the adoption figures above, which are self-reported and not independently audited. That's a real gap, and it's part of why SkillzBench maintains a free directory that pins every skill version to a commit SHA, security-scans it, and publishes benchmarked Lift results separately from any rating.

The names worth knowing right now:

• Grill Me and the Karpathy Guidelines repo (210k+ stars) push Claude to critique its own work harder before shipping.
• Superpowers is a large workflow framework, popular but reportedly needing real setup time.
• Frontend Design improves UI output, though practitioners note it doesn't fit enterprise dashboards.
• Handoff structures context for passing work between sessions or agents.

Even the popular ones carry documented limits. The Karpathy skill reportedly adds friction on trivial tasks, and Anthropic's own enterprise documentation warns that broad, multipurpose skills can "steal triggers" from narrower ones and degrade agent performance, with a hard cap of 20 skills per API request. Skill hoarding, in other words, actively hurts you.

So treat these five as the community's shortlist, not a verified leaderboard. The next sections look at what each one actually does, and where the hype outruns the evidence.

What the Evidence Says Is Overrated: Broad Skills, Skill Hoarding, and Vague Triggers

Here's the uncomfortable part: some of the most popular Claude Skills actively work against you. Anthropic's own documentation says so, and the evidence is worth reading closely before you install another multipurpose "productivity" skill.

The core problem is trigger competition. According to Anthropic's enterprise documentation, broad skills with general descriptions "steal triggers" from narrow ones. When a skill claims to handle everything vaguely, Claude pattern-matches against that description at startup and fires it on tasks it shouldn't touch. The docs also warn that with too many skills active, Claude may fail to select the right skill or miss relevant ones entirely. And there's a hard ceiling: a maximum of 20 skills per API request. Skill hoarding isn't just clutter, it's a performance tax.

Practitioners who've tested dozens of skills flag the same red flags. In one detailed hands-on review, the author calls out a 4,000-token SKILL.md that loads on every task, vague triggers like "productivity tasks" (their verdict: "Productivity is not a category. Claude cannot route to it reliably"), self-reported metadata, and skills with no worked examples. Their rule of thumb: three worked examples beat twenty bullet-pointed constraints, and the core instructions should fit on a phone screen.

• A SKILL.md so large it eats context on every session, whether you need it or not
• Vague descriptions that produce vague activation, or no activation at all
• One skill trying to do five jobs, stealing triggers from skills that do those jobs well
• No worked examples showing when the skill should and shouldn't fire

Even the darlings have documented limits. The same practitioner review notes that Anthropic's Frontend Design skill, despite 110k+ weekly installs, "doesn't fit enterprise dashboards." Superpowers demands setup time before it pays off. The Karpathy Guidelines skill "adds friction on trivial tasks." Popularity measures downloads, not fit for your workload.

So how do you sort the useful from the bloated without installing everything and testing by hand? That's exactly the problem SkillzBench's free directory is built around: every skill gets security-scanned, pinned to a commit SHA, and benchmarked in a sandbox with and without the skill, so you can see the measured Lift before it ever touches your agent. The per-agent loadouts also let you toggle exactly which skills each agent sees, which directly addresses the over-triggering problem Anthropic documents.

The honest takeaway: the best skill is usually the narrow one that does one job with a sharp description. Everything else is context you're paying for on every prompt.

The Security Problem Nobody's Voting On

A skill with 200,000 GitHub stars can still be the one reading your SSH keys. That contradiction sits at the center of the Claude skills ecosystem right now, and it's the reason a thoughtful "best of" list isn't really a quality ranking. It's a risk assessment.

The numbers are stark. Security research from the Cloud Security Alliance found that 26.1% of 42,447 analyzed skills carry at least one vulnerability. A separate major audit put the figure at 36.82%. In one documented campaign, 1,184 malicious skills flooded a major registry across 12 publisher accounts, and at peak infection, 5 of the top 7 most-downloaded skills were confirmed malware. Star counts and install numbers, the same signals Reddit threads and practitioner blogs use to recommend skills, were actively pointing users at compromised code.

The mechanism matters as much as the count. Skills are markdown files. Three lines of natural language in a SKILL.md can instruct an agent to read ~/.ssh/id_rsa and POST it to an external endpoint. No eval(). No subprocess. No detectable code signature. Researchers describe this as the consent gap: users approve what they see, but hidden payloads operate under the same trust context. A live proof-of-concept delivered ransomware through a single hidden helper function.

Why star counts fail as a safety proxy:

• Stars reflect adoption speed, not vetting. A malicious skill can accumulate thousands of installs before anyone audits it.
• Skills propagate across platforms. A poisoned skill on Claude Code can reach Cursor, Codex CLI, and OpenClaw with no re-review.
• Anthropic's own enterprise documentation warns that "skill authors should not be their own reviewers" and that every update requires a full security review.
• Built-in scanning covers only part of the surface: it doesn't extend to the Skills API, pre-existing skills, or CMEK/ZDR/HIPAA configurations.

The OWASP Agentic Skills Top 10, formalized in March 2026, now treats these failure modes as a first-class security category. That's overdue. The skills ecosystem grew from a clean October 2025 launch into thousands of packages in months, and verification hasn't kept pace. Popularity is a distribution channel, not a safety seal.

If you want to use community skills without flying blind, the practical move is to treat every install like untrusted code: pin to a commit SHA, scan for known patterns, and benchmark in a sandbox before letting a skill touch real work. SkillzBench's free directory runs that verification layer continuously, pinning versions, security-scanning, and publishing benchmark Lift separately from ratings, so install counts never double as trust scores. Browse verified skills, toggle exactly which ones each agent sees, and skip the rest.

How to Pick Skills That Actually Work: A Practical Checklist

A skill's description is what Claude pattern-matches against at startup, so a vague one like "productivity tasks" produces vague activation or none at all. Anthropic's own guidance warns that broad, multipurpose skills "steal triggers" from narrow ones, and that with too many skills active, Claude may fail to pick the right one entirely. Since the API caps requests at 20 skills, hoarding is a real performance cost.

Use this checklist before installing anything:

• Does the description name a specific routing rule, not a category?
• Is the SKILL.md lean, with the bulk of the material in reference files?
• Does it do one job, with three worked examples instead of twenty bullet-point constraints?
• Do its bundled scripts make any network calls the documentation doesn't disclose?
• Has anyone besides the author reviewed it? Anthropic's rule is blunt: skill authors should not be their own reviewers.

Then test triggering accuracy with 3 to 5 representative queries per skill, as Anthropic recommends, and treat every update as a new deployment requiring full security review. That last point matters more than it sounds: one audit found 36.82% of skills carry security flaws, a larger analysis put 26.1% of 42,447 skills at one or more vulnerabilities, and at the peak of one campaign, 5 of the top 7 most-downloaded skills were confirmed malware. Popularity is not a safety signal.

Verification is the missing layer. SkillzBench pins every skill version to a commit SHA, security-scans it, and publishes benchmark Lift separately from ratings, so you can see whether a skill actually helps before it touches your agent. Browse the free directory and toggle exactly which skills each agent sees at skillzbench.com.

Verify Before You Trust: Benchmarking Skills with SkillzBench

A skill's star count tells you nothing about whether it works or whether it's safe. In one documented campaign, 5 of the top 7 most-downloaded skills were confirmed malware at peak infection, and broader analysis found roughly 26% of 42,447 analyzed skills carry at least one vulnerability. Popularity, in other words, is not a trust signal.

That's the gap SkillzBench (skillzbench.com) fills, and it's free. Instead of trusting a README or an install counter, you get verification and measured performance before anything touches your agent.

Here's what the platform does:

• Verifies every skill: each version is pinned to a commit SHA, security-scanned, license-checked, and quality-judged, with a trust score from 0 to 100 built on security, quality, license, maintenance, and community signals.
• Benchmarks in a sandbox: every skill is tested with the same model, with and without the skill, and the resulting Lift is published in percentage points. Lift is shown separately from ratings, so a score and a measured result never blur together.
• Equips agents selectively: one free MCP connector plus per-agent loadouts means each agent only sees the skills you toggled for it.
• Stays current: upstream changes are tracked, skills get re-scanned and re-benchmarked, and you're notified when something shifts.

That last point matters more than it sounds. Anthropic's own enterprise documentation warns that with too many skills active, Claude may fail to select the right skill or miss relevant ones entirely, and there's a hard cap of 20 skills per API request. Skill hoarding actively degrades performance. Per-agent loadouts solve this directly: your coding agent gets the skills it needs, your writing agent gets different ones, and neither drowns the other's triggers.

The benchmarking pillar also addresses a problem the community keeps circling. Practitioners recommend testing skills against 3 to 5 representative queries before production, but almost nobody actually does it. SkillzBench runs that comparison for you and publishes the result, so "does this skill actually help?" becomes a number you can read rather than a vibe you have to test yourself.

Given that security researchers describe the SKILL.md file as "the new package.json, and it's already compromised," browsing a directory where everything is pinned, scanned, and measured is the sensible implementation step. Current numbers and verified results live at skillzbench.com, and the directory, benchmarks, alerts, and MCP connector are all free.

Skills, proven. Browse verified skills, check their sandboxed Lift results, and equip your agents for free at skillzbench.com.