A complete, opinionated library of Claude Skills covering the full lifecycle of building, launching, running, and growing a brand and a website.
59 stack-agnostic skills covering brand, design, content, SEO, dev, ops, growth, and research. Includes an Ahrefs MCP-powered SEO audit suite. Use them on Next.js, WordPress, Shopify, Webflow, plain HTML, or anything else.
- What are Claude Skills?
- What is in this library
- Getting started
- Quick example
- How they compose
- The 59-skill catalog
- Recommended MCPs
- Authoring conventions
- Repository structure
- Contributing
- Resources
- License
Claude Skills are reusable capability packages that teach Claude how to handle a specific kind of task with a consistent framework, vocabulary, and output format. Each skill is a folder containing a SKILL.md (instructions plus YAML metadata) and optional reference files (templates, checklists, worked examples). Claude loads a skill automatically when a user request matches the skill's description.
Skills work across Claude.ai, Claude Code, and the Anthropic API. Once you write a skill, it is portable across all three.
For the official deep dive, see Anthropic's Agent Skills documentation.
This is not a curated list of other people's skills. It is a single, opinionated library where every skill follows the same structure and conventions, so the skills compose cleanly across a real project lifecycle.
What you get:
- 59 skills across 13 categories, every one with a complete
SKILL.mdand at least one reference file - 75 reference files (templates, checklists, decision matrices, worked examples)
- Stack-agnostic. Works on any web stack. The only named-tool exception is the SEO audit suite, which assumes the Ahrefs MCP.
- Future-proof. Principles over tools. Stable concepts over trending techniques. References to durable specs (W3C, WHATWG, Schema.org, MDN, NN/g, WCAG) over content that ages with each algorithm update.
- Uniform structure. Every skill uses the same section order, the same tone, and the same authoring conventions. Predictable in, predictable out.
- Composable. Skills reference each other.
creative-briefpoints tobrand-voice.incident-responsepoints tomonitoring-and-alerting. Each skill's "When NOT to use" tells you which sibling fits your adjacent work.
Highlight categories: brand strategy, design systems, content production, full SEO suite, frontend dev, accessibility, performance, QA, launch and incident ops, growth and CRO, UX research, plus a meta-skill that teaches you to write your own.
Skills install in three different places depending on where you use Claude. Pick the platform that matches your workflow.
If your Claude.ai plan supports custom Skills:
- Go to Settings → Capabilities → Skills.
- Upload the skill folder you want as a
.zip(one zip per skill folder containingSKILL.mdand thereferences/subfolder). - Enable the skill in the chat interface.
Claude will load the skill automatically when your request matches its description.
For current plan availability and the exact upload UI, see Anthropic's Skills user guide.
Skills are first-class citizens in Claude Code. Drop them into your skills directory and Claude Code picks them up automatically.
User-level skills (available in every project):
# macOS / Linux
mkdir -p ~/.claude/skills
cp -r skills/* ~/.claude/skills/
# Windows (PowerShell)
New-Item -ItemType Directory -Force -Path "$HOME\.claude\skills"
Copy-Item -Recurse skills\* "$HOME\.claude\skills\"Project-level skills (available only in a specific project):
mkdir -p .claude/skills
cp -r path/to/this-repo/skills/* .claude/skills/Start (or restart) Claude Code. Skills load automatically.
For exact current paths and config flags, see the Claude Code documentation.
Use Skills programmatically by referencing them in your API calls. Skills must first be uploaded to your workspace (via the Console or API), then referenced by ID when creating messages.
For the current API surface, request format, and limits, see the Agent Skills API documentation.
You do not have to install all 59. Pick the categories that match your work. The library is modular: each skill stands on its own.
Once installed, skills trigger automatically based on your request. You do not have to name the skill or change how you talk to Claude.
You ask:
"Our organic traffic dropped 30% last week. Help me figure out why."
What happens:
Claude recognizes the request matches seo-traffic-diagnosis, loads the skill, and walks through its 5-layer root cause framework: confirm the change is real → localize the change → page-level analysis → technical analysis → external analysis. By the end, you have a hypothesis statement, evidence, and an action plan, structured the same way every time.
Other natural triggers:
- "Help me write a creative brief" →
creative-brief - "Audit my homepage for SEO" →
seo-onpage - "We need a backlink audit" →
seo-backlink-audit - "Plan our content roadmap for Q3" →
seo-content-gap-auditpluscontent-strategy - "Postmortem template for last night's incident" →
after-action-report - "How do I write my own skill?" →
skill-creation-walkthrough
You can also call a skill explicitly: "Use the seo-audit-orchestration skill to run a full audit on example.com."
The skills compose into a full project flow:
brand-discovery → brand-ideation → brand-identity → brand-style-guide → brand-voice
↓
creative-brief → information-architecture → content-strategy → design-system
↓
seo-keyword → seo-content-audit → content-and-copy → landing-page-copy
↓
seo-onpage → seo-technical → seo-aeo-geo → seo-offpage → seo-competitor
↓
frontend-component-build → accessibility-audit → performance-optimization
↓
code-review-web → qa-testing → security-baseline → launch-runbook
↓
domain-strategy → monitoring-and-alerting → backup-and-disaster-recovery
↓
incident-response → after-action-report
↓
analytics-strategy → cro-optimization → ux-research → usability-testing → journey-mapping
The SEO audit suite (Ahrefs MCP-powered) wraps around the SEO foundation skills:
seo-audit-orchestration
├── seo-site-health-audit
├── seo-backlink-audit
├── seo-keyword-gap-audit
├── seo-content-gap-audit
├── seo-traffic-diagnosis (also runs standalone for incident-style work)
└── seo-rank-tracking (ongoing, feeds the others)
Operations, cross-cutting, and team skills (stakeholder-communication, documentation-strategy, vendor-evaluation, team-onboarding-playbook, dependency-management, cost-optimization, etc.) cut across the lifecycle.
You can also pull individual skills for one-off work. Need just a backlink audit? Use seo-backlink-audit. Need to write a creative brief? Use creative-brief. Each skill stands on its own.
All 59 skills are shipped. Each has a complete SKILL.md plus at least one reference file (template, checklist, or playbook).
| # | Skill | What it does |
|---|---|---|
| 1 | brand-discovery |
Audience research, competitive scan, positioning territory exploration |
| 2 | creative-brief |
Project briefs that align stakeholders before work starts |
| 3 | information-architecture |
Sitemap, navigation, URL structure, content types, taxonomy |
| 4 | content-strategy |
Editorial strategy, content calendar, topical authority planning |
| # | Skill | What it does |
|---|---|---|
| 5 | brand-ideation |
Naming, positioning territories, mood directions, narrative angles |
| 6 | brand-identity |
Logo system, color, typography, imagery, iconography, motion |
| 7 | brand-style-guide |
The canonical reference document for the full brand system |
| 8 | brand-voice |
Voice attributes, tone shifts, vocabulary, paired-example library |
| # | Skill | What it does |
|---|---|---|
| 9 | design-system |
Component library, design tokens, design system documentation |
| 10 | design-standards |
Production-grade page and component design standards |
| 11 | art-direction |
Photography, illustration, and visual direction for campaigns |
| # | Skill | What it does |
|---|---|---|
| 12 | content-and-copy |
Website copy, blog content, content production frameworks |
| 13 | landing-page-copy |
Landing pages, sales pages, hero-to-CTA flow |
| 14 | email-sequences |
Onboarding flows, lifecycle campaigns, transactional copy |
Tool-agnostic SEO skills. These define the conceptual frameworks. The SEO audit suite below adds the Ahrefs MCP-powered execution layer.
| # | Skill | What it does |
|---|---|---|
| 15 | seo-onpage |
Single-page audits and optimization across 8 dimensions |
| 16 | seo-technical |
Crawlability, indexability, rendering, schema, page experience |
| 17 | seo-keyword |
Discovery, intent classification, clustering, prioritization |
| 18 | seo-competitor |
SERP overlap, content gaps, backlink gaps, technical comparison |
| 19 | seo-offpage |
Link building, digital PR, citations, linkable assets |
| 20 | seo-content-audit |
Keep/update/merge/redirect/delete decisions across a site |
| 21 | seo-aeo-geo |
AI search optimization, llms.txt, extraction-friendly content |
End-to-end SEO audit workflows that pull data from the Ahrefs MCP and produce concrete deliverables. These skills assume the Ahrefs MCP is connected.
| # | Skill | What it does |
|---|---|---|
| 22 | seo-audit-orchestration |
Master orchestrator: sequences the suite, produces a rollup report |
| 23 | seo-backlink-audit |
Profile health, anchor mix, toxic links, reclamation, gap analysis |
| 24 | seo-keyword-gap-audit |
Competitor keyword gaps with opportunity scoring and clustering |
| 25 | seo-content-gap-audit |
Missing topics, thin coverage, outdated content, decay diagnosis |
| 26 | seo-traffic-diagnosis |
Diagnose drops, stalls, or wins via 5-layer root cause analysis |
| 27 | seo-site-health-audit |
Triage Ahrefs Site Audit findings by SEO impact, not severity |
| 28 | seo-rank-tracking |
Setup, baseline, segmentation, alerting, dashboarding |
| # | Skill | What it does |
|---|---|---|
| 29 | pm-spec-writing |
PRDs, user stories, acceptance criteria, dev briefs |
| 30 | roadmap-planning |
Quarterly planning, prioritization, dependency mapping |
| # | Skill | What it does |
|---|---|---|
| 31 | code-review-web |
PR review, build error diagnosis, security and quality checks |
| 32 | frontend-component-build |
Component architecture, props design, accessibility from the start |
| 33 | accessibility-audit |
WCAG compliance audit with remediation plan |
| 34 | performance-optimization |
Core Web Vitals, asset optimization, render performance |
| # | Skill | What it does |
|---|---|---|
| 35 | qa-testing |
Pre-launch QA, regression testing, cross-browser checks |
| # | Skill | What it does |
|---|---|---|
| 36 | launch-runbook |
Go-live runbook, DNS cutover, deploy day procedures |
| 37 | incident-response |
Incident triage, comms, mitigation, escalation |
| 38 | after-action-report |
Post-mortems, retros, learnings documentation |
| 39 | domain-strategy |
DNS architecture, redirects, registrars, multi-domain portfolios |
| 40 | monitoring-and-alerting |
SLO design, uptime checks, alert routing, on-call rotations |
| 41 | backup-and-disaster-recovery |
RPO/RTO targets, backup strategy, restoration drills |
| 42 | security-baseline |
HTTPS, security headers, CSP, secrets management, vulnerability scans |
| 43 | email-deliverability |
DMARC, SPF, DKIM, sender reputation, deliverability monitoring |
| 44 | media-asset-management |
Image pipelines, video hosting, asset libraries, format selection |
| # | Skill | What it does |
|---|---|---|
| 45 | analytics-strategy |
Measurement frameworks, dashboard design, event taxonomy |
| 46 | cro-optimization |
Hypothesis-driven testing, conversion optimization |
| # | Skill | What it does |
|---|---|---|
| 47 | ux-research |
Research planning, user interviews, qualitative synthesis |
| 48 | usability-testing |
Test design, moderation, findings reports |
| 49 | journey-mapping |
Customer journey maps, service blueprints, friction analysis |
| # | Skill | What it does |
|---|---|---|
| 50 | form-strategy |
Form design, validation patterns, spam prevention, conversion tuning |
| 51 | content-migration |
Platform migrations with SEO equity preservation |
| 52 | internationalization |
Locale strategy, hreflang, translation workflow, RTL design |
| 53 | dependency-management |
Package updates, security patches, lockfile hygiene |
| 54 | cost-optimization |
Infrastructure spend audits, rightsizing, contract negotiation |
| # | Skill | What it does |
|---|---|---|
| 55 | stakeholder-communication |
Status updates, exec readouts, project communications |
| 56 | documentation-strategy |
Documentation systems, what to document, maintenance cadence |
| 57 | vendor-evaluation |
Tool and vendor selection using a structured rubric |
| 58 | team-onboarding-playbook |
30-60-90 onboarding plans for new hires and contractors |
| 59 | skill-creation-walkthrough |
The meta-skill: how to write your own custom skills |
Skills compose best when Claude has live access to your data and tools. Model Context Protocol (MCP) servers provide that bridge. The skills in this library work without any MCPs, but pair them with the right ones and they go from "frameworks Claude follows" to "workflows Claude executes against your real systems."
Below is the MCP shortlist by skill area. None of these are required (except the Ahrefs MCP for the SEO audit suite). All are categorical recommendations: where multiple options exist for the same job, pick the one that fits your stack.
The SEO audit suite (skills 22-28) is built around the Ahrefs MCP. The foundation SEO skills (15-21) work with any equivalent.
- Ahrefs MCP - referenced explicitly by
seo-audit-orchestrationand the 6 audit suite skills (backlink, keyword gap, content gap, traffic, site health, rank tracking) - DataForSEO MCP - alternative for SERP, keyword, and backlink data; useful as a complement to Ahrefs for cross-validation
- Google Search Console MCP - free, official Google data; essential for
seo-traffic-diagnosisand any audit that needs ground-truth click and impression data - PageSpeed Insights MCP - free, paired with
performance-optimizationandseo-site-health-auditfor Core Web Vitals field data
- GitHub MCP - paired with
code-review-web,pm-spec-writing,roadmap-planning,incident-response. Lets Claude read PRs, file issues, search code, and reference real commits. - Filesystem MCP - local file and code operations; pairs with most dev and content skills
- Sentry MCP - paired with
monitoring-and-alertingandincident-response. Real error data turns generic incident frameworks into specific diagnoses.
- Cloudflare MCP - paired with
domain-strategy,security-baseline,performance-optimization. DNS records, redirects, page rules, security headers. - Vercel MCP - paired with
launch-runbookandincident-response. Deployments, env vars, build logs. - Supabase MCP - paired with
code-review-web,pm-spec-writing,backup-and-disaster-recovery. Schema, queries, edge functions.
- PostHog MCP - paired with
analytics-strategy,cro-optimization,journey-mapping. Event taxonomy review and funnel analysis grounded in real data. - Datadog MCP - paired with
monitoring-and-alerting,incident-response. SLO design and alert routing against actual metrics.
- Slack MCP - paired with
incident-response,stakeholder-communication,after-action-report. Read channel context, draft updates, post incident comms. - Linear MCP (or Jira MCP) - paired with
pm-spec-writing,roadmap-planning. Spec writing against the actual issue tracker, not a generic template.
- Web search (built into Claude in most environments) - paired with
brand-discovery,seo-keyword,seo-competitor,ux-research - Tavily MCP or Brave Search MCP - alternatives for deeper research workflows
- modelcontextprotocol.io/servers - the canonical directory of MCP servers
- The Connectors directory inside Claude.ai (Settings → Connectors)
claude mcp addin Claude Code for direct installation- Vendor websites for first-party servers (most major SaaS tools now ship official MCPs)
If a skill in this library would benefit from a tool integration that does not yet exist, the MCP documentation walks through building one. The seo-audit-orchestration skill is a worked example of how to design a skill suite around a specific MCP's capabilities.
Every skill follows the same structure. See SKILL_AUTHORING.md for the full spec.
Highlights:
- Stack-agnostic. No specific framework versions in SKILL.md. Stack-specific patterns go in reference files. The Ahrefs-powered audit suite is the single named-tool exception.
- Future-proof. Reference durable specs (W3C, WHATWG, Schema.org, MDN, NN/g, WCAG). Avoid trend pieces.
- Uniform structure. Every SKILL.md has the same section order: When to use, When NOT to use, Required inputs, The framework, Workflow, Failure patterns, Output format, Reference files.
- Tight length. SKILL.md under 250 lines. References under 400.
- Punchy voice. Short sentences. Concrete examples beat abstract advice.
skills/
skill-name/
SKILL.md
references/
template.md
checklist.md
example.md
SKILL_AUTHORING.md (the authoring guide)
CONTRIBUTING.md (how to contribute)
MAPPING.md (origin notes for skills ported from existing work)
README.md (this file)
LICENSE (MIT)
Contributions are welcome. Whether you want to fix a typo, add a reference file, or propose an entirely new skill, the bar is the same: follow the uniform structure, keep the voice consistent, and prove the skill earns its place.
See CONTRIBUTING.md for the full process.
The fastest path: use the skill-creation-walkthrough skill itself. It teaches the same authoring discipline used across all 59 skills, with worked examples and a blank template.
- Agent Skills overview - The canonical reference
- Anthropic engineering blog on Skills - Background on the design
- Claude Code documentation - Where most of these skills will run
- Anthropic API reference - For programmatic use
- Anthropic's official skills repository - Examples and primitives published by Anthropic
- Awesome Claude Skills (Composio) - A curated index of community skills
- Model Context Protocol (MCP) - The protocol behind the Ahrefs MCP and other tool integrations referenced in this library
- WCAG quick reference - Accessibility standard cited by the accessibility audit and design skills
- Schema.org - Structured data vocabulary cited across the SEO suite
MIT. Use it. Fork it. Ship things with it.