I'd spent two weekends before that trying to assemble the same thing from free sources. Roughly 12 hours across claudemarketplaces.com (6,700+ skills, mostly bimodal quality), claudeskills.info (smaller, slightly more curated), the ComposioHQ awesome-list on GitHub, and alirezarezvani/claude-skills (313+ skills, no shared spec). Of the 14 production-grade skills I kept after that sweep, four happened to overlap with the pack. The other ten were the actual purchase.

Worth doing.

This post is the inventory I wish I'd had before either weekend started.

What a Claude Code skill pack actually is

A Claude Code skill is a single markdown file with YAML frontmatter. name, description, body. Claude reads the description on every new session and decides whether the skill applies based on what you've typed. The body is the SOP: the steps Claude follows when the skill triggers. The full spec is at code.claude.com/docs/en/skills.

A skill pack is a folder of skills shipped together with the same conventions. The conventions are what separate $29 packs from free directory dumps. Three specifics:

The pack you can pay for carries a version field per skill (calver, like 2026.05) and a last_verified date. If a skill hasn't been re-tested against the current Claude model in 90 days, you know it's drifting. Most free repos don't carry versions at all.

Every skill ships a rubric.yml and a stdlib-only Python scorer that prints a quality trailer on every run. Something like 6 of 6 auto-checks passed. This is the unfakeable signal of paid-tier work, because writing the scorer is real engineering that has to happen one specific time per skill before the skill is shippable at the $29 tier. Free repos almost never include one. Nobody got paid to write it.

Every skill ships a reproducible example bundle. An examples/01-starter/ directory with input.md, output.md, and the actual quality-check.txt from running the scorer on the example. You can re-run the scorer yourself and verify the trailer matches what the author shipped. It's the customer's smoke test.

A pack missing those three things is selling curation, not engineering. That can still be worth $29. Your time is worth more than $29 to discover, test, and reject the 80% of free skills that don't survive contact with production, especially once you've installed enough of them that one skill starts colliding with another over the same trigger phrase. It's a different deal.

The 14 skills, ranked by how often I actually open them

Other "best Claude Code skills" listicles rank by author preference. I logged 14 days of session activity and ranked by frequency. Daily-use skills first. Quarterly-use last. A skill that fires once a quarter can still earn its slot if it's load-bearing when it does fire.

The four I open more than five times a week: humanizer (rewrites AI text to pass GPTZero / Originality.ai / Copyleaks; 22 banned AI-tells, em-dash budget, sentence-length variance), seo-blog-writer (YouTube URL or topic into a 2,000+ word post with schema and frontmatter; auto-chains humanizer), website-designer (markdown copy plus a brand.yml into a deployable single-page site; the page you're reading shipped from it), and skill-builder (brain-dump into a premium-pattern skill folder; the other 13 skills were built with it).

Weekly use: youtube-scraper (channel, playlist, or search into structured JSON via yt-dlp; no API key), news-scraper (Brave News plus HN Algolia into JSON), video-consumer (any YouTube/Loom/Vimeo into a Whisper transcript and visual timeline), landing-page-audit (URL or HTML into a prioritized fix list across rendering, structure, visual, copy, SEO), and seo-optimizer (deployed page into a fix list across title, meta, schema, sitemap, OpenGraph).

Monthly to quarterly: landing-page-copy and pricing-page-copy (used at launch, then rarely until the next launch), brand-research (one pass per product), competitor-research (Brave SERP plus site scrape), and stripe-checkout (one CLI command for a Payment Link).

What surprised me when I logged it: the four daily skills do roughly 80% of the work. The bottom five could ship as a separate "launch-time" pack and I wouldn't notice they were absent on a random Tuesday. If you're shopping for a pack and the seller can't tell you which skills you'll open daily versus quarterly, ask why.

Five workflows: where a pack beats a list

A single skill is a tip. A workflow is a verb you type once and walk away from. Five came in the box.

YouTube research to ranked blog post. youtube-scraper pulls the top 15 videos on a keyword. I pick three or four. video-consumer transcribes each into a local Whisper transcript plus visual timeline. seo-blog-writer writes a 2,500-word post against the current top-10 SERP. humanizer strips the AI tells. Total wall-clock from query to publishable draft: about three hours, of which 25 minutes is me at the keyboard.

Product idea to live Stripe storefront. brand-research produces the brief, landing-page-copy writes the page, website-designer renders, stripe-checkout wires the payment link. The skillshelf.co site shipped through this exact chain in one afternoon.

Vague task to reusable skill. skill-builder interviews you, scaffolds the SKILL.md, writes the rubric, generates the stdlib-only scorer, then humanizer runs the docs-mode audit on the prose. The skill gets symlinked into ~/.claude/skills/ and is ready in your next Claude Code session.

Existing site to audit plus redesign. landing-page-audit produces the fix list, website-designer re-renders with the fixes patched in. The audit I ran on the skillshelf launch caught two critical rendering bugs and three SEO gaps before the first real visitor saw the site.

Existing page to shipped SEO fixes. seo-optimizer audits title, meta, schema, sitemap, OpenGraph, keyword coverage. Fixes get patched into the copy file. website-designer re-renders. Deploy. The loop closes in under an hour for a single-page site.

The thing that makes any of this possible is the file-handoff convention. Every skill in the pack writes its output to a known path that the next skill reads from. No conversation state to carry. If you're evaluating a pack and the skills don't share file conventions, the workflows on the sales page are imaginary.

The four free directories I tried first

claudemarketplaces.com indexes 6,700+ skills. Skill quality is bimodal. Roughly 15% production-grade. The rest are experiments or abandoned forks. No way to tell which is which from the listing page itself, because the directory accepts submissions without auditing whether the underlying SKILL.md actually runs against the current Claude model. Best used as a search engine for when you already know the exact skill name you want.

claudeskills.info has about 400 skills with noticeably better curation. Browse-by-category works. Still no enforced quality bar, so installing five skills means learning five invocation styles in one afternoon.

ComposioHQ/awesome-claude-skills is the classic "awesome list" format. Curated, organized by category. Good starting point for learning what exists. Not a pack. You click through to each skill's repo and install separately, which works fine for the first one or two but turns into a maintenance burden by the time you've collected ten skills across ten different upstream authors with ten different ideas about how a SKILL.md should be structured.

alirezarezvani/claude-skills ships 313+ skills across engineering, marketing, product, compliance. The volume play. No rubric, no scorer, no shared frontmatter. Useful if you want to grep skill patterns to learn the format. Rough if you want to install ten and have them coexist.

I gave up on the free path after about 12 hours. The right comparison isn't "free versus $29." It's "12 hours of evaluation plus the risk of installing one skill that breaks another, versus $29 plus zero evaluation." If your hourly rate is over $2.50 the pack wins. The number on the door is $29 because the launch window is open; it's going to $99 after the first hundred buyers.

What got dropped from the pack

This is the transparency move every pack should make and almost none do. The curator was willing to tell me what got cut:

A general-purpose code-explainer skill. Anthropic's built-in Claude Code already explains code well enough that the third-party skill didn't beat the baseline. Dropped.

A Twitter thread writer. Worked, but humanizer plus a one-shot prompt produced equivalent output. Redundant.

A Slack message summarizer. Built it, used it twice, found that the Slack search UI plus a copy-paste into a fresh Claude session was faster. Negative-return.

An iMessage bridge. Abandoned mid-May 2026 after Anthropic shipped official remote-control. Maintenance cost stopped being worth it.

Two cold-email skills, different angles. Both shipped to test, both pulled when response rates couldn't beat a hand-written first email. Outreach text turns out to be a much harder rubric position than internal text.

A pack that admits what it removed is more trustworthy than a pack that grows monotonically. The first tells you the curator has taste. The second tells you the curator hasn't said no to anything yet.

The premium pattern, in case you want to roll your own

The pack enforces an 18-item checklist on every skill. The short version: versioned frontmatter (version, last_verified), a composes_with block naming upstream and downstream skills, a description with five or more trigger phrases plus a "do not use for" exclusion, a references/ folder with dated research, a scripts/ folder with a stdlib-only Python scorer, an examples/01-starter/ directory with a reproducible quality-check, a rubric.yml listing measurable thresholds, at least 60% of rubric items auto-checked by Python, a CHANGELOG with dated entries, and a SKILL.md whose prose passes the humanizer docs-mode audit (zero AI-tell words).

Fourteen out of eighteen and the skill ships at the $29 tier. All eighteen and it would comfortably ship at $99. The pack publishes the audit output as audit.txt so you can verify each skill yourself.

How to install in 47 seconds

Buy the pack. You get a zip with one folder per skill. Unzip into ~/.claude/skills/. Restart your Claude Code session. The skills appear in the picker automatically. Type one of the trigger phrases listed in any skill's description and the skill fires.

That's the whole install. No package manager, no pip install, no API keys unless you're installing a skill that wraps an external service. Those skills come with .env.example files that name exactly what's required, which is the only configuration step in the entire flow and only fires for the two or three skills in the pack that talk to outside services like Stripe or the Brave Search API.

If you want to skip the 12-hour evaluation weekend, the pack is at skillshelf.co. $29 during launch, going to $99 after the first hundred buyers. One zip, one unzip, 14-day refund if you don't want it.