In Part I, we mapped the anatomy — what Skills are, how they load, how to build your own. This companion piece answers the question that matters more: which ones are people actually using?
The Skills ecosystem crossed 85,000 indexed entries in under six months. The signal-to-noise ratio, predictably, is rough. Most Skills are experiments. Some are duplicates. A few are remarkably good. And a small handful have quietly become infrastructure — the kind of tooling teams rely on without thinking about it, the way you rely on git or Slack.
This article organizes the landscape by who's using what, and why. We move from enterprise down to the individual builder, because the patterns change at every scale.
The Leaderboard — Most Installed Skills
Before we slice by role, here's the raw popularity data. These are the most-installed Skills as of March 2026, according to skills.sh install tracking. The chart animates when you scroll to it — watch the bars race.
Notice something? The number-one Skill is a meta-skill — a Skill that discovers and installs other Skills. The ecosystem is self-reinforcing. And three of the top five come from Vercel and Anthropic, not community contributors. Official Skills still dominate by volume.
Enterprise — Where Governance Meets Productivity
Enterprise adoption of Skills follows a predictable pattern: start with document Skills (quick wins for legal, HR, finance), then layer in compliance-specific custom Skills, then build internal Skill libraries that codify institutional knowledge. The organizations pulling the most value aren't using the flashiest Skills — they're using the ones that eliminate the sentence "let me explain how we do this here."
The universal starting point. When Thomson Reuters cut legal document research time from hours to minutes, or when enterprise compliance teams began auto-generating regulatory filings from raw data, these four Skills were doing the heavy lifting. They're pre-installed on every paid plan and require zero setup.
Enterprise pattern: Combine pdf-reading with a custom extraction Skill that knows your company's specific contract structure — clause numbering, risk categories, escalation triggers. The pdf Skill handles the mechanics; your custom Skill handles the domain knowledge.
"Read our master services agreement PDF, extract all indemnification clauses, compare them against our standard terms template, and flag any deviations in a Word document with redline markup."
Not technically a Skill in the SKILL.md sense, but tightly adjacent and increasingly bundled into enterprise workflows. Claude Code Security scans codebases for vulnerabilities that static analysis misses — broken business logic, subtle access control flaws, data flow issues. Every finding goes through multi-stage self-verification before reaching a human analyst. Currently in limited research preview for Enterprise and Team customers.
Enterprise pattern: Pair with custom compliance Skills that map findings to specific frameworks — NIST 800-53, ISO 27001, PCI DSS, SOC 2. The security scan finds the problem; your custom Skill classifies the regulatory impact.
The internal-comms Skill provides templates for 3P updates, newsletters, FAQs, and incident reports. The brand-guidelines Skill ensures every artifact — presentations, one-pagers, landing pages — uses your company's exact colors, fonts, and visual hierarchy. Together, they eliminate the "this doesn't look like us" feedback loop.
Enterprise pattern: Fork brand-guidelines and replace Anthropic's palette with your own. Deploy organization-wide via the admin console. Now every Claude-generated deliverable is automatically on-brand.
"Write a 3P update for the VP of Engineering covering the data platform migration. Progress: schema validation complete. Plans: staging deployment next Tuesday. Problems: vendor API rate limits on the CDC pipeline."
The sleeper hit for enterprise knowledge teams. Three-stage collaborative writing: context gathering (Claude interviews you for background, constraints, politics), iterative refinement (section-by-section, back and forth), and reader testing (a fresh Claude with zero context reads the document and flags blind spots). That last stage is quietly revolutionary — it catches the assumptions that live in your head but never made it onto the page.
Enterprise pattern: Use for technical design docs, decision documents, RFCs, and board memos. The reader-testing stage alone has caught missing context that would have delayed approval cycles by weeks.
Enterprise Security Reality
Skills uploaded to Claude.ai don't sync to Claude Code or the API. Each surface requires separate deployment. Enterprise admins should maintain Skill source files in Git as the single source of truth. Pin Skills to specific versions in production. Treat every update as a new deployment requiring a full security review. And never — never — deploy Skills from untrusted sources without auditing every file in the folder, not just the SKILL.md.
Growth Teams & Mid-Market — Speed at Scale
Growth-stage companies don't need governance frameworks. They need leverage. The Skills that win here are the ones that let a 15-person team operate like a 50-person team — shipping faster, producing more polished artifacts, and avoiding the "explain it to Claude again" tax.
The most complete multi-agent development workflow available as a Skill. Not a single Skill — it's a composable framework that structures the full software development lifecycle: brainstorming, git worktree setup, implementation planning, subagent-driven execution, TDD (red-green-refactor), and code review before merging. Ships with /brainstorm, /write-plan, /execute-plan commands and a skill-search tool.
Growth pattern: Install Superpowers on your engineering team. The spec → plan → subagent → review → merge loop enforces repeatability. Junior engineers ship with the rigor of seniors. Senior engineers ship at 3x speed.
/plugin marketplace add obra/superpowers-marketplaceBuilt by Corey Haines specifically for technical founders wearing too many hats. Twenty-plus Skills in one install covering CRO analysis, copywriting frameworks, SEO strategy, email sequences, A/B test design, and growth playbooks. For solo founders or lean teams, this is the one collection worth having rather than hunting individual Skills across repositories.
Growth pattern: The SEO and CRO Skills are the most immediately useful. Feed them your landing page URL and get structured audits with prioritized action items — not generic advice, but specific changes with expected impact.
github.com/coreyhaines31/marketingskillsMakes any developer capable of programmatic video production without leaving their code editor. Gives Claude deep knowledge of Remotion animations, timing, audio, captions, and 3D — so it writes correct Remotion code on the first try. Shipped January 2026 and immediately became one of the most-installed Skills in the ecosystem.
Growth pattern: Product marketing teams use this to generate demo videos, social clips, and onboarding walkthroughs directly from code. No video editing software. No external vendors. Ship a feature, generate the promo video in the same PR.
Two companion Skills from Vercel that together represent the second and third most-installed Skills in the entire ecosystem. The React Skill codifies Vercel's production patterns — server components, caching, data fetching, edge middleware. The Design Skill pulls the latest design guidelines from the source repo and validates your interface code against every rule before you ship.
Growth pattern: If you're a Next.js shop, these two Skills should be your first install. They eliminate an entire class of "why is this slow?" and "why does this look wrong?" conversations in code review.
Startups & Solo Builders — Maximum Leverage
At the startup end, Skills aren't about governance or compliance. They're about making one person feel like three. The most valuable Skills here are the ones that eliminate the re-explanation tax — the cognitive cost of teaching Claude your preferences, your brand, your workflow, every single conversation.
The canonical anti-slop Skill. Covered in Part I, but it earns its place here because solo builders rely on it more than anyone. When you don't have a designer on the team, the difference between "AI-generated landing page" and "looks like it was designed by a human" is this one Skill. Internal tools and prototypes become shareable without embarrassment.
"Build me a SaaS landing page for a developer tool that turns API logs into debugging timelines. Tone: clean, technical, no gimmicks. Think Linear meets Datadog."
Drop a URL, receive a structured audit: technical SEO issues, page-level analysis, schema markup validation, sitemap generation, and AI search optimization (GEO/AEO). Structured as 12 sub-skills running parallel subagents. For anyone running a content site or SaaS with organic traffic ambitions, this makes regular SEO audits practical rather than aspirational.
github.com/AgriciDaniel/claude-seoNot a specific published Skill — it's a pattern that keeps appearing in every "best Skills" roundup because every builder eventually creates their own version. A Brand Voice Skill captures your writing tone, audience, forbidden phrases, formatting preferences, and editorial standards. Build it once, never explain your style again. One creator reported building theirs in 25 minutes and never re-explaining their writing style since.
Startup pattern: Start with a simple version that lists your audience, tone words, anti-patterns (words you never use), and a few example paragraphs. Iterate as you notice Claude drifting. This is your highest-ROI custom Skill.
---
name: brand-voice
description: Applies our editorial voice to all
written content. Trigger on any writing, blog,
email, social post, or copy request.
---
Audience: Technical practitioners, not executives.
Tone: Direct, warm, zero fluff. Think: engineer
explaining something to a peer over coffee.
Never use: "leverage," "synergy," "unlock,"
"game-changing," "it's worth noting."
Always: Lead with the insight. Cut the preamble.
Covered in depth in Part I, but it belongs in the startup toolkit because the most useful Skill you'll ever install is often one you build yourself. The Skill Creator walks you through intent capture, SKILL.md drafting, test prompts, evaluation, and description optimization. Turn "I keep explaining this to Claude" into "Claude just knows how to do this" in under an hour.
Which Skills for Which Role?
Click your role to see the recommended starter stack. These aren't exhaustive — they're the Skills that deliver the most value in the first week.
Start with: Superpowers for the dev lifecycle, Vercel React + Web Design for frontend quality, pdf-reading for spec extraction, and the Skill Creator for codifying your team's patterns.
Custom Skill idea: A code review checklist Skill that enforces your team's conventions — naming, test coverage thresholds, PR description format.
Start with: Doc Co-Authoring for PRDs and specs, pptx for stakeholder decks, internal-comms for status updates, and xlsx for data analysis on user research.
Custom Skill idea: A sprint retrospective Skill that ingests Jira data and produces a structured retro doc with themes, metrics, and action items.
Start with: Marketing Skills collection for CRO/SEO/copy, frontend-design for landing pages, Claude SEO for audits, Remotion for video content, and brand-voice (custom) for consistency.
Custom Skill idea: A campaign brief Skill that takes your ICP, channels, and budget and outputs a structured launch plan with copy variants for each channel.
Start with: Everything from Marketing plus Doc Co-Authoring for investor memos, xlsx for financial models, brand-voice for consistent external comms, and the Skill Creator because your most valuable Skills are the ones only you can build.
Custom Skill idea: An investor update Skill. Define your metrics, narrative structure, and tone once. Generate monthly updates from raw numbers in under five minutes.
Start with: xlsx for spreadsheet work, pdf-reading for extracting tables from reports, docx for writing data documentation, and mcp-builder for connecting Claude to your warehouse.
Custom Skill idea: A data quality report Skill. Feed it a dataset, get a structured profiling report: null rates, distribution anomalies, schema drift flags, and lineage notes.
Should You Build, Install, or Skip?
Not every workflow needs a Skill. Use this quick decision flow to figure out if a Skill is the right solution for your problem.
Where to Find Skills
The ecosystem is fragmented but navigable. Here are the directories worth checking regularly:
anthropics/skills (GitHub) — Anthropic's official repository. Document Skills, example Skills, and the source-available implementations that power Claude.ai's file creation features. Apache 2.0 for most, source-available for document Skills.
skills.sh — Install tracking and discovery. The install numbers cited in this article come from here. Use find-skills (the meta-skill) to search from within Claude Code.
Anthropic Academy — Free courses on building and distributing Skills, including the "Introduction to Agent Skills" course on Skilljar.
awesome-claude-skills (GitHub) — Curated list maintained by the community. Good signal-to-noise ratio. Tracks timeline of ecosystem milestones.
obra/superpowers — 40.9K stars. Both a Skill library and a plugin marketplace. Install via /plugin marketplace add obra/superpowers-marketplace.
Antigravity Awesome Skills — 1,234+ Skills organized by role-based bundles (Web Wizard, Data Wrangler, etc.). Install all at once or pick a bundle.
clawhub.com — Over 5,700 community Skills browsable by category.
claudemarketplace.com — Community-curated marketplace with install instructions.
The Trust Problem
Anthropic is explicit: only use Skills from trusted sources. The ecosystem has crossed 85,000 entries. The vast majority are harmless. But a malicious Skill can instruct Claude to execute arbitrary code, access sensitive files, or transmit data externally. If you're evaluating a community Skill, read every file in the folder. If it contains scripts, understand what they do before installing. For enterprise deployment, require a security review using Anthropic's published review checklist before approving any Skill.
The Rule of Three — A Closing Framework
After surveying the landscape, here's the simplest way to think about your Skill stack:
Install three official Skills. The document Skills (pdf, docx, xlsx, pptx) are already there. Add frontend-design if you build anything visual. Add product-self-knowledge if you ask Claude about Claude.
Install three community Skills for your role. Use the role matrix above. If you're an engineer, that's Superpowers + Vercel React + Web Design Guidelines. If you're a founder, that's Marketing Skills + Claude SEO + Remotion.
Build three custom Skills. Your brand voice. Your most-repeated workflow. Your team's specific format for the deliverable you produce most often. These are the Skills that deliver the most value, because no one else can build them for you.
Nine Skills total. That's a Skill stack that covers 80% of your daily Claude interactions without bloating your context window or creating trigger conflicts. Start there. Expand intentionally.