[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"extension-skill-rampstackco-product-analytics-setup-zh-CN":3,"guides-for-rampstackco-product-analytics-setup":1994,"similar-k176622z7ymqaebhhgn14xxcas86ncgj-zh-CN":1995},{"_creationTime":4,"_id":5,"children":6,"community":7,"display":9,"evaluation":15,"identity":247,"isFallback":239,"parentExtension":253,"providers":254,"relations":259,"repo":261,"tags":1991,"workflow":1992},1778696113180.8228,"k176622z7ymqaebhhgn14xxcas86ncgj",[],{"reviewCount":8},0,{"description":10,"installMethods":11,"name":13,"sourceUrl":14},"How to actually instrument product analytics correctly. Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts. Triggers on product analytics setup, event taxonomy, tracking plan, instrumentation, schema versioning, North Star metric, retention cohorts, funnel design, naming conventions, instrument new feature, audit existing analytics, dashboard reconciliation, instrumentation debt, Mixpanel setup, Amplitude setup, PostHog setup, warehouse-native analytics. Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted.",{"claudeCode":12},"rampstackco/claude-skills","Product Analytics Setup","https://github.com/rampstackco/claude-skills",{"_creationTime":16,"_id":17,"extensionId":5,"locale":18,"result":19,"trustSignals":230,"workflow":245},1778697446310.648,"kn738znzja1a8qkqcs9xj555t986ng5r","en",{"checks":20,"evaluatedAt":192,"extensionSummary":193,"features":194,"nonGoals":201,"practices":206,"prerequisites":210,"promptVersionExtension":211,"promptVersionScoring":212,"purpose":213,"rationale":214,"score":215,"summary":216,"tags":217,"targetMarket":223,"tier":224,"useCases":225},[21,26,29,32,36,39,44,48,51,54,58,62,65,69,72,75,78,81,84,87,91,95,99,103,107,110,113,116,120,123,126,129,132,135,138,142,146,150,153,157,160,163,166,169,173,176,179,182,185,189],{"category":22,"check":23,"severity":24,"summary":25},"Practical Utility","Problem relevance","pass","The description clearly names the user problem of correctly instrumenting product analytics and lists specific trigger scenarios.",{"category":22,"check":27,"severity":24,"summary":28},"Unique selling proposition","The skill offers a systematic, disciplined approach to product analytics instrumentation, going beyond basic LLM capabilities by providing detailed frameworks, rules, and best practices.",{"category":22,"check":30,"severity":24,"summary":31},"Production readiness","The skill's detailed explanations, reference files, and comprehensive coverage of the instrumentation lifecycle indicate it is ready for production use.",{"category":33,"check":34,"severity":24,"summary":35},"Scope","Single responsibility principle","The skill focuses solely on the execution of product analytics instrumentation, clearly distinguishing itself from strategy, experimentation, or platform selection skills.",{"category":33,"check":37,"severity":24,"summary":38},"Description quality","The displayed description accurately and comprehensively reflects the skill's content and scope, detailing the specific aspects of product analytics instrumentation covered.",{"category":40,"check":41,"severity":42,"summary":43},"Invocation","Scoped tools","not_applicable","This is a skill, not a tool-based extension, so it does not expose individual tools with verb-noun names.",{"category":45,"check":46,"severity":42,"summary":47},"Documentation","Configuration & parameter reference","The skill does not appear to have configurable parameters or external configurations beyond what is described in the SKILL.md.",{"category":33,"check":49,"severity":42,"summary":50},"Tool naming","This is a skill, not a tool-based extension, so it does not have user-facing tool names to evaluate.",{"category":33,"check":52,"severity":42,"summary":53},"Minimal I/O surface","As a skill, it does not expose explicit tools with parameter schemas or response shapes in the same way as a tool-based extension.",{"category":55,"check":56,"severity":24,"summary":57},"License","License usability","The extension is explicitly licensed under MIT, as indicated by the LICENSE file, allowing for broad usability.",{"category":59,"check":60,"severity":24,"summary":61},"Maintenance","Commit recency","The last commit was on May 10, 2026, which is within the last 3 months.",{"category":59,"check":63,"severity":42,"summary":64},"Dependency Management","The extension does not appear to use any third-party dependencies that require management.",{"category":66,"check":67,"severity":24,"summary":68},"Security","Secret Management","The skill focuses on documentation and process, and does not appear to handle or expose any secrets.",{"category":66,"check":70,"severity":24,"summary":71},"Injection","The skill provides detailed frameworks and instructions, but does not execute code or load external data in a way that poses an injection risk.",{"category":66,"check":73,"severity":24,"summary":74},"Transitive Supply-Chain Grenades","The skill does not fetch external files or code at runtime; all content is bundled within the repository.",{"category":66,"check":76,"severity":24,"summary":77},"Sandbox Isolation","The skill provides guidance and does not perform file system operations or other actions that would require sandbox isolation.",{"category":66,"check":79,"severity":24,"summary":80},"Sandbox escape primitives","The skill does not involve code execution or scripts that could contain sandbox-escape primitives.",{"category":66,"check":82,"severity":24,"summary":83},"Data Exfiltration","The skill provides documentation and frameworks, and does not include any instructions for reading or submitting confidential data.",{"category":66,"check":85,"severity":24,"summary":86},"Hidden Text Tricks","The bundled content is free of hidden-steering tricks, and descriptions use clean ASCII and expected Unicode.",{"category":88,"check":89,"severity":24,"summary":90},"Hooks","Opaque code execution","The skill's content is plain, readable prose and does not involve obfuscated code execution.",{"category":92,"check":93,"severity":24,"summary":94},"Portability","Structural Assumption","The skill provides documentation and frameworks, not code that makes structural assumptions about user projects.",{"category":96,"check":97,"severity":24,"summary":98},"Trust","Issues Attention","There are 0 open issues and 0 closed issues in the last 90 days, indicating low recent activity but no negative signals.",{"category":100,"check":101,"severity":24,"summary":102},"Versioning","Release Management","The SKILL.md frontmatter includes a 'name' and 'version' is implied by the directory structure, allowing for clear version detection.",{"category":104,"check":105,"severity":42,"summary":106},"Code Execution","Validation","This skill provides documentation and guidance, not executable code that requires input validation.",{"category":66,"check":108,"severity":24,"summary":109},"Unguarded Destructive Operations","The skill provides guidance and does not perform any destructive operations.",{"category":104,"check":111,"severity":42,"summary":112},"Error Handling","As a documentation-heavy skill, it does not have executable code paths with user-facing errors.",{"category":104,"check":114,"severity":42,"summary":115},"Logging","The skill does not perform actions that would require local audit logging.",{"category":117,"check":118,"severity":24,"summary":119},"Compliance","GDPR","The skill focuses on analytics methodology and does not operate on personal data.",{"category":117,"check":121,"severity":24,"summary":122},"Target market","The skill provides general product analytics best practices applicable globally, with no regional restrictions.",{"category":92,"check":124,"severity":24,"summary":125},"Runtime stability","The skill is documentation-based and does not make assumptions about specific editors, shells, or runtimes.",{"category":45,"check":127,"severity":24,"summary":128},"README","The README exists, is comprehensive, and clearly states the library's purpose and structure.",{"category":33,"check":130,"severity":42,"summary":131},"Tool surface size","This is a skill, not a tool-based extension, so it does not expose tools or commands.",{"category":40,"check":133,"severity":42,"summary":134},"Overlapping near-synonym tools","This is a skill, not a tool-based extension, so it does not have overlapping tools.",{"category":45,"check":136,"severity":24,"summary":137},"Phantom features","All features described in the README and SKILL.md have corresponding implementations or detailed explanations within the skill's documentation.",{"category":139,"check":140,"severity":24,"summary":141},"Install","Installation instruction","The README provides clear, multi-platform installation instructions for Claude.ai, Claude Code, and the API, including quick examples.",{"category":143,"check":144,"severity":42,"summary":145},"Errors","Actionable error messages","As a documentation-based skill, it does not have user-facing error paths.",{"category":147,"check":148,"severity":42,"summary":149},"Execution","Pinned dependencies","The skill does not use third-party dependencies that require pinning.",{"category":33,"check":151,"severity":42,"summary":152},"Dry-run preview","The skill provides guidance and documentation, not state-changing commands requiring a dry-run mode.",{"category":154,"check":155,"severity":42,"summary":156},"Protocol","Idempotent retry & timeouts","The skill does not involve remote calls or state-changing operations that would require idempotency or timeouts.",{"category":117,"check":158,"severity":24,"summary":159},"Telemetry opt-in","The skill provides documentation and does not emit telemetry.",{"category":40,"check":161,"severity":24,"summary":162},"Precise Purpose","The SKILL.md clearly defines the skill's purpose regarding product analytics instrumentation execution and explicitly states its non-goals.",{"category":40,"check":164,"severity":24,"summary":165},"Concise Frontmatter","The SKILL.md frontmatter is concise, self-contained, and accurately summarizes the core capability and trigger phrases.",{"category":45,"check":167,"severity":24,"summary":168},"Concise Body","The SKILL.md body is well-structured, under the line limit, and effectively delegates deeper material to reference files.",{"category":170,"check":171,"severity":24,"summary":172},"Context","Progressive Disclosure","The skill uses relative paths to link to separate reference files for detailed procedures and templates, demonstrating effective progressive disclosure.",{"category":170,"check":174,"severity":42,"summary":175},"Forked exploration","This skill provides instructional content and does not involve deep exploration or code review that would require forked context.",{"category":22,"check":177,"severity":24,"summary":178},"Usage examples","The SKILL.md includes numerous detailed examples within reference files that plausibly demonstrate the claimed behaviors and instrumentation patterns.",{"category":22,"check":180,"severity":24,"summary":181},"Edge cases","The skill addresses failure modes and limitations, documenting observable symptoms and recovery steps in reference files.",{"category":104,"check":183,"severity":42,"summary":184},"Tool Fallback","This skill does not reference external tools like MCPs and thus has no fallback path to evaluate.",{"category":186,"check":187,"severity":24,"summary":188},"Safety","Halt on unexpected state","The skill's documentation emphasizes discipline and adherence to standards, implicitly guiding users to halt on unexpected states rather than proceeding blindly.",{"category":92,"check":190,"severity":24,"summary":191},"Cross-skill coupling","The skill is self-contained and clearly delineates its scope, referencing related skills like 'analytics-strategy' explicitly rather than assuming their presence.",1778697446211,"This skill provides a detailed playbook and reference materials for correctly instrumenting product analytics, covering event taxonomy, property design, naming conventions, schema versioning, funnel design, cohort definitions, retention measurement, North Star metric selection, dashboard hygiene, and managing instrumentation debt.",[195,196,197,198,199,200],"Detailed guidance on event taxonomy design and naming conventions","Best practices for property design (event-level vs user-level) and type discipline","Frameworks for schema versioning and migration patterns","Templates and rules for designing effective funnels and cohort definitions","Guidance on North Star metric selection and supporting metrics","Principles for dashboard hygiene and managing instrumentation debt",[202,203,204,205],"Analytics strategy and measurement framework selection","Experimentation result interpretation","Paid media analytics or platform decisions","Specific tool setup (Mixpanel, Amplitude, etc.) beyond general principles",[207,208,209],"Data Quality","Instrumentation Discipline","Schema Management",[],"3.0.0","4.4.0","To guide users in setting up and maintaining accurate, trustworthy product analytics instrumentation that supports strategic decision-making.","The skill is exceptionally well-documented, comprehensive, and adheres to all best practices for skills development. The low issue count and MIT license contribute to a high trust score.",99,"A comprehensive and highly disciplined guide to correct product analytics instrumentation, covering all key aspects from taxonomy to maintenance.",[218,219,220,221,222],"product-analytics","instrumentation","data-quality","reporting","saas","global","verified",[226,227,228,229],"Setting up product analytics instrumentation from scratch","Auditing and improving an existing, untrustworthy analytics setup","Designing instrumentation for new features","Establishing and enforcing data quality standards for product analytics",{"codeQuality":231,"collectedAt":233,"documentation":234,"maintenance":237,"security":242,"testCoverage":244},{"hasLockfile":232},false,1778697432014,{"descriptionLength":235,"readmeSize":236},821,59736,{"closedIssues90d":8,"forks":238,"hasChangelog":239,"openIssues90d":8,"pushedAt":240,"stars":241},17,true,1778452822000,168,{"hasNpmPackage":232,"license":243,"smitheryVerified":232},"MIT",{"hasCi":239,"hasTests":232},{"updatedAt":246},1778697446310,{"basePath":248,"githubOwner":249,"githubRepo":250,"locale":18,"slug":251,"type":252},"skills/product-analytics-setup","rampstackco","claude-skills","product-analytics-setup","skill",null,{"evaluate":255,"extract":257},{"promptVersionExtension":211,"promptVersionScoring":212,"score":215,"tags":256,"targetMarket":223,"tier":224},[218,219,220,221,222],{"commitSha":258,"license":243},"HEAD",{"repoId":260},"kd7bebccrrd1xf6w868aggftrd86m86v",{"_creationTime":262,"_id":260,"identity":263,"providers":264,"workflow":1987},1778696105594.453,{"githubOwner":249,"githubRepo":250,"sourceUrl":14},{"classify":265,"discover":1964,"github":1967},{"commitSha":258,"extensions":266},[267,285,307,329,339,365,375,389,399,425,497,509,521,533,545,557,583,609,623,649,661,685,711,721,747,773,785,795,808,822,832,856,866,880,894,920,930,940,968,978,990,1012,1033,1055,1077,1105,1115,1129,1155,1165,1177,1199,1225,1235,1245,1269,1281,1291,1317,1339,1365,1375,1385,1411,1437,1462,1483,1497,1525,1539,1560,1586,1614,1624,1650,1659,1685,1695,1707,1717,1727,1739,1750,1760,1772,1782,1794,1807,1817,1827,1838,1848,1862,1872,1882,1908,1918,1944,1954],{"basePath":268,"description":269,"displayName":270,"installMethods":271,"rationale":272,"selectedPaths":273,"source":284,"sourceLanguage":18,"type":252},"skills/accessibility-audit","Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.","accessibility-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/accessibility-audit/SKILL.md",[274,277,280,282],{"path":275,"priority":276},"SKILL.md","mandatory",{"path":278,"priority":279},"references/aria-patterns.md","medium",{"path":281,"priority":279},"references/audit-report-template.md",{"path":283,"priority":279},"references/wcag-quick-reference.md","rule",{"basePath":286,"description":287,"displayName":288,"installMethods":289,"rationale":290,"selectedPaths":291,"source":284,"sourceLanguage":18,"type":252},"skills/ads-creative-development","How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.","ads-creative-development",{"claudeCode":12},"SKILL.md frontmatter at skills/ads-creative-development/SKILL.md",[292,293,295,297,299,301,303,305],{"path":275,"priority":276},{"path":294,"priority":279},"references/brand-voice-performance-balance.md",{"path":296,"priority":279},"references/creative-variation-templates.md",{"path":298,"priority":279},"references/fatigue-detection-checklist.md",{"path":300,"priority":279},"references/format-decision-matrix.md",{"path":302,"priority":279},"references/hook-pattern-library.md",{"path":304,"priority":279},"references/platform-creative-norms.md",{"path":306,"priority":279},"references/testing-cadence-playbook.md",{"basePath":308,"description":309,"displayName":310,"installMethods":311,"rationale":312,"selectedPaths":313,"source":284,"sourceLanguage":18,"type":252},"skills/ads-performance-analytics","How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.","ads-performance-analytics",{"claudeCode":12},"SKILL.md frontmatter at skills/ads-performance-analytics/SKILL.md",[314,315,317,319,321,323,325,327],{"path":275,"priority":276},{"path":316,"priority":279},"references/attribution-model-comparison.md",{"path":318,"priority":279},"references/cohort-analysis-templates.md",{"path":320,"priority":279},"references/common-interpretation-failures.md",{"path":322,"priority":279},"references/dashboard-reconciliation-patterns.md",{"path":324,"priority":279},"references/incrementality-testing-playbook.md",{"path":326,"priority":279},"references/metric-definitions-glossary.md",{"path":328,"priority":279},"references/platform-reporting-quirks.md",{"basePath":330,"description":331,"displayName":332,"installMethods":333,"rationale":334,"selectedPaths":335,"source":284,"sourceLanguage":18,"type":252},"skills/after-action-report","Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.","after-action-report",{"claudeCode":12},"SKILL.md frontmatter at skills/after-action-report/SKILL.md",[336,337],{"path":275,"priority":276},{"path":338,"priority":279},"references/aar-template.md",{"basePath":340,"description":341,"displayName":342,"installMethods":343,"rationale":344,"selectedPaths":345,"source":284,"sourceLanguage":18,"type":252},"skills/ai-content-collaboration","How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.","ai-content-collaboration",{"claudeCode":12},"SKILL.md frontmatter at skills/ai-content-collaboration/SKILL.md",[346,347,349,351,353,355,357,359,361,363],{"path":275,"priority":276},{"path":348,"priority":279},"references/ai-participation-boundaries.md",{"path":350,"priority":279},"references/ai-slop-detection-and-avoidance.md",{"path":352,"priority":279},"references/common-collaboration-failures.md",{"path":354,"priority":279},"references/disclosure-and-transparency-patterns.md",{"path":356,"priority":279},"references/ethics-and-intellectual-honesty.md",{"path":358,"priority":279},"references/hybrid-workflow-patterns.md",{"path":360,"priority":279},"references/quality-calibration-with-ai-in-loop.md",{"path":362,"priority":279},"references/team-training-and-calibration.md",{"path":364,"priority":279},"references/voice-ownership-preservation.md",{"basePath":366,"description":367,"displayName":368,"installMethods":369,"rationale":370,"selectedPaths":371,"source":284,"sourceLanguage":18,"type":252},"skills/analytics-strategy","Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.","analytics-strategy",{"claudeCode":12},"SKILL.md frontmatter at skills/analytics-strategy/SKILL.md",[372,373],{"path":275,"priority":276},{"path":374,"priority":279},"references/event-taxonomy-template.md",{"basePath":376,"description":377,"displayName":378,"installMethods":379,"rationale":380,"selectedPaths":381,"source":284,"sourceLanguage":18,"type":252},"skills/art-direction","Direct visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, write a creative direction document, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables.","art-direction",{"claudeCode":12},"SKILL.md frontmatter at skills/art-direction/SKILL.md",[382,383,385,387],{"path":275,"priority":276},{"path":384,"priority":279},"references/creative-brief-template.md",{"path":386,"priority":279},"references/illustration-brief.md",{"path":388,"priority":279},"references/photo-shoot-brief.md",{"basePath":390,"description":391,"displayName":392,"installMethods":393,"rationale":394,"selectedPaths":395,"source":284,"sourceLanguage":18,"type":252},"skills/backup-and-disaster-recovery","Plan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.","backup-and-disaster-recovery",{"claudeCode":12},"SKILL.md frontmatter at skills/backup-and-disaster-recovery/SKILL.md",[396,397],{"path":275,"priority":276},{"path":398,"priority":279},"references/restore-runbook-template.md",{"basePath":400,"description":401,"displayName":402,"installMethods":403,"rationale":404,"selectedPaths":405,"source":284,"sourceLanguage":18,"type":252},"skills/beta-program-management","Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional feedback loops, clear graduation criteria). Triggers on beta program, alpha test, beta cohort, beta participant, beta feedback, beta to GA decision, design partner, early access program, closed beta, open beta, RC release. Also triggers when a feature is approaching launch and the team needs structured pre-GA validation, when prior betas produced noise rather than signal, or when the team has soft-launched before but wants more structured feedback this time.","beta-program-management",{"claudeCode":12},"SKILL.md frontmatter at skills/beta-program-management/SKILL.md",[406,407,409,411,413,415,417,419,421,423],{"path":275,"priority":276},{"path":408,"priority":279},"references/beta-onboarding-templates.md",{"path":410,"priority":279},"references/beta-to-ga-graduation-criteria.md",{"path":412,"priority":279},"references/beta-type-decisions.md",{"path":414,"priority":279},"references/beta-wind-down-communication.md",{"path":416,"priority":279},"references/cohort-sizing-patterns.md",{"path":418,"priority":279},"references/common-beta-failures.md",{"path":420,"priority":279},"references/feedback-collection-patterns.md",{"path":422,"priority":279},"references/mid-beta-triage-and-iteration.md",{"path":424,"priority":279},"references/participant-selection-criteria.md",{"basePath":426,"description":427,"displayName":428,"installMethods":429,"rationale":430,"selectedPaths":431,"source":284,"sourceLanguage":18,"type":252},"skills/brand-archetype-system","Apply pre-composed aesthetic archetype defaults to jumpstart brand design work covering color, typography, layout, voice, and imagery direction. Use this skill whenever the user wants a starting point for brand visual and verbal direction, references a brand they want to design near (for example 'something like Stripe' or 'editorial like Linear'), needs to converge faster from many directions to one, or wants known-good defaults for a specific industry vertical. Triggers on archetype, design archetype, brand archetype, near to (brand), in the style of, similar aesthetic, design starting point, brand template, vertical-typical, industry-typical. Also triggers when the user has a brief and wants to map it to a known aesthetic family rather than design from first principles.","brand-archetype-system",{"claudeCode":12},"SKILL.md frontmatter at skills/brand-archetype-system/SKILL.md",[432,433,435,437,439,441,443,445,447,449,451,453,455,457,459,461,463,465,467,469,471,473,475,477,479,481,483,485,487,489,491,493,495],{"path":275,"priority":276},{"path":434,"priority":279},"references/00-archetype-system-overview.md",{"path":436,"priority":279},"references/01-how-to-apply-an-archetype.md",{"path":438,"priority":279},"references/by-vertical/01-b2b-saas-developer-tools.md",{"path":440,"priority":279},"references/by-vertical/02-b2b-saas-business-productivity.md",{"path":442,"priority":279},"references/by-vertical/03-b2b-saas-marketing-sales.md",{"path":444,"priority":279},"references/by-vertical/04-b2b-saas-data-analytics.md",{"path":446,"priority":279},"references/by-vertical/05-fintech-consumer.md",{"path":448,"priority":279},"references/by-vertical/06-fintech-enterprise.md",{"path":450,"priority":279},"references/by-vertical/07-dtc-fashion.md",{"path":452,"priority":279},"references/by-vertical/08-dtc-beauty.md",{"path":454,"priority":279},"references/by-vertical/09-dtc-home-lifestyle.md",{"path":456,"priority":279},"references/by-vertical/10-dtc-food-beverage.md",{"path":458,"priority":279},"references/by-vertical/11-consumer-health-wellness.md",{"path":460,"priority":279},"references/by-vertical/12-hospitality-travel.md",{"path":462,"priority":279},"references/by-vertical/13-media-publishing.md",{"path":464,"priority":279},"references/by-vertical/14-edtech.md",{"path":466,"priority":279},"references/by-vertical/15-gaming-entertainment.md",{"path":468,"priority":279},"references/by-vertical/16-marketplace.md",{"path":470,"priority":279},"references/by-vertical/17-crypto-web3.md",{"path":472,"priority":279},"references/by-vertical/18-real-estate-proptech.md",{"path":474,"priority":279},"references/core-archetypes/01-editorial-restrained.md",{"path":476,"priority":279},"references/core-archetypes/02-technical-precise.md",{"path":478,"priority":279},"references/core-archetypes/03-warm-conversational.md",{"path":480,"priority":279},"references/core-archetypes/04-bold-confident.md",{"path":482,"priority":279},"references/core-archetypes/05-playful-energetic.md",{"path":484,"priority":279},"references/core-archetypes/06-luxe-considered.md",{"path":486,"priority":279},"references/core-archetypes/07-clinical-trustworthy.md",{"path":488,"priority":279},"references/core-archetypes/08-rugged-utilitarian.md",{"path":490,"priority":279},"references/core-archetypes/09-retro-nostalgic.md",{"path":492,"priority":279},"references/core-archetypes/10-minimal-essentialist.md",{"path":494,"priority":279},"references/core-archetypes/11-vibrant-saturated.md",{"path":496,"priority":279},"references/core-archetypes/12-documentary-honest.md",{"basePath":498,"description":499,"displayName":500,"installMethods":501,"rationale":502,"selectedPaths":503,"source":284,"sourceLanguage":18,"type":252},"skills/brand-discovery","Run upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration. Use this skill at the very start of a brand or website project when the user needs to understand who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand. Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff. Also triggers when a creative brief is requested but the upstream inputs (audience, competitors, problem space) are not yet clear.","brand-discovery",{"claudeCode":12},"SKILL.md frontmatter at skills/brand-discovery/SKILL.md",[504,505,507],{"path":275,"priority":276},{"path":506,"priority":279},"references/discovery-report-template.md",{"path":508,"priority":279},"references/interview-guide.md",{"basePath":510,"description":511,"displayName":512,"installMethods":513,"rationale":514,"selectedPaths":515,"source":284,"sourceLanguage":18,"type":252},"skills/brand-ideation","Generate, evaluate, and narrow brand concepts during early ideation including positioning territories, naming candidates, mood directions, and narrative angles. Use this skill whenever the user is in the early phase of brand creation, exploring brand directions, brainstorming names, building moodboards, generating positioning options, or trying to choose between multiple brand directions. Triggers on brand ideation, brand concept, naming, brand name, name candidates, positioning, brand positioning, mood board, brand directions, exploring brands, early brand work, brand exploration, brand brainstorm, brand options. Also triggers when the user has multiple half-formed brand ideas and needs help converging on one, even if they do not say 'ideation' explicitly.","brand-ideation",{"claudeCode":12},"SKILL.md frontmatter at skills/brand-ideation/SKILL.md",[516,517,519],{"path":275,"priority":276},{"path":518,"priority":279},"references/ideation-output-template.md",{"path":520,"priority":279},"references/naming-evaluation-rubric.md",{"basePath":522,"description":523,"displayName":524,"installMethods":525,"rationale":526,"selectedPaths":527,"source":284,"sourceLanguage":18,"type":252},"skills/brand-identity","Design or evaluate a brand visual identity system covering logo, color, typography, imagery direction, iconography, and motion principles. Use this skill whenever the user wants to design a logo, build a visual identity, define brand colors, choose brand typography, develop iconography, plan brand imagery, or evaluate an existing identity for cohesion. Triggers on logo design, brand identity, visual identity, brand mark, wordmark, monogram, color palette, brand colors, brand typography, type system, iconography, brand imagery, motion design, brand system, identity system. Also triggers when the user has a brand direction approved and now needs the visual artifacts that express it.","brand-identity",{"claudeCode":12},"SKILL.md frontmatter at skills/brand-identity/SKILL.md",[528,529,531],{"path":275,"priority":276},{"path":530,"priority":279},"references/contrast-and-accessibility.md",{"path":532,"priority":279},"references/identity-system-spec.md",{"basePath":534,"description":535,"displayName":536,"installMethods":537,"rationale":538,"selectedPaths":539,"source":284,"sourceLanguage":18,"type":252},"skills/brand-style-guide","Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style guide for completeness, or produce the artifact that other teams will reference for years. Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference. Also triggers when the brand identity is finished and needs to be documented for handoff to designers, developers, vendors, or future team members.","brand-style-guide",{"claudeCode":12},"SKILL.md frontmatter at skills/brand-style-guide/SKILL.md",[540,541,543],{"path":275,"priority":276},{"path":542,"priority":279},"references/maintenance-playbook.md",{"path":544,"priority":279},"references/style-guide-template.md",{"basePath":546,"description":547,"displayName":548,"installMethods":549,"rationale":550,"selectedPaths":551,"source":284,"sourceLanguage":18,"type":252},"skills/brand-voice","Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples. Use this skill whenever the user wants to define how a brand sounds, write a voice and tone document, audit existing copy for voice consistency, train a team or AI assistant on brand voice, or refine the personality of brand writing. Triggers on brand voice, voice and tone, tone of voice, writing voice, brand personality, copy voice, voice document, voice guidelines, how should we write, voice training, voice audit. Also triggers when the user has copy that 'feels off' and the underlying issue is voice, even if not stated explicitly.","brand-voice",{"claudeCode":12},"SKILL.md frontmatter at skills/brand-voice/SKILL.md",[552,553,555],{"path":275,"priority":276},{"path":554,"priority":279},"references/voice-document-template.md",{"path":556,"priority":279},"references/voice-frameworks.md",{"basePath":558,"description":559,"displayName":560,"installMethods":561,"rationale":562,"selectedPaths":563,"source":284,"sourceLanguage":18,"type":252},"skills/calculator-design","Designing interactive calculators (ROI calculators, pricing estimators, savings projections, mortgage calculators, custom assessments) that deliver real decision-support value while serving as lead magnets and qualified-traffic generators. Honest about vanity-calculator (no real value), lead-trap (hides the answer behind email), and transparent-decision-tool (gives the result and earns the email through tiered value) patterns. Triggers on calculator, ROI calculator, pricing estimator, savings calculator, custom calculator, interactive tool, decision tool, financial calculator. Also triggers when an audience needs a calculation-driven lead magnet, when a vanity calculator is producing leads but no qualified ones, or when a calculator is being scoped for the first time.","calculator-design",{"claudeCode":12},"SKILL.md frontmatter at skills/calculator-design/SKILL.md",[564,565,567,569,571,573,575,577,579,581],{"path":275,"priority":276},{"path":566,"priority":279},"references/calculation-logic-transparency.md",{"path":568,"priority":279},"references/calculator-anti-patterns.md",{"path":570,"priority":279},"references/calculator-investment-criteria.md",{"path":572,"priority":279},"references/common-calculator-failures.md",{"path":574,"priority":279},"references/email-capture-decision-tree.md",{"path":576,"priority":279},"references/input-design-patterns.md",{"path":578,"priority":279},"references/methodology-disclosure-templates.md",{"path":580,"priority":279},"references/result-presentation-patterns.md",{"path":582,"priority":279},"references/tiered-value-structures.md",{"basePath":584,"description":585,"displayName":586,"installMethods":587,"rationale":588,"selectedPaths":589,"source":284,"sourceLanguage":18,"type":252},"skills/chatbot-flow-design","Designing conversational flows for website chatbots and AI agents. Intent recognition architecture, branching logic, fallback handling, escalation to human, conversation analytics. Honest about scripted-bot (rigid trees, fail edge cases), hallucinating-bot (LLM without structure, makes things up), and structured-guided-conversation (LLM-powered with intent architecture and fallback discipline) patterns. Distinguishes chatbot DESIGN (this skill) from chatbot IMPLEMENTATION (engineering and platform work). Triggers on chatbot, conversational AI, AI agent, chat widget, intent design, conversational flow, bot escalation, LLM grounding. Also triggers when a chatbot is hallucinating, when a scripted bot is failing edge cases, or when a chatbot is being scoped for the first time.","chatbot-flow-design",{"claudeCode":12},"SKILL.md frontmatter at skills/chatbot-flow-design/SKILL.md",[590,591,593,595,597,599,601,603,605,607],{"path":275,"priority":276},{"path":592,"priority":279},"references/branching-and-conditional-logic.md",{"path":594,"priority":279},"references/chatbot-anti-patterns.md",{"path":596,"priority":279},"references/chatbot-decision-criteria.md",{"path":598,"priority":279},"references/common-chatbot-failures.md",{"path":600,"priority":279},"references/conversation-analytics-patterns.md",{"path":602,"priority":279},"references/escalation-to-human-patterns.md",{"path":604,"priority":279},"references/fallback-pattern-design.md",{"path":606,"priority":279},"references/intent-architecture-patterns.md",{"path":608,"priority":279},"references/knowledge-base-grounding-patterns.md",{"basePath":610,"description":611,"displayName":612,"installMethods":613,"rationale":614,"selectedPaths":615,"source":284,"sourceLanguage":18,"type":252},"skills/code-review-web","Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.","code-review-web",{"claudeCode":12},"SKILL.md frontmatter at skills/code-review-web/SKILL.md",[616,617,619,621],{"path":275,"priority":276},{"path":618,"priority":279},"references/nextjs-patterns.md",{"path":620,"priority":279},"references/review-template.md",{"path":622,"priority":279},"references/wordpress-headless-patterns.md",{"basePath":624,"description":625,"displayName":626,"installMethods":627,"rationale":628,"selectedPaths":629,"source":284,"sourceLanguage":18,"type":252},"skills/comparison-tool-design","Designing side-by-side comparison tools (plan-compare, product-compare, alternative-compare) that help users decide rather than just listing features. Axis selection, default-comparison logic, recommendation discipline. Honest about feature-list-dump (every feature in a row, no decision support), hidden-recommendation (biased comparison pretending to be neutral), and honest-comparison-with-guidance (genuine comparison plus opinionated recommendation) patterns. Triggers on comparison tool, plan compare, product compare, alternative compare, vs page, decision support tool. Also triggers when conversion through comparison stages is poor, when users are abandoning at the comparison step, or when a comparison tool is being scoped for the first time.","comparison-tool-design",{"claudeCode":12},"SKILL.md frontmatter at skills/comparison-tool-design/SKILL.md",[630,631,633,635,637,639,641,643,645,647],{"path":275,"priority":276},{"path":632,"priority":279},"references/axis-selection-patterns.md",{"path":634,"priority":279},"references/common-comparison-failures.md",{"path":636,"priority":279},"references/comparison-anti-patterns.md",{"path":638,"priority":279},"references/comparison-fatigue-patterns.md",{"path":640,"priority":279},"references/comparison-tool-decision-criteria.md",{"path":642,"priority":279},"references/default-comparison-logic.md",{"path":644,"priority":279},"references/filter-and-toggle-patterns.md",{"path":646,"priority":279},"references/honest-recommendation-discipline.md",{"path":648,"priority":279},"references/recommendation-engine-design.md",{"basePath":650,"description":651,"displayName":652,"installMethods":653,"rationale":654,"selectedPaths":655,"source":284,"sourceLanguage":18,"type":252},"skills/content-and-copy","Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal. Use this skill whenever the user wants to write an article, draft website copy, edit existing content for clarity or voice, write a blog post, or produce general editorial content. Triggers on write a blog post, draft an article, write copy for, edit this, rewrite this, write content, write a guide, draft a how-to, write web copy. Also triggers when content has been outlined and now needs to be written, or when existing content needs voice or clarity edits.","content-and-copy",{"claudeCode":12},"SKILL.md frontmatter at skills/content-and-copy/SKILL.md",[656,657,659],{"path":275,"priority":276},{"path":658,"priority":279},"references/content-brief-template.md",{"path":660,"priority":279},"references/content-edit-checklist.md",{"basePath":662,"description":663,"displayName":664,"installMethods":665,"rationale":666,"selectedPaths":667,"source":284,"sourceLanguage":18,"type":252},"skills/content-brief-authoring","How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both. Per-piece editorial brief: target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria. The middle path between thin briefs (a keyword and a deadline) and thick briefs (a 4-page document nobody reads). Triggers on content brief, brief the writer, brief the article, brief authoring, content brief template, brief audit, per-piece brief, editorial brief, target keyword brief, search intent brief. Also triggers when briefing a human writer or an AI agent on a single content piece.","content-brief-authoring",{"claudeCode":12},"SKILL.md frontmatter at skills/content-brief-authoring/SKILL.md",[668,669,671,673,675,677,679,681,683],{"path":275,"priority":276},{"path":670,"priority":279},"references/brief-governance-patterns.md",{"path":672,"priority":279},"references/brief-templates.md",{"path":674,"priority":279},"references/common-brief-failures.md",{"path":676,"priority":279},"references/entity-coverage-checklist.md",{"path":678,"priority":279},"references/heading-structure-patterns.md",{"path":680,"priority":279},"references/internal-linking-strategy.md",{"path":682,"priority":279},"references/search-intent-classification.md",{"path":684,"priority":279},"references/writer-handoff-protocols.md",{"basePath":686,"description":687,"displayName":688,"installMethods":689,"rationale":690,"selectedPaths":691,"source":284,"sourceLanguage":18,"type":252},"skills/content-distribution","Content distribution as a discipline. Owned channels (newsletter, blog, social), earned channels (PR, syndication, mentions), paid channels (boosted posts, syndication networks), and the channel-fit decisions that distinguish strategic distribution from spam-everywhere. Audience-channel matching, content-channel matching, distribution cadence. Triggers on content distribution, channel strategy for content, owned earned paid channels, content amplification, content promotion, audience-channel matching, content-channel matching, distribution cadence, syndication strategy, organic distribution. Also triggers when content is publishing but reach is low, when the team is distributing on every channel without strategy, or when the content program needs a distribution discipline rather than just publication.","content-distribution",{"claudeCode":12},"SKILL.md frontmatter at skills/content-distribution/SKILL.md",[692,693,695,697,699,701,703,705,707,709],{"path":275,"priority":276},{"path":694,"priority":279},"references/audience-channel-matching.md",{"path":696,"priority":279},"references/channel-taxonomy.md",{"path":698,"priority":279},"references/common-distribution-failures.md",{"path":700,"priority":279},"references/content-channel-matching.md",{"path":702,"priority":279},"references/distribution-cadence-patterns.md",{"path":704,"priority":279},"references/distribution-measurement.md",{"path":706,"priority":279},"references/earned-channel-work.md",{"path":708,"priority":279},"references/owned-channel-discipline.md",{"path":710,"priority":279},"references/paid-promotion-patterns.md",{"basePath":712,"description":713,"displayName":714,"installMethods":715,"rationale":716,"selectedPaths":717,"source":284,"sourceLanguage":18,"type":252},"skills/content-migration","Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations. Use this skill when planning a CMS migration, replatforming, consolidating sites, changing URL structures, or merging content from multiple sources. Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop. Also triggers when planning a launch that involves moving existing content.","content-migration",{"claudeCode":12},"SKILL.md frontmatter at skills/content-migration/SKILL.md",[718,719],{"path":275,"priority":276},{"path":720,"priority":279},"references/migration-runbook.md",{"basePath":722,"description":723,"displayName":724,"installMethods":725,"rationale":726,"selectedPaths":727,"source":284,"sourceLanguage":18,"type":252},"skills/content-refresh-system","Systematic content refresh discipline. Quarterly audits, refresh prioritization (which pieces, when, how deep), refresh-vs-merge-vs-delete decisions, the lifecycle that distinguishes intentional refresh from set-and-forget decay. Builds on the refresh sections of pillar-content-architecture and editorial-qa with a program-level discipline. Triggers on content refresh, content decay, content audit, refresh prioritization, content lifecycle, refresh strategy, traffic decay, ranking drop, content freshness, evergreen content, content maintenance. Also triggers when traffic is eroding silently across an aging content library, when teams cannot decide which pieces to refresh, or when refresh work is happening but the impact is unclear.","content-refresh-system",{"claudeCode":12},"SKILL.md frontmatter at skills/content-refresh-system/SKILL.md",[728,729,731,733,735,737,739,741,743,745],{"path":275,"priority":276},{"path":730,"priority":279},"references/audit-cadence-patterns.md",{"path":732,"priority":279},"references/common-refresh-failures.md",{"path":734,"priority":279},"references/effectiveness-measurement.md",{"path":736,"priority":279},"references/re-promotion-after-refresh.md",{"path":738,"priority":279},"references/refresh-depth-decision.md",{"path":740,"priority":279},"references/refresh-execution-patterns.md",{"path":742,"priority":279},"references/refresh-prioritization-matrix.md",{"path":744,"priority":279},"references/refresh-signals-checklist.md",{"path":746,"priority":279},"references/refresh-vs-merge-vs-delete.md",{"basePath":748,"description":749,"displayName":750,"installMethods":751,"rationale":752,"selectedPaths":753,"source":284,"sourceLanguage":18,"type":252},"skills/content-repurposing","Cross-format content adaptation. Turning one substantial piece into many derivative formats (blog series, email sequences, social posts, webinars, podcasts, video shorts) without losing the original's value or producing AI-slop variants. The discipline of adaptation per medium rather than mass-blast distribution. Triggers on content repurposing, content adaptation, cross-format content, content atomization, content multiplication, content distribution across formats, source-piece-to-derivative, video shorts from blog, email from whitepaper, podcast from article, blog series from research. Also triggers when a flagship piece is shipping but the team has not planned how to extend it across formats, when repurposing is happening but the derivatives feel mass-produced, or when AI-assisted repurposing is producing slop variants of strong source pieces.","content-repurposing",{"claudeCode":12},"SKILL.md frontmatter at skills/content-repurposing/SKILL.md",[754,755,757,759,761,763,765,767,769,771],{"path":275,"priority":276},{"path":756,"priority":279},"references/aeo-extraction-patterns.md",{"path":758,"priority":279},"references/common-repurposing-failures.md",{"path":760,"priority":279},"references/cross-promotion-patterns.md",{"path":762,"priority":279},"references/format-adaptation-patterns.md",{"path":764,"priority":279},"references/per-format-constraints.md",{"path":766,"priority":279},"references/repurposing-pipeline-templates.md",{"path":768,"priority":279},"references/sequencing-and-cadence-patterns.md",{"path":770,"priority":279},"references/source-piece-selection-criteria.md",{"path":772,"priority":279},"references/voice-consistency-across-formats.md",{"basePath":774,"description":775,"displayName":776,"installMethods":777,"rationale":778,"selectedPaths":779,"source":284,"sourceLanguage":18,"type":252},"skills/content-strategy","Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.","content-strategy",{"claudeCode":12},"SKILL.md frontmatter at skills/content-strategy/SKILL.md",[780,781,783],{"path":275,"priority":276},{"path":782,"priority":279},"references/content-strategy-template.md",{"path":784,"priority":279},"references/editorial-calendar-template.md",{"basePath":786,"description":787,"displayName":788,"installMethods":789,"rationale":790,"selectedPaths":791,"source":284,"sourceLanguage":18,"type":252},"skills/cost-optimization","Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity. Use this skill when reviewing monthly cloud or SaaS spend, finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning for budget cuts. Triggers on cost optimization, cloud spend, SaaS spend, rightsizing, unused resources, FinOps, infrastructure audit, vendor consolidation, budget cut, cost review. Also triggers when finance flags rising costs or when a contract renewal is up.","cost-optimization",{"claudeCode":12},"SKILL.md frontmatter at skills/cost-optimization/SKILL.md",[792,793],{"path":275,"priority":276},{"path":794,"priority":279},"references/cloud-audit-checklist.md",{"basePath":796,"description":797,"displayName":798,"installMethods":799,"rationale":800,"selectedPaths":801,"source":284,"sourceLanguage":18,"type":252},"skills/creative-brief","Create or refine a creative brief that bridges discovery and execution. Use this skill whenever the user is starting a new project, kicking off a website, beginning a brand build or redesign, briefing a designer or developer or AI agent, or trying to align a team before building. Triggers on creative brief, design brief, brand brief, project kickoff, kicking off, briefing the team, project intake, design direction, brief the designer, brief the dev, where do we start, how do we start, write a brief, project overview, scope this project, align on direction. Also triggers when the user has a vague idea and needs to make it concrete enough to hand off, even if they do not say 'brief' explicitly.","creative-brief",{"claudeCode":12},"SKILL.md frontmatter at skills/creative-brief/SKILL.md",[802,803,804,806],{"path":275,"priority":276},{"path":384,"priority":279},{"path":805,"priority":279},"references/example-brief.md",{"path":807,"priority":279},"references/voice-and-tone-guide.md",{"basePath":809,"description":810,"displayName":811,"installMethods":812,"rationale":813,"selectedPaths":814,"source":284,"sourceLanguage":18,"type":252},"skills/creative-direction","Walk the user through four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) and produce a structured aesthetic brief that downstream skills consume as required input. This is the aesthetic depth layer, distinct from `creative-brief` which covers the operational kickoff (scope, audience, deliverables, constraints). Use this skill when a project needs aesthetic coherence across many small decisions and the user has not yet articulated direction beyond a vague feeling. The brief becomes a reference that content, copy, design, and art-direction skills check against when producing output. Triggers on creative direction, aesthetic direction, set the aesthetic, define the visual direction, what's the vibe, what's the tone, the four axes, tone register, aesthetic philosophy, audience relationship, sensory ambition, our visual register. Also triggers when multiple downstream aesthetic-producing skills are about to run and need a shared brief to maintain coherence. Does NOT fire when the user needs a general kickoff brief covering scope and constraints (use `creative-brief` instead), for tactical single-piece work, when the user already has complete aesthetic direction documented, for purely functional output, or for production-stage work where direction is locked.","creative-direction",{"claudeCode":12},"SKILL.md frontmatter at skills/creative-direction/SKILL.md",[815,816,818,820],{"path":275,"priority":276},{"path":817,"priority":279},"references/axes-explained.md",{"path":819,"priority":279},"references/brief-template.md",{"path":821,"priority":279},"references/example-aesthetic-brief.md",{"basePath":823,"description":824,"displayName":825,"installMethods":826,"rationale":827,"selectedPaths":828,"source":284,"sourceLanguage":18,"type":252},"skills/cro-optimization","Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions. Use this skill whenever the user wants to optimize conversion, run A/B tests, audit a funnel, generate test hypotheses, design experiments, or analyze test results. Triggers on conversion optimization, CRO, A/B test, split test, multivariate test, hypothesis, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization. Also triggers when the user has a conversion problem and isn't sure where to start, or when test results are ambiguous and need interpretation.","cro-optimization",{"claudeCode":12},"SKILL.md frontmatter at skills/cro-optimization/SKILL.md",[829,830],{"path":275,"priority":276},{"path":831,"priority":279},"references/hypothesis-library.md",{"basePath":833,"description":834,"displayName":835,"installMethods":836,"rationale":837,"selectedPaths":838,"source":284,"sourceLanguage":18,"type":252},"skills/data-warehouse-experimentation","Running experiments out of the data warehouse instead of via dedicated experiment platforms. SQL-based assignment, exposure logging discipline, metric definitions in dbt models, statistical analysis in SQL or Python, variance reduction with CUPED, sequential testing, and the operational tradeoffs vs platforms like Statsig and Optimizely. Triggers on warehouse-native experimentation, run experiments in BigQuery, run experiments in Snowflake, dbt experiments, SQL t-test, CUPED variance reduction, exposure log, sample ratio mismatch, sequential testing, mSPRT, doubly robust estimation, build vs buy experimentation. Also triggers when the team is choosing between platform and warehouse, building warehouse-native experiment infrastructure, auditing one, or running an experiment with a custom metric the platform cannot handle.","data-warehouse-experimentation",{"claudeCode":12},"SKILL.md frontmatter at skills/data-warehouse-experimentation/SKILL.md",[839,840,842,844,846,848,850,852,854],{"path":275,"priority":276},{"path":841,"priority":279},"references/assignment-and-exposure-patterns.md",{"path":843,"priority":279},"references/common-pitfalls.md",{"path":845,"priority":279},"references/metric-definitions-in-dbt.md",{"path":847,"priority":279},"references/power-analysis-calculations.md",{"path":849,"priority":279},"references/sequential-testing-patterns.md",{"path":851,"priority":279},"references/statistical-analysis-templates.md",{"path":853,"priority":279},"references/variance-reduction-techniques.md",{"path":855,"priority":279},"references/warehouse-vs-platform-decision.md",{"basePath":857,"description":858,"displayName":859,"installMethods":860,"rationale":861,"selectedPaths":862,"source":284,"sourceLanguage":18,"type":252},"skills/dependency-management","Manage third-party libraries, runtimes, and SaaS dependencies. Use this skill when setting an update cadence, responding to security advisories, dealing with deprecated dependencies, evaluating new dependencies, auditing what's installed, or unblocking a dependency upgrade. Triggers on dependency, package update, security patch, lockfile, deprecated, breaking change, supply chain, dependency audit, npm audit, dependabot, renovate. Also triggers when a build breaks after an update or when an advisory is published for a used package.","dependency-management",{"claudeCode":12},"SKILL.md frontmatter at skills/dependency-management/SKILL.md",[863,864],{"path":275,"priority":276},{"path":865,"priority":279},"references/upgrade-checklist.md",{"basePath":867,"description":868,"displayName":869,"installMethods":870,"rationale":871,"selectedPaths":872,"source":284,"sourceLanguage":18,"type":252},"skills/design-standards","Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card, CTA, layout, review the UI, fix the design, design system, design tokens, spacing, typography scale, button standards, mobile design. Also triggers for any production design decision where contrast, accessibility, spacing, or visual hierarchy matters.","design-standards",{"claudeCode":12},"SKILL.md frontmatter at skills/design-standards/SKILL.md",[873,874,876,878],{"path":275,"priority":276},{"path":875,"priority":279},"references/design-tokens-template.md",{"path":877,"priority":279},"references/preship-checklist.md",{"path":879,"priority":279},"references/tailwind-patterns.md",{"basePath":881,"description":882,"displayName":883,"installMethods":884,"rationale":885,"selectedPaths":886,"source":284,"sourceLanguage":18,"type":252},"skills/design-system","Build or audit a design system including component library, design tokens, naming conventions, contribution model, and documentation. Use this skill whenever the user wants to build a design system, audit an existing system, define design tokens at the system level, structure a component library, or set up design system governance. Triggers on design system, component library, design tokens, atomic design, atoms, molecules, organisms, design system documentation, Storybook, Figma library, system governance, design contribution model. Also triggers when teams are inconsistent across products and a system is the answer.","design-system",{"claudeCode":12},"SKILL.md frontmatter at skills/design-system/SKILL.md",[887,888,890,892],{"path":275,"priority":276},{"path":889,"priority":279},"references/governance-playbook.md",{"path":891,"priority":279},"references/system-architecture.md",{"path":893,"priority":279},"references/system-audit-template.md",{"basePath":895,"description":896,"displayName":897,"installMethods":898,"rationale":899,"selectedPaths":900,"source":284,"sourceLanguage":18,"type":252},"skills/discovery-research-synthesis","Turning research artifacts into actionable PM insight. Customer interviews, user research notes, support ticket reviews, sales call transcripts, survey data, in-app feedback, all synthesized into the decisions they are meant to inform. The discipline of moving from raw discovery data to clear product direction without losing signal in the synthesis or fabricating insight that was not actually there. Triggers on research synthesis, customer interview synthesis, user research analysis, discovery readout, research insights, sales call analysis, support ticket analysis, qualitative data analysis. Also triggers when a team has done research but cannot turn it into decisions, when synthesis is producing pretty decks but no roadmap movement, or when an upcoming PM decision needs to be grounded in research already conducted.","discovery-research-synthesis",{"claudeCode":12},"SKILL.md frontmatter at skills/discovery-research-synthesis/SKILL.md",[901,902,904,906,908,910,912,914,916,918],{"path":275,"priority":276},{"path":903,"priority":279},"references/common-discovery-synthesis-failures.md",{"path":905,"priority":279},"references/from-pattern-to-product-implication.md",{"path":907,"priority":279},"references/pattern-naming-patterns.md",{"path":909,"priority":279},"references/research-types-and-when-each-fits.md",{"path":911,"priority":279},"references/synthesis-review-and-validation.md",{"path":913,"priority":279},"references/synthesis-sequence-walkthrough.md",{"path":915,"priority":279},"references/tagging-and-clustering-discipline.md",{"path":917,"priority":279},"references/when-to-gather-more-data.md",{"path":919,"priority":279},"references/writing-for-decisions-not-decks.md",{"basePath":921,"description":922,"displayName":923,"installMethods":924,"rationale":925,"selectedPaths":926,"source":284,"sourceLanguage":18,"type":252},"skills/documentation-strategy","Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech writing, knowledge base, wiki, runbook, README, internal docs, doc audit, doc maintenance, stale docs, where do we document. Also triggers when the team is repeatedly answering the same questions or when onboarding takes too long.","documentation-strategy",{"claudeCode":12},"SKILL.md frontmatter at skills/documentation-strategy/SKILL.md",[927,928],{"path":275,"priority":276},{"path":929,"priority":279},"references/doc-types-guide.md",{"basePath":931,"description":932,"displayName":933,"installMethods":934,"rationale":935,"selectedPaths":936,"source":284,"sourceLanguage":18,"type":252},"skills/domain-strategy","Plan, manage, and optimize a domain portfolio. Use this skill for DNS architecture decisions, redirect strategies, registrar choice, parking unused domains, multi-site setups, and domain consolidation or split planning. Triggers on DNS, domain, registrar, redirect, parking, subdomain, apex, www vs non-www, multi-site, portfolio, hreflang setup, domain migration. Also triggers when planning a new site that needs domain decisions made before launch.","domain-strategy",{"claudeCode":12},"SKILL.md frontmatter at skills/domain-strategy/SKILL.md",[937,938],{"path":275,"priority":276},{"path":939,"priority":279},"references/dns-record-reference.md",{"basePath":941,"description":942,"displayName":943,"installMethods":944,"rationale":945,"selectedPaths":946,"source":284,"sourceLanguage":18,"type":252},"skills/editorial-qa","Pre-publish QA framework for content. Brief adherence, voice consistency, fact accuracy, structure and clarity, AI-content audit, SEO and AEO compliance, internal linking and schema validation, QA at scale via sampling, the QA workflow, and the discipline that distinguishes catch-problems QA from checkbox QA. Triggers on editorial QA, content review, pre-publish review, content audit, content QA process, AI-content audit, hallucination check, content sampling, programmatic QA, voice consistency check, brief adherence check. Also triggers when a content team is shipping sloppy work, when AI-co-authored content is reaching publish unaudited, when a QA process burns reviewers out, or when a programmatic SEO set needs sampling discipline.","editorial-qa",{"claudeCode":12},"SKILL.md frontmatter at skills/editorial-qa/SKILL.md",[947,948,950,952,954,956,958,960,962,964,966],{"path":275,"priority":276},{"path":949,"priority":279},"references/ai-content-audit-patterns.md",{"path":951,"priority":279},"references/brief-adherence-checklist.md",{"path":953,"priority":279},"references/common-qa-failures.md",{"path":955,"priority":279},"references/fact-accuracy-and-citation-discipline.md",{"path":957,"priority":279},"references/internal-linking-and-schema-validation.md",{"path":959,"priority":279},"references/qa-at-scale-patterns.md",{"path":961,"priority":279},"references/qa-workflow-templates.md",{"path":963,"priority":279},"references/seo-aeo-compliance-checklist.md",{"path":965,"priority":279},"references/structure-and-clarity-review.md",{"path":967,"priority":279},"references/voice-consistency-patterns.md",{"basePath":969,"description":970,"displayName":971,"installMethods":972,"rationale":973,"selectedPaths":974,"source":284,"sourceLanguage":18,"type":252},"skills/email-deliverability","Make sure email actually reaches inboxes. Use this skill when setting up email authentication (SPF, DKIM, DMARC), diagnosing emails landing in spam, planning a domain reputation strategy, monitoring sender reputation, or hardening against email spoofing. Triggers on email deliverability, SPF, DKIM, DMARC, spam folder, sender reputation, mailbox provider, soft bounces, bounce rate, BIMI, MTA-STS, deliverability audit. Also triggers when a marketing or transactional email isn't reaching users.","email-deliverability",{"claudeCode":12},"SKILL.md frontmatter at skills/email-deliverability/SKILL.md",[975,976],{"path":275,"priority":276},{"path":977,"priority":279},"references/dmarc-rollout-playbook.md",{"basePath":979,"description":980,"displayName":981,"installMethods":982,"rationale":983,"selectedPaths":984,"source":284,"sourceLanguage":18,"type":252},"skills/email-sequences","Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, and broadcast sends. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns.","email-sequences",{"claudeCode":12},"SKILL.md frontmatter at skills/email-sequences/SKILL.md",[985,986,988],{"path":275,"priority":276},{"path":987,"priority":279},"references/sequence-templates.md",{"path":989,"priority":279},"references/subject-line-patterns.md",{"basePath":991,"description":992,"displayName":993,"installMethods":994,"rationale":995,"selectedPaths":996,"source":284,"sourceLanguage":18,"type":252},"skills/experiment-design","A discipline for designing experiments (A/B tests, multivariate, holdouts) so the results actually answer the question you asked. Hypothesis writing, sample size, duration, segment analysis, interpretation, decision-making, and the common failure modes that produce confidently wrong shipping decisions.","experiment-design",{"claudeCode":12},"SKILL.md frontmatter at skills/experiment-design/SKILL.md",[997,998,1000,1002,1004,1006,1008,1010],{"path":275,"priority":276},{"path":999,"priority":279},"references/common-failures.md",{"path":1001,"priority":279},"references/hypothesis-templates.md",{"path":1003,"priority":279},"references/platform-comparison.md",{"path":1005,"priority":279},"references/post-experiment-decision-framework.md",{"path":1007,"priority":279},"references/pre-experiment-readiness-checklist.md",{"path":1009,"priority":279},"references/results-interpretation-checklist.md",{"path":1011,"priority":279},"references/sample-size-tables.md",{"basePath":1013,"description":1014,"displayName":1015,"installMethods":1016,"rationale":1017,"selectedPaths":1018,"source":284,"sourceLanguage":18,"type":252},"skills/experimentation-analytics","How to read experiment results without fooling yourself. Confidence intervals, p-values, multiple testing, sequential testing, CUPED, heterogeneous treatment effects, ratio metrics, network effects, dashboard reconciliation, and the interpretation failures that produce confidently wrong shipping decisions.","experimentation-analytics",{"claudeCode":12},"SKILL.md frontmatter at skills/experimentation-analytics/SKILL.md",[1019,1020,1022,1023,1025,1027,1029,1031],{"path":275,"priority":276},{"path":1021,"priority":279},"references/analytics-platform-comparison.md",{"path":320,"priority":279},{"path":1024,"priority":279},"references/confidence-interval-cheatsheet.md",{"path":1026,"priority":279},"references/dashboard-vs-experiment-reconciliation.md",{"path":1028,"priority":279},"references/p-value-interpretation-guide.md",{"path":1030,"priority":279},"references/result-presentation-templates.md",{"path":1032,"priority":279},"references/statistical-method-reference.md",{"basePath":1034,"description":1035,"displayName":1036,"installMethods":1037,"rationale":1038,"selectedPaths":1039,"source":284,"sourceLanguage":18,"type":252},"skills/experimentation-platform-orchestrator","A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.","experimentation-platform-orchestrator",{"claudeCode":12},"SKILL.md frontmatter at skills/experimentation-platform-orchestrator/SKILL.md",[1040,1041,1043,1045,1047,1049,1051,1053],{"path":275,"priority":276},{"path":1042,"priority":279},"references/common-mistakes.md",{"path":1044,"priority":279},"references/cost-and-pricing-models.md",{"path":1046,"priority":279},"references/governance-and-team-setup.md",{"path":1048,"priority":279},"references/mcp-capability-comparison.md",{"path":1050,"priority":279},"references/migration-playbook.md",{"path":1052,"priority":279},"references/multi-platform-orchestration.md",{"path":1054,"priority":279},"references/platform-decision-matrix.md",{"basePath":1056,"description":1057,"displayName":1058,"installMethods":1059,"rationale":1060,"selectedPaths":1061,"source":284,"sourceLanguage":18,"type":252},"skills/feature-flagging","Operational discipline for feature flags as production infrastructure. Flag types, naming, targeting rules, rollout strategy, lifecycle, governance, stale flag management, and the technical debt patterns that bite teams who weren't deliberate about it.","feature-flagging",{"claudeCode":12},"SKILL.md frontmatter at skills/feature-flagging/SKILL.md",[1062,1063,1065,1067,1069,1071,1073,1075],{"path":275,"priority":276},{"path":1064,"priority":279},"references/flag-lifecycle-checklist.md",{"path":1066,"priority":279},"references/flag-naming-conventions.md",{"path":1068,"priority":279},"references/flag-rollout-strategies.md",{"path":1070,"priority":279},"references/flag-types-reference.md",{"path":1072,"priority":279},"references/governance-and-permissions.md",{"path":1074,"priority":279},"references/stale-flag-cleanup-playbook.md",{"path":1076,"priority":279},"references/targeting-rule-patterns.md",{"basePath":1078,"description":1079,"displayName":1080,"installMethods":1081,"rationale":1082,"selectedPaths":1083,"source":284,"sourceLanguage":18,"type":252},"skills/feature-launch-playbook","The operational playbook for launching a feature well. Positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses, and the discipline that distinguishes shipping from releasing from actually launching. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when planning a launch (any size, any segment), auditing an existing launch process, fixing the we shipped it but the metric did not move problem, or building a launch checklist for the team.","feature-launch-playbook",{"claudeCode":12},"SKILL.md frontmatter at skills/feature-launch-playbook/SKILL.md",[1084,1085,1087,1089,1091,1093,1095,1097,1099,1101,1103],{"path":275,"priority":276},{"path":1086,"priority":279},"references/common-launch-failures.md",{"path":1088,"priority":279},"references/customer-comms-playbook.md",{"path":1090,"priority":279},"references/internal-alignment-checklist.md",{"path":1092,"priority":279},"references/launch-tier-decision.md",{"path":1094,"priority":279},"references/monitoring-readiness-checklist.md",{"path":1096,"priority":279},"references/positioning-canvas.md",{"path":1098,"priority":279},"references/post-launch-measurement-framework.md",{"path":1100,"priority":279},"references/rollout-strategy-patterns.md",{"path":1102,"priority":279},"references/sales-enablement-template.md",{"path":1104,"priority":279},"references/support-readiness-checklist.md",{"basePath":1106,"description":1107,"displayName":1108,"installMethods":1109,"rationale":1110,"selectedPaths":1111,"source":284,"sourceLanguage":18,"type":252},"skills/form-strategy","Design forms that convert, validate well, resist spam, and integrate cleanly with downstream systems. Use this skill when designing or auditing any form (contact, signup, checkout, multi-step, embedded), planning validation logic, fighting spam, choosing form tooling, or improving form conversion. Triggers on form design, form validation, form conversion, multi-step form, form spam, captcha, honeypot, form abandonment, signup form, contact form. Also triggers when form completion rates are low or spam is overwhelming.","form-strategy",{"claudeCode":12},"SKILL.md frontmatter at skills/form-strategy/SKILL.md",[1112,1113],{"path":275,"priority":276},{"path":1114,"priority":279},"references/form-anatomy-checklist.md",{"basePath":1116,"description":1117,"displayName":1118,"installMethods":1119,"rationale":1120,"selectedPaths":1121,"source":284,"sourceLanguage":18,"type":252},"skills/frontend-component-build","Build production-ready frontend components with accessible markup, sensible props, defined states, and tested behavior. Use this skill whenever the user wants to build a component from scratch, refactor an existing one, design a component API, or implement a UI element with proper states and accessibility. Triggers on build a component, create a button, create a modal, create a form input, component API, props design, component states, refactor component, accessible component. Also triggers when implementing UI from a design that needs to be reusable.","frontend-component-build",{"claudeCode":12},"SKILL.md frontmatter at skills/frontend-component-build/SKILL.md",[1122,1123,1125,1127],{"path":275,"priority":276},{"path":1124,"priority":279},"references/accessibility-patterns.md",{"path":1126,"priority":279},"references/component-api-patterns.md",{"path":1128,"priority":279},"references/component-spec-template.md",{"basePath":1130,"description":1131,"displayName":1132,"installMethods":1133,"rationale":1134,"selectedPaths":1135,"source":284,"sourceLanguage":18,"type":252},"skills/funnel-flow-architecture","Architecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels. Honest about silo-funnels (every tool standalone), kitchen-sink-funnels (every audience squeezed through one path), and matched-funnels (architecture matched to audience-and-stage) patterns. Triggers on funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration. Also triggers when the team's growth tools are working individually but not together, when audience segments share one nurture path, or when a funnel is being architected from scratch.","funnel-flow-architecture",{"claudeCode":12},"SKILL.md frontmatter at skills/funnel-flow-architecture/SKILL.md",[1136,1137,1139,1141,1143,1145,1147,1149,1151,1153],{"path":275,"priority":276},{"path":1138,"priority":279},"references/architecture-anti-patterns.md",{"path":1140,"priority":279},"references/audience-and-stage-segmentation.md",{"path":1142,"priority":279},"references/common-funnel-architecture-failures.md",{"path":1144,"priority":279},"references/cross-tool-data-flow-patterns.md",{"path":1146,"priority":279},"references/entry-point-architecture-patterns.md",{"path":1148,"priority":279},"references/funnel-iteration-discipline.md",{"path":1150,"priority":279},"references/funnel-measurement-patterns.md",{"path":1152,"priority":279},"references/nurture-sequence-architecture.md",{"path":1154,"priority":279},"references/tool-to-funnel-mapping.md",{"basePath":1156,"description":1157,"displayName":1158,"installMethods":1159,"rationale":1160,"selectedPaths":1161,"source":284,"sourceLanguage":18,"type":252},"skills/incident-response","Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.","incident-response",{"claudeCode":12},"SKILL.md frontmatter at skills/incident-response/SKILL.md",[1162,1163],{"path":275,"priority":276},{"path":1164,"priority":279},"references/incident-playbook.md",{"basePath":1166,"description":1167,"displayName":1168,"installMethods":1169,"rationale":1170,"selectedPaths":1171,"source":284,"sourceLanguage":18,"type":252},"skills/information-architecture","Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system level. Triggers on sitemap, site structure, navigation, IA, information architecture, URL structure, content types, taxonomy, categorization, breadcrumbs, hub pages, faceted navigation, site search, labeling. Also triggers when content is being created without a structural plan, or when an existing site's structure is being audited or restructured.","information-architecture",{"claudeCode":12},"SKILL.md frontmatter at skills/information-architecture/SKILL.md",[1172,1173,1175],{"path":275,"priority":276},{"path":1174,"priority":279},"references/ia-document-template.md",{"path":1176,"priority":279},"references/url-pattern-library.md",{"basePath":1178,"description":1179,"displayName":1180,"installMethods":1181,"rationale":1182,"selectedPaths":1183,"source":284,"sourceLanguage":18,"type":252},"skills/integration-orchestrator","Generate a phased delivery orchestration plan for creative-direction-driven work, mapping which skills run when, what locks at which gate, how handoffs occur between phases, and how the cadence implements in the team's actual tools (Jira, Linear, Notion, Figma, GitHub) with AI agents participating via MCP and CLI. Distinct from `creative-brief` (static project brief) and `creative-direction` (aesthetic direction). This skill produces a temporal map: phase-by-phase cadence, lock points, handoff specs, gate definitions, automation and QA verification gates, and platform-specific implementation. Triggers on integration orchestrator, delivery cadence, project orchestration, when does the brief lock, how to phase creative direction, brand build cadence, rebrand timeline, campaign delivery plan, design-development handoff, brief freeze, identity gate, copy approval phase, QA gate, automated verification, MCP integration for project management, Claude Code workflow setup, agent-driven QA. Triggers when a team is starting a creative-direction project and needs to sequence the work, OR when a project is mid-flight and the cadence has broken (freeze points being unfrozen, parallel work getting out of sync), OR when a team is integrating AI agents into their existing PM workflow. Does NOT fire when the user needs project scoping (use `creative-brief`), aesthetic direction (use `creative-direction`), or general project management without a creative-direction throughline.","integration-orchestrator",{"claudeCode":12},"SKILL.md frontmatter at skills/integration-orchestrator/SKILL.md",[1184,1185,1187,1189,1191,1193,1195,1197],{"path":275,"priority":276},{"path":1186,"priority":279},"references/automation-and-qa-tooling.md",{"path":1188,"priority":279},"references/cadence-patterns.md",{"path":1190,"priority":279},"references/example-orchestration.md",{"path":1192,"priority":279},"references/gate-definitions.md",{"path":1194,"priority":279},"references/handoff-protocols.md",{"path":1196,"priority":279},"references/platform-implementation.md",{"path":1198,"priority":279},"references/team-size-modulation.md",{"basePath":1200,"description":1201,"displayName":1202,"installMethods":1203,"rationale":1204,"selectedPaths":1205,"source":284,"sourceLanguage":18,"type":252},"skills/interactive-product-tour","Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of need), and contextual-when-needed (surfaces help at the moment friction occurs) patterns. Triggers on product tour, in-product tooltip, contextual help, walkthrough, feature tour, hint system, in-app guidance, tour platform. Also triggers when feature adoption is low, when users miss key product capabilities, or when an in-product help system is being scoped for the first time.","interactive-product-tour",{"claudeCode":12},"SKILL.md frontmatter at skills/interactive-product-tour/SKILL.md",[1206,1207,1209,1211,1213,1215,1217,1219,1221,1223],{"path":275,"priority":276},{"path":1208,"priority":279},"references/common-tour-failures.md",{"path":1210,"priority":279},"references/completion-tracking-and-re-trigger.md",{"path":1212,"priority":279},"references/contextual-placement-patterns.md",{"path":1214,"priority":279},"references/dismissal-and-non-intrusion-patterns.md",{"path":1216,"priority":279},"references/power-user-vs-new-user-patterns.md",{"path":1218,"priority":279},"references/tour-anti-patterns.md",{"path":1220,"priority":279},"references/tour-architecture-patterns.md",{"path":1222,"priority":279},"references/tour-decision-criteria.md",{"path":1224,"priority":279},"references/trigger-logic-patterns.md",{"basePath":1226,"description":1227,"displayName":1228,"installMethods":1229,"rationale":1230,"selectedPaths":1231,"source":284,"sourceLanguage":18,"type":252},"skills/internationalization","Plan and run a multi-language or multi-region site. Use this skill when adding new locales, choosing URL structure for languages (subfolders vs subdomains vs ccTLDs), implementing hreflang, planning translation workflow, handling currency and date formats, designing for RTL languages, or auditing a stalled internationalization rollout. Triggers on internationalization, i18n, localization, l10n, hreflang, multi-language, translation workflow, RTL, locale, ccTLD, subfolder vs subdomain, language switcher. Also triggers when international audiences underperform or translations are stale.","internationalization",{"claudeCode":12},"SKILL.md frontmatter at skills/internationalization/SKILL.md",[1232,1233],{"path":275,"priority":276},{"path":1234,"priority":279},"references/locale-checklist.md",{"basePath":1236,"description":1237,"displayName":1238,"installMethods":1239,"rationale":1240,"selectedPaths":1241,"source":284,"sourceLanguage":18,"type":252},"skills/journey-mapping","Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the user experience, or visualize touchpoints and pain points. Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map. Also triggers when the team has departmental views of users but no shared map of what the experience actually feels like.","journey-mapping",{"claudeCode":12},"SKILL.md frontmatter at skills/journey-mapping/SKILL.md",[1242,1243],{"path":275,"priority":276},{"path":1244,"priority":279},"references/journey-map-template.md",{"basePath":1246,"description":1247,"displayName":1248,"installMethods":1249,"rationale":1250,"selectedPaths":1251,"source":284,"sourceLanguage":18,"type":252},"skills/jtbd-framing","The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation. Also triggers when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy.","jtbd-framing",{"claudeCode":12},"SKILL.md frontmatter at skills/jtbd-framing/SKILL.md",[1252,1253,1255,1257,1259,1261,1263,1265,1267],{"path":275,"priority":276},{"path":1254,"priority":279},"references/applying-jtbd-to-discovery.md",{"path":1256,"priority":279},"references/applying-jtbd-to-positioning.md",{"path":1258,"priority":279},"references/applying-jtbd-to-prioritization.md",{"path":1260,"priority":279},"references/common-jtbd-failures.md",{"path":1262,"priority":279},"references/functional-emotional-social-dimensions.md",{"path":1264,"priority":279},"references/hire-and-fire-criteria.md",{"path":1266,"priority":279},"references/identifying-struggling-moments.md",{"path":1268,"priority":279},"references/job-statement-structure-patterns.md",{"basePath":1270,"description":1271,"displayName":1272,"installMethods":1273,"rationale":1274,"selectedPaths":1275,"source":284,"sourceLanguage":18,"type":252},"skills/landing-page-copy","Write landing page copy with attention to the hero, value proposition, social proof, objection handling, and conversion-focused CTAs. Use this skill whenever the user wants to write a landing page, sales page, hero section, or any conversion-focused web copy. Triggers on landing page, sales page, hero copy, value proposition, headline, subheadline, hero section, CTA copy, conversion copy, opt-in page, squeeze page. Also triggers when the user has a marketing campaign or product launch needing dedicated conversion copy.","landing-page-copy",{"claudeCode":12},"SKILL.md frontmatter at skills/landing-page-copy/SKILL.md",[1276,1277,1279],{"path":275,"priority":276},{"path":1278,"priority":279},"references/hero-formulas.md",{"path":1280,"priority":279},"references/objection-library.md",{"basePath":1282,"description":1283,"displayName":1284,"installMethods":1285,"rationale":1286,"selectedPaths":1287,"source":284,"sourceLanguage":18,"type":252},"skills/launch-runbook","Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers on launch runbook, go-live, launch day, DNS cutover, deploy to production, site launch, product launch, cutover plan, launch checklist, deployment procedure. Also triggers when a launch is approaching and the team needs structured coordination, even if 'runbook' is not explicitly stated.","launch-runbook",{"claudeCode":12},"SKILL.md frontmatter at skills/launch-runbook/SKILL.md",[1288,1289],{"path":275,"priority":276},{"path":1290,"priority":279},"references/runbook-template.md",{"basePath":1292,"description":1293,"displayName":1294,"installMethods":1295,"rationale":1296,"selectedPaths":1297,"source":284,"sourceLanguage":18,"type":252},"skills/lead-magnet-design","Designing lead magnets that earn the email. The discipline of building gated content (ebooks, templates, checklists, swipe files, mini-courses, free tools) that delivers genuine standalone value while qualifying the lead and warming them for what comes next. Honest about thin-bait (overpromises, underdelivers), kitchen-sink-resource (everything, helps with nothing), and earned-value-magnet (delivers standalone value while qualifying the lead). Triggers on lead magnet, gated content, opt-in offer, ebook, checklist, template, swipe file, mini-course, free tool, content upgrade, freebie, opt-in, list-building offer. Also triggers when an audience is being asked for an email and the offer attached to that ask needs design discipline, when previous lead magnets converted but did not produce qualified leads, or when a lead magnet is being scoped for the first time.","lead-magnet-design",{"claudeCode":12},"SKILL.md frontmatter at skills/lead-magnet-design/SKILL.md",[1298,1299,1301,1303,1305,1307,1309,1311,1313,1315],{"path":275,"priority":276},{"path":1300,"priority":279},"references/audience-fit-qualification.md",{"path":1302,"priority":279},"references/common-lead-magnet-failures.md",{"path":1304,"priority":279},"references/delivery-and-follow-up-sequences.md",{"path":1306,"priority":279},"references/format-selection-patterns.md",{"path":1308,"priority":279},"references/format-specific-quality-gates.md",{"path":1310,"priority":279},"references/lead-magnet-anti-patterns.md",{"path":1312,"priority":279},"references/lead-magnet-decision-criteria.md",{"path":1314,"priority":279},"references/title-and-presentation-discipline.md",{"path":1316,"priority":279},"references/would-they-pay-for-this-test.md",{"basePath":1318,"description":1319,"displayName":1320,"installMethods":1321,"rationale":1322,"selectedPaths":1323,"source":284,"sourceLanguage":18,"type":252},"skills/logo-design","Generate logo variants for a brand or organization, producing multiple production-grade marks across different architectures (wordmark, lockup, symbol-only, letterform-as-symbol, monogram) with rationale, application specs, and decision-ready presentation. Distinct from `brand-identity`, which produces a complete identity system covering logo plus color plus type plus voice plus applications. This skill goes deep on the logo specifically: typographic register selection, symbol approach taxonomy, application context discipline (16px favicon, embroidery, signage, motion), production specs (SVG-ready, single-color reproducibility, reverse versions). Triggers on logo design, design a logo, logo for X, brand mark, wordmark, logotype, monogram, lockup, mark variants, logo iterations, redesign the logo, refine the logo, logo refresh, letterform-as-symbol. Also triggers when the user has an established brand and wants to explore mark variants or when iterating on existing logo work for production. Does NOT fire when the user needs full brand identity (use `brand-identity`), brand positioning or strategy (use `brand-discovery`), project-wide creative direction (use `creative-direction`), or one-off illustration.","logo-design",{"claudeCode":12},"SKILL.md frontmatter at skills/logo-design/SKILL.md",[1324,1325,1327,1329,1331,1333,1335,1337],{"path":275,"priority":276},{"path":1326,"priority":279},"references/application-contexts.md",{"path":1328,"priority":279},"references/architectures-explained.md",{"path":1330,"priority":279},"references/category-conventions.md",{"path":1332,"priority":279},"references/client-package.md",{"path":1334,"priority":279},"references/example-variant-spec.md",{"path":1336,"priority":279},"references/symbol-approaches.md",{"path":1338,"priority":279},"references/typographic-registers.md",{"basePath":1340,"description":1341,"displayName":1342,"installMethods":1343,"rationale":1344,"selectedPaths":1345,"source":284,"sourceLanguage":18,"type":252},"skills/long-form-content-frameworks","Patterns for individual long-form content pieces. Case studies, whitepapers, research reports, definitive guides, manifestos, ebooks, long-form tutorials. The structural disciplines that distinguish publication-quality long-form from bloggy-long padding or academic bloat. Different from pillar-content-architecture (which covers hub structure); this skill covers individual deep-dive pieces. Triggers on long-form content, case study writing, whitepaper, research report, definitive guide, ebook, manifesto, long-form tutorial, deep-dive article, anchor piece, foundational article, structural archetypes. Also triggers when a piece is over 3,000 words and the team is unsure how to structure it, when a long-form draft feels padded or saggy, or when a flagship asset needs the depth to actually earn the length.","long-form-content-frameworks",{"claudeCode":12},"SKILL.md frontmatter at skills/long-form-content-frameworks/SKILL.md",[1346,1347,1349,1351,1353,1355,1357,1359,1361,1363],{"path":275,"priority":276},{"path":1348,"priority":279},"references/attention-sustaining-techniques.md",{"path":1350,"priority":279},"references/breakouts-and-visualization.md",{"path":1352,"priority":279},"references/citation-and-source-authority.md",{"path":1354,"priority":279},"references/closing-patterns.md",{"path":1356,"priority":279},"references/common-long-form-failures.md",{"path":1358,"priority":279},"references/format-decision-framework.md",{"path":1360,"priority":279},"references/lede-patterns-for-long-form.md",{"path":1362,"priority":279},"references/section-weight-calibration.md",{"path":1364,"priority":279},"references/structural-archetype-patterns.md",{"basePath":1366,"description":1367,"displayName":1368,"installMethods":1369,"rationale":1370,"selectedPaths":1371,"source":284,"sourceLanguage":18,"type":252},"skills/media-asset-management","Plan and run a media pipeline for images, video, and downloadable assets. Use this skill when designing image storage and delivery, choosing formats (WebP, AVIF), setting up responsive images, picking a video host, organizing a brand asset library, or auditing a slow image pipeline. Triggers on image pipeline, asset library, DAM, image optimization, WebP, AVIF, responsive images, video hosting, image CDN, asset workflow, media management. Also triggers when images are slow, broken, or scattered across systems.","media-asset-management",{"claudeCode":12},"SKILL.md frontmatter at skills/media-asset-management/SKILL.md",[1372,1373],{"path":275,"priority":276},{"path":1374,"priority":279},"references/responsive-image-patterns.md",{"basePath":1376,"description":1377,"displayName":1378,"installMethods":1379,"rationale":1380,"selectedPaths":1381,"source":284,"sourceLanguage":18,"type":252},"skills/monitoring-and-alerting","Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards, what should we monitor. Also triggers when an incident reveals a gap in monitoring.","monitoring-and-alerting",{"claudeCode":12},"SKILL.md frontmatter at skills/monitoring-and-alerting/SKILL.md",[1382,1383],{"path":275,"priority":276},{"path":1384,"priority":279},"references/slo-design-guide.md",{"basePath":1386,"description":1387,"displayName":1388,"installMethods":1389,"rationale":1390,"selectedPaths":1391,"source":284,"sourceLanguage":18,"type":252},"skills/multi-step-form-design","Designing forms with multiple steps, progress indicators, conditional logic, and save-and-resume mechanics. The discipline of breaking complex data collection into stages that respect cognitive load while maintaining completion intent. Honest about kitchen-sink-single-page (overwhelms before the user starts), progress-theater (steps without genuine staging), and genuinely-staged (each step earns its own page) patterns. Triggers on multi-step form, multi-page form, form wizard, signup wizard, lead form, application form, intake form, configurator, onboarding form. Also triggers when a long form is converting poorly, when an audience is dropping off mid-form, or when a multi-step form is being scoped for the first time.","multi-step-form-design",{"claudeCode":12},"SKILL.md frontmatter at skills/multi-step-form-design/SKILL.md",[1392,1393,1395,1397,1399,1401,1403,1405,1407,1409],{"path":275,"priority":276},{"path":1394,"priority":279},"references/common-multi-step-form-failures.md",{"path":1396,"priority":279},"references/conditional-logic-patterns.md",{"path":1398,"priority":279},"references/drop-off-measurement-and-remediation.md",{"path":1400,"priority":279},"references/form-anti-patterns.md",{"path":1402,"priority":279},"references/multi-step-decision-criteria.md",{"path":1404,"priority":279},"references/progress-indicator-patterns.md",{"path":1406,"priority":279},"references/save-and-resume-mechanics.md",{"path":1408,"priority":279},"references/step-architecture-patterns.md",{"path":1410,"priority":279},"references/validation-strategy-patterns.md",{"basePath":1412,"description":1413,"displayName":1414,"installMethods":1415,"rationale":1416,"selectedPaths":1417,"source":284,"sourceLanguage":18,"type":252},"skills/okr-design","OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition with quarterly accountability). Triggers on OKR design, OKR setting, key result design, OKR scoring, mid-quarter recalibration, OKR cascading, outcomes vs outputs, quarterly planning, goal setting. Also triggers when a team's OKRs are always hit and producing no learning, when OKRs are demoralizing because they were set as fantasy, or when the team uses OKR vocabulary but the practice has decayed.","okr-design",{"claudeCode":12},"SKILL.md frontmatter at skills/okr-design/SKILL.md",[1418,1419,1421,1423,1425,1427,1429,1431,1433,1435],{"path":275,"priority":276},{"path":1420,"priority":279},"references/cascading-okrs-decisions.md",{"path":1422,"priority":279},"references/common-okr-failures.md",{"path":1424,"priority":279},"references/key-result-design-patterns.md",{"path":1426,"priority":279},"references/mid-quarter-recalibration.md",{"path":1428,"priority":279},"references/objective-design-patterns.md",{"path":1430,"priority":279},"references/okr-anti-patterns.md",{"path":1432,"priority":279},"references/okrs-vs-roadmap-vs-metrics.md",{"path":1434,"priority":279},"references/review-cadence-templates.md",{"path":1436,"priority":279},"references/scoring-discipline.md",{"basePath":1438,"description":1439,"displayName":1440,"installMethods":1441,"rationale":1442,"selectedPaths":1443,"source":284,"sourceLanguage":18,"type":252},"skills/onboarding-wizard-design","Designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. Honest about tutorial-overload (dump everything upfront), skip-friendly-empty (skipped onboarding leads to abandoned product), and earned-progressive-disclosure (right things at the right moments) patterns. Triggers on onboarding wizard, product onboarding, first-run experience, signup flow, activation flow, FRX, time-to-value, ah-ha moment design. Also triggers when activation rates are low, when users skip onboarding and never return, when onboarding flows are being scoped for the first time, or when audience research shows users not finding key features.","onboarding-wizard-design",{"claudeCode":12},"SKILL.md frontmatter at skills/onboarding-wizard-design/SKILL.md",[1444,1445,1447,1449,1451,1453,1455,1456,1458,1460],{"path":275,"priority":276},{"path":1446,"priority":279},"references/ah-ha-moment-engineering.md",{"path":1448,"priority":279},"references/common-onboarding-failures.md",{"path":1450,"priority":279},"references/drop-off-measurement-templates.md",{"path":1452,"priority":279},"references/progressive-disclosure-patterns.md",{"path":1454,"priority":279},"references/skip-and-resume-mechanics.md",{"path":1408,"priority":279},{"path":1457,"priority":279},"references/user-type-variation-patterns.md",{"path":1459,"priority":279},"references/wizard-anti-patterns.md",{"path":1461,"priority":279},"references/wizard-decision-criteria.md",{"basePath":1463,"description":1464,"displayName":1465,"installMethods":1466,"rationale":1467,"selectedPaths":1468,"source":284,"sourceLanguage":18,"type":252},"skills/paid-media-strategy","A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media strategy, ad budget allocation, channel selection, paid media plan, audit my Google Ads, audit my Meta Ads, scale paid media, kill underperforming campaign, paid media hypothesis, ad spend strategy, attribution reality, performance marketing strategy. Also triggers when a team is asking how to scale paid media, or whether to add a new channel, or how to reallocate spend across channels.","paid-media-strategy",{"claudeCode":12},"SKILL.md frontmatter at skills/paid-media-strategy/SKILL.md",[1469,1470,1472,1474,1476,1478,1480,1482],{"path":275,"priority":276},{"path":1471,"priority":279},"references/ads-platform-comparison.md",{"path":1473,"priority":279},"references/audience-segmentation-patterns.md",{"path":1475,"priority":279},"references/bid-strategy-reference.md",{"path":1477,"priority":279},"references/budget-allocation-templates.md",{"path":1479,"priority":279},"references/campaign-type-reference.md",{"path":1481,"priority":279},"references/channel-decision-matrix.md",{"path":999,"priority":279},{"basePath":1484,"description":1485,"displayName":1486,"installMethods":1487,"rationale":1488,"selectedPaths":1489,"source":284,"sourceLanguage":18,"type":252},"skills/performance-optimization","Diagnose and fix web performance issues including Core Web Vitals (LCP, INP, CLS), bundle size, asset optimization, render performance, and runtime efficiency. Use this skill whenever the user wants to improve page speed, fix Core Web Vitals, optimize assets, reduce bundle size, debug slow renders, or systematically improve a site's performance. Triggers on performance, page speed, Core Web Vitals, LCP, INP, CLS, FID, TTFB, bundle size, code splitting, image optimization, lazy loading, render blocking, slow page, performance audit, Lighthouse score. Also triggers when traffic or conversion is dropping due to perceived slowness.","performance-optimization",{"claudeCode":12},"SKILL.md frontmatter at skills/performance-optimization/SKILL.md",[1490,1491,1493,1495],{"path":275,"priority":276},{"path":1492,"priority":279},"references/audit-template.md",{"path":1494,"priority":279},"references/optimization-checklist.md",{"path":1496,"priority":279},"references/optimization-playbook.md",{"basePath":1498,"description":1499,"displayName":1500,"installMethods":1501,"rationale":1502,"selectedPaths":1503,"source":284,"sourceLanguage":18,"type":252},"skills/pillar-content-architecture","How to design a content hub that earns topical authority. Pillar topic selection, cluster planning, internal linking architecture, URL structure, pillar and cluster page anatomy, topical authority signals for SEO and AEO/GEO, and the maintenance discipline that distinguishes intentional hubs from accidental orphans. Triggers on pillar content, content hub, topic cluster, topical authority, content architecture, hub and spoke, pillar page, cluster page, content silo, internal linking strategy. Also triggers when a content set is not ranking despite individual piece quality, when a pillar was launched without a cluster, or when content has accumulated without an architecture.","pillar-content-architecture",{"claudeCode":12},"SKILL.md frontmatter at skills/pillar-content-architecture/SKILL.md",[1504,1505,1507,1509,1511,1513,1515,1517,1519,1521,1523],{"path":275,"priority":276},{"path":1506,"priority":279},"references/cluster-piece-anatomy.md",{"path":1508,"priority":279},"references/cluster-planning-patterns.md",{"path":1510,"priority":279},"references/common-pillar-failures.md",{"path":1512,"priority":279},"references/content-refresh-patterns.md",{"path":1514,"priority":279},"references/internal-linking-architecture.md",{"path":1516,"priority":279},"references/pillar-cluster-decision.md",{"path":1518,"priority":279},"references/pillar-page-anatomy.md",{"path":1520,"priority":279},"references/topic-selection-criteria.md",{"path":1522,"priority":279},"references/topical-authority-signals.md",{"path":1524,"priority":279},"references/url-structure-patterns.md",{"basePath":1526,"description":1527,"displayName":1528,"installMethods":1529,"rationale":1530,"selectedPaths":1531,"source":284,"sourceLanguage":18,"type":252},"skills/pm-spec-writing","Translate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.","pm-spec-writing",{"claudeCode":12},"SKILL.md frontmatter at skills/pm-spec-writing/SKILL.md",[1532,1533,1535,1537],{"path":275,"priority":276},{"path":1534,"priority":279},"references/dev-brief-template.md",{"path":1536,"priority":279},"references/feature-spec-template.md",{"path":1538,"priority":279},"references/prioritization-frameworks.md",{"basePath":248,"description":10,"displayName":251,"installMethods":1540,"rationale":1541,"selectedPaths":1542,"source":284,"sourceLanguage":18,"type":252},{"claudeCode":12},"SKILL.md frontmatter at skills/product-analytics-setup/SKILL.md",[1543,1544,1546,1547,1548,1550,1552,1554,1556,1558],{"path":275,"priority":276},{"path":1545,"priority":279},"references/cohort-definition-patterns.md",{"path":999,"priority":279},{"path":374,"priority":279},{"path":1549,"priority":279},"references/funnel-design-templates.md",{"path":1551,"priority":279},"references/instrumentation-audit-checklist.md",{"path":1553,"priority":279},"references/naming-convention-reference.md",{"path":1555,"priority":279},"references/north-star-metric-selection.md",{"path":1557,"priority":279},"references/property-design-patterns.md",{"path":1559,"priority":279},"references/schema-versioning-patterns.md",{"basePath":1561,"description":1562,"displayName":1563,"installMethods":1564,"rationale":1565,"selectedPaths":1566,"source":284,"sourceLanguage":18,"type":252},"skills/product-configurator-design","Designing build-your-own product configurators (Tesla-style, custom-pricing, plan-builders) with constraint logic, real-time pricing, validation, and save-and-share mechanics. Honest about infinite-options (decision paralysis), canned-bundles-only (no real customization), and guided-configuration (smart defaults plus meaningful constraints plus escape hatches) patterns. Triggers on configurator design, build-your-own, custom configuration, plan builder, product customizer, configuration tool. Also triggers when users abandon mid-configuration, when configurator conversion is poor, or when a configurator is being scoped for the first time.","product-configurator-design",{"claudeCode":12},"SKILL.md frontmatter at skills/product-configurator-design/SKILL.md",[1567,1568,1570,1572,1574,1576,1578,1580,1582,1584],{"path":275,"priority":276},{"path":1569,"priority":279},"references/common-configurator-failures.md",{"path":1571,"priority":279},"references/configurator-anti-patterns.md",{"path":1573,"priority":279},"references/configurator-decision-criteria.md",{"path":1575,"priority":279},"references/configurator-to-cart-handoff.md",{"path":1577,"priority":279},"references/constraint-logic-patterns.md",{"path":1579,"priority":279},"references/default-configuration-design.md",{"path":1581,"priority":279},"references/real-time-pricing-patterns.md",{"path":1583,"priority":279},"references/save-and-share-mechanics.md",{"path":1585,"priority":279},"references/validation-and-error-patterns.md",{"basePath":1587,"description":1588,"displayName":1589,"installMethods":1590,"rationale":1591,"selectedPaths":1592,"source":284,"sourceLanguage":18,"type":252},"skills/programmatic-seo","How to design and run a programmatic SEO program that produces durable traffic instead of penalty-bait. Data source identification, template design, schema patterns, quality control at scale, internal linking architecture, crawl budget management, AEO/GEO for programmatic pages, refresh discipline, and the make-or-break question of whether pSEO is the right answer for your program at all. Triggers on programmatic SEO, pSEO, scaled content, page generation, template SEO, location pages, comparison pages, directory site, listing site, scaled landing pages, programmatic content. Also triggers when a content set is not ranking, has been hit by an algorithm update, or when a team is considering pSEO as a growth lever.","programmatic-seo",{"claudeCode":12},"SKILL.md frontmatter at skills/programmatic-seo/SKILL.md",[1593,1594,1596,1598,1600,1602,1604,1606,1608,1610,1612],{"path":275,"priority":276},{"path":1595,"priority":279},"references/aeo-geo-for-programmatic-pages.md",{"path":1597,"priority":279},"references/common-pseo-failures.md",{"path":1599,"priority":279},"references/crawl-budget-management.md",{"path":1601,"priority":279},"references/data-source-identification-patterns.md",{"path":1603,"priority":279},"references/internal-linking-at-scale.md",{"path":1605,"priority":279},"references/quality-control-at-scale.md",{"path":1607,"priority":279},"references/refresh-at-scale.md",{"path":1609,"priority":279},"references/schema-design-patterns.md",{"path":1611,"priority":279},"references/template-design-patterns.md",{"path":1613,"priority":279},"references/when-pseo-works-decision.md",{"basePath":1615,"description":1616,"displayName":1617,"installMethods":1618,"rationale":1619,"selectedPaths":1620,"source":284,"sourceLanguage":18,"type":252},"skills/qa-testing","Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to test a page, audit a site, check for bugs, verify a deploy, run a QA sweep, or review accessibility, performance, or SEO basics. Triggers on test, QA, audit, verify, check, is it working, does it look right, broken, 404, image not loading, post-deploy check, regression test. Also triggers proactively after any significant code change or new page launch where verification matters.","qa-testing",{"claudeCode":12},"SKILL.md frontmatter at skills/qa-testing/SKILL.md",[1621,1622],{"path":275,"priority":276},{"path":1623,"priority":279},"references/qa-report-template.md",{"basePath":1625,"description":1626,"displayName":1627,"installMethods":1628,"rationale":1629,"selectedPaths":1630,"source":284,"sourceLanguage":18,"type":252},"skills/quiz-and-assessment-design","Designing quizzes, personality assessments, and recommendation tools that segment users into actionable categories rather than generating clicks for clicks' sake. Question architecture, scoring algorithms, result categorization, recommendation mapping, lead capture integration. Honest about clickbait-quiz (engagement only), vanity-result (entertaining, not useful), and actionable-segmentation (genuine categorization that drives next-step recommendations) patterns. Triggers on quiz, assessment, personality test, recommendation tool, scorecard, diagnostic, fit evaluator, what-type-of-X-are-you, persona quiz. Also triggers when an audience needs a categorization-driven lead magnet, when a vanity quiz is producing engagement but no qualified leads, or when an assessment is being scoped for the first time.","quiz-and-assessment-design",{"claudeCode":12},"SKILL.md frontmatter at skills/quiz-and-assessment-design/SKILL.md",[1631,1632,1634,1636,1638,1640,1642,1644,1646,1648],{"path":275,"priority":276},{"path":1633,"priority":279},"references/clickbait-vs-actionable-distinctions.md",{"path":1635,"priority":279},"references/common-quiz-failures.md",{"path":1637,"priority":279},"references/lead-capture-integration-patterns.md",{"path":1639,"priority":279},"references/question-architecture-patterns.md",{"path":1641,"priority":279},"references/quiz-anti-patterns.md",{"path":1643,"priority":279},"references/quiz-investment-criteria.md",{"path":1645,"priority":279},"references/result-categorization-patterns.md",{"path":1647,"priority":279},"references/result-to-recommendation-mapping.md",{"path":1649,"priority":279},"references/scoring-algorithm-patterns.md",{"basePath":1651,"description":1652,"displayName":1653,"installMethods":1654,"rationale":1655,"selectedPaths":1656,"source":284,"sourceLanguage":18,"type":252},"skills/roadmap-planning","Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.","roadmap-planning",{"claudeCode":12},"SKILL.md frontmatter at skills/roadmap-planning/SKILL.md",[1657,1658],{"path":275,"priority":276},{"path":1538,"priority":279},{"basePath":1660,"description":1661,"displayName":1662,"installMethods":1663,"rationale":1664,"selectedPaths":1665,"source":284,"sourceLanguage":18,"type":252},"skills/scheduler-and-booking-design","Designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic Calendly link. Availability logic, qualification gating, prep automation, follow-up sequencing. Honest about any-time-friction (no qualification, just a booking link), interrogation-gate (so much qualification it scares users off), and qualified-fast-path (just enough qualification to set up the call well) patterns. Triggers on scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page, qualification flow. Also triggers when sales team complains about cold demos, when booking conversion is poor, or when scheduler is being scoped for the first time.","scheduler-and-booking-design",{"claudeCode":12},"SKILL.md frontmatter at skills/scheduler-and-booking-design/SKILL.md",[1666,1667,1669,1671,1673,1675,1677,1679,1681,1683],{"path":275,"priority":276},{"path":1668,"priority":279},"references/availability-logic-patterns.md",{"path":1670,"priority":279},"references/common-scheduler-failures.md",{"path":1672,"priority":279},"references/prep-automation-patterns.md",{"path":1674,"priority":279},"references/qualification-field-design.md",{"path":1676,"priority":279},"references/reminder-sequence-patterns.md",{"path":1678,"priority":279},"references/reschedule-and-no-show-handling.md",{"path":1680,"priority":279},"references/routing-patterns.md",{"path":1682,"priority":279},"references/scheduler-anti-patterns.md",{"path":1684,"priority":279},"references/scheduler-decision-criteria.md",{"basePath":1686,"description":1687,"displayName":1688,"installMethods":1689,"rationale":1690,"selectedPaths":1691,"source":284,"sourceLanguage":18,"type":252},"skills/security-baseline","Establish a security baseline for a website or web app. Use this skill when configuring HTTPS and TLS, setting security headers, planning secrets management, evaluating CSP policies, doing a basic security audit, or hardening a site before launch. Triggers on security headers, HTTPS, TLS, CSP, content security policy, HSTS, secrets management, vulnerability scan, security audit, harden, OWASP, security baseline. Also triggers when a security review is required for compliance or before going live.","security-baseline",{"claudeCode":12},"SKILL.md frontmatter at skills/security-baseline/SKILL.md",[1692,1693],{"path":275,"priority":276},{"path":1694,"priority":279},"references/headers-checklist.md",{"basePath":1696,"description":1697,"displayName":1698,"installMethods":1699,"rationale":1700,"selectedPaths":1701,"source":284,"sourceLanguage":18,"type":252},"skills/seo-aeo-geo","Optimize content and site structure for AI-driven search experiences including AI overviews, large language model citations, generative answer engines, and AI assistants. Use this skill whenever the user wants to optimize for AI search, get cited by language models, appear in AI overviews, build llms.txt, structure content for AI extraction, or future-proof their SEO for the shift from blue links to AI answers. Triggers on AEO, GEO, AI search, AI SEO, AI overview, generative search, LLM optimization, llms.txt, AI citation, ChatGPT search, Perplexity, Gemini, Claude search, AI assistant optimization, answer engine. Also triggers when the user expresses concern about AI eating their organic traffic or wants to understand how to remain visible as search shifts.","seo-aeo-geo",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-aeo-geo/SKILL.md",[1702,1703,1705],{"path":275,"priority":276},{"path":1704,"priority":279},"references/extraction-friendly-patterns.md",{"path":1706,"priority":279},"references/llms-txt-guide.md",{"basePath":1708,"description":1709,"displayName":1710,"installMethods":1711,"rationale":1712,"selectedPaths":1713,"source":284,"sourceLanguage":18,"type":252},"skills/seo-audit-orchestration","Master orchestrator for a full SEO audit suite powered by the Ahrefs MCP. Use this skill when running a comprehensive SEO audit, scoping a quarterly health check, doing pre-acquisition SEO due diligence, or post-migration verification. Triggers on full SEO audit, comprehensive SEO review, SEO health check, audit my site, SEO due diligence, audit suite, comprehensive audit, end-to-end SEO. Also triggers when a stakeholder wants the complete picture rather than a single-dimension audit.","seo-audit-orchestration",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-audit-orchestration/SKILL.md",[1714,1715],{"path":275,"priority":276},{"path":1716,"priority":279},"references/audit-rollup-template.md",{"basePath":1718,"description":1719,"displayName":1720,"installMethods":1721,"rationale":1722,"selectedPaths":1723,"source":284,"sourceLanguage":18,"type":252},"skills/seo-backlink-audit","Audit a backlink profile using Ahrefs MCP data: profile health, anchor text distribution, toxic link identification, lost link reclamation, and gap analysis against competitors. Use this skill when reviewing backlink health, scoping a disavow project, recovering from a manual action, planning link building, or doing M&A due diligence on a property's link equity. Triggers on backlink audit, link profile, toxic links, disavow, anchor text analysis, lost links, link reclamation, referring domains, link gap. Also triggers when traffic decline correlates with link loss or when an unnatural link warning appears in Search Console.","seo-backlink-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-backlink-audit/SKILL.md",[1724,1725],{"path":275,"priority":276},{"path":1726,"priority":279},"references/toxic-link-criteria.md",{"basePath":1728,"description":1729,"displayName":1730,"installMethods":1731,"rationale":1732,"selectedPaths":1733,"source":284,"sourceLanguage":18,"type":252},"skills/seo-competitor","Run a competitive SEO analysis comparing the user's site to chosen competitors across SERP overlap, content depth, backlink profiles, technical posture, and brand presence. Use this skill whenever the user wants to analyze competitors, find content gaps, identify backlink opportunities, understand why competitors outrank them, or benchmark against the rest of their category. Triggers on competitor analysis, competitive analysis, SERP analysis, content gap, backlink gap, why is X ranking, who is winning the SERP, beat my competitor, benchmark, market positioning. Also triggers when planning a content strategy and the question 'what are competitors doing' is implicit.","seo-competitor",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-competitor/SKILL.md",[1734,1735,1737],{"path":275,"priority":276},{"path":1736,"priority":279},"references/competitive-audit-template.md",{"path":1738,"priority":279},"references/content-gap-method.md",{"basePath":1740,"description":1741,"displayName":1742,"installMethods":1743,"rationale":1744,"selectedPaths":1745,"source":284,"sourceLanguage":18,"type":252},"skills/seo-content-audit","Audit existing content across a site to decide what to keep, update, merge, redirect, or delete. Use this skill whenever the user wants to audit existing content, fix content decay, resolve keyword cannibalization, prune underperforming pages, prioritize content updates, or apply a keep/update/merge/redirect/delete framework to a content library. Triggers on content audit, content decay, content refresh, cannibalization, keyword cannibalization, prune content, delete pages, redirect old pages, content inventory, what to keep, what to update, content scorecard, evergreen refresh. Also triggers when traffic is dropping site-wide and the cause might be content quality, even if 'audit' is not said explicitly.","seo-content-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-content-audit/SKILL.md",[1746,1747,1748],{"path":275,"priority":276},{"path":1492,"priority":279},{"path":1749,"priority":279},"references/cannibalization-resolution.md",{"basePath":1751,"description":1752,"displayName":1753,"installMethods":1754,"rationale":1755,"selectedPaths":1756,"source":284,"sourceLanguage":18,"type":252},"skills/seo-content-gap-audit","Audit content gaps and decay using Ahrefs MCP data: missing topics, thin coverage, outdated content, and decaying pages. Use this skill when planning a content roadmap, refreshing a stale catalog, building topical authority, or identifying which existing pages need update versus replacement. Triggers on content gap, content audit, content refresh, content roadmap, decaying content, content decay, topical authority, what topics should we cover, where is competitor content stronger. Also triggers when organic traffic is flat despite consistent publishing.","seo-content-gap-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-content-gap-audit/SKILL.md",[1757,1758],{"path":275,"priority":276},{"path":1759,"priority":279},"references/content-decision-matrix.md",{"basePath":1761,"description":1762,"displayName":1763,"installMethods":1764,"rationale":1765,"selectedPaths":1766,"source":284,"sourceLanguage":18,"type":252},"skills/seo-keyword","Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production. Use this skill whenever the user asks to do keyword research, find target keywords, identify ranking opportunities, classify search intent, build a topical map, or plan a content strategy around what people search for. Triggers on keyword research, keyword strategy, search intent, keyword clustering, topic clusters, keyword difficulty, search volume, ranking opportunity, content gap, what should I write about, target keyword, primary keyword, secondary keyword, long-tail. Also triggers when planning a content calendar or new site without keywords yet defined.","seo-keyword",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-keyword/SKILL.md",[1767,1768,1770],{"path":275,"priority":276},{"path":1769,"priority":279},"references/intent-classification-guide.md",{"path":1771,"priority":279},"references/keyword-research-template.md",{"basePath":1773,"description":1774,"displayName":1775,"installMethods":1776,"rationale":1777,"selectedPaths":1778,"source":284,"sourceLanguage":18,"type":252},"skills/seo-keyword-gap-audit","Find keywords competitors rank for that the target property does not, and prioritize them by opportunity. Uses Ahrefs MCP for keyword and competitor data. Use this skill when planning content investment, identifying quick wins, building a content calendar against a competitor set, or scoping a market entry. Triggers on keyword gap, content gap, competitor keywords, opportunity keywords, what should we target, where are competitors winning, keyword opportunity. Also triggers when planning content for a new market or after losing organic share to a specific competitor.","seo-keyword-gap-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-keyword-gap-audit/SKILL.md",[1779,1780],{"path":275,"priority":276},{"path":1781,"priority":279},"references/opportunity-scoring-rubric.md",{"basePath":1783,"description":1784,"displayName":1785,"installMethods":1786,"rationale":1787,"selectedPaths":1788,"source":284,"sourceLanguage":18,"type":252},"skills/seo-offpage","Plan and execute off-page SEO including link building, digital PR, brand mentions, citation building, and external authority signals. Use this skill whenever the user wants to build backlinks, plan a digital PR campaign, list local citations, run guest post outreach, develop linkable assets, recover lost links, or audit a backlink profile for risk. Triggers on link building, backlinks, digital PR, brand mentions, citation building, guest post, outreach, linkable asset, broken link building, HARO, podcast outreach, off-page SEO, anchor text, link velocity, toxic backlinks, disavow. Also triggers when the user is trying to grow domain authority or earn coverage.","seo-offpage",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-offpage/SKILL.md",[1789,1790,1792],{"path":275,"priority":276},{"path":1791,"priority":279},"references/linkable-assets-guide.md",{"path":1793,"priority":279},"references/outreach-templates.md",{"basePath":1795,"description":1796,"displayName":1797,"installMethods":1798,"rationale":1799,"selectedPaths":1800,"source":284,"sourceLanguage":18,"type":252},"skills/seo-onpage","Run a comprehensive on-page SEO audit or optimization pass covering title tags, meta descriptions, header structure, content quality, internal links, image optimization, URL hygiene, and on-page schema. Use this skill whenever the user asks to optimize a page, audit on-page SEO, fix titles or meta tags, review header structure, check internal linking, improve a single URL's search performance, or write SEO-friendly copy. Triggers on on-page SEO, page audit, title tag, meta description, H1, header structure, internal links, image alt, URL slug, page optimization, optimize this page, SEO this page. Also triggers for any single-page review where ranking, click-through, or relevance signal quality is the goal, even if the user does not say 'SEO' explicitly.","seo-onpage",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-onpage/SKILL.md",[1801,1802,1803,1805],{"path":275,"priority":276},{"path":1492,"priority":279},{"path":1804,"priority":279},"references/onpage-checklist.md",{"path":1806,"priority":279},"references/title-and-meta-patterns.md",{"basePath":1808,"description":1809,"displayName":1810,"installMethods":1811,"rationale":1812,"selectedPaths":1813,"source":284,"sourceLanguage":18,"type":252},"skills/seo-rank-tracking","Set up and run rank tracking using Ahrefs MCP: pick the right keywords to track, segment them by purpose, set baselines, and define alert thresholds. Use this skill when starting a new tracking project, baselining for a campaign, choosing what to monitor, or building a rank reporting cadence. Triggers on rank tracking, keyword tracking, monitor rankings, track positions, what should we track, ranking dashboard, baseline rankings, alert thresholds. Also triggers when a stakeholder wants weekly or monthly ranking visibility.","seo-rank-tracking",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-rank-tracking/SKILL.md",[1814,1815],{"path":275,"priority":276},{"path":1816,"priority":279},"references/dashboard-template.md",{"basePath":1818,"description":1819,"displayName":1820,"installMethods":1821,"rationale":1822,"selectedPaths":1823,"source":284,"sourceLanguage":18,"type":252},"skills/seo-site-health-audit","Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity. Use this skill when reviewing crawl results, prioritizing technical fixes, scoping a technical SEO sprint, or after running any site-wide crawl. Triggers on site audit results, technical fix list, crawl errors, technical SEO triage, prioritize technical issues, what should we fix first, broken links, redirect chains. Also triggers when a long list of crawler issues is creating decision paralysis.","seo-site-health-audit",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-site-health-audit/SKILL.md",[1824,1825],{"path":275,"priority":276},{"path":1826,"priority":279},"references/issue-impact-table.md",{"basePath":1828,"description":1829,"displayName":1830,"installMethods":1831,"rationale":1832,"selectedPaths":1833,"source":284,"sourceLanguage":18,"type":252},"skills/seo-technical","Run a comprehensive technical SEO audit covering crawlability, indexability, rendering, site architecture, structured data, page experience, security, and internationalization. Use this skill whenever the user asks about technical SEO, crawl issues, indexing problems, sitemaps, robots.txt, canonical tags, schema markup, page speed, Core Web Vitals, hreflang, redirects, or site-wide search performance. Triggers on technical SEO, site audit, crawlability, indexability, sitemap, robots.txt, canonical, redirect chain, schema, JSON-LD, Core Web Vitals, page speed, hreflang, mobile usability, HTTPS, security headers, render-blocking, JavaScript SEO. Also triggers when a site has indexing problems, traffic drops, or migration concerns, even if 'technical SEO' is not said explicitly.","seo-technical",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-technical/SKILL.md",[1834,1835,1836],{"path":275,"priority":276},{"path":1492,"priority":279},{"path":1837,"priority":279},"references/migration-checklist.md",{"basePath":1839,"description":1840,"displayName":1841,"installMethods":1842,"rationale":1843,"selectedPaths":1844,"source":284,"sourceLanguage":18,"type":252},"skills/seo-traffic-diagnosis","Diagnose organic traffic changes (drops, stalls, or unexpected wins) using Ahrefs MCP plus Search Console data. Use this skill when traffic suddenly dropped, has been flat despite investment, after an algorithm update, after a migration or deploy, or when a competitor seems to be taking share. Triggers on traffic dropped, traffic decline, traffic stalled, organic decline, lost rankings, why is traffic down, algorithm update, post-migration traffic loss, traffic diagnosis. Also triggers when stakeholders are panicking about analytics.","seo-traffic-diagnosis",{"claudeCode":12},"SKILL.md frontmatter at skills/seo-traffic-diagnosis/SKILL.md",[1845,1846],{"path":275,"priority":276},{"path":1847,"priority":279},"references/diagnosis-checklist.md",{"basePath":1849,"description":1850,"displayName":1851,"installMethods":1852,"rationale":1853,"selectedPaths":1854,"source":284,"sourceLanguage":18,"type":252},"skills/skill-creation-walkthrough","Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not triggering or not loading the right context, when you are auditing a skill that is underperforming, or when you want to publish a skill for others. Also triggers when someone asks \"how do I make a skill\" or \"what makes a good skill\". Useful for individuals, teams, and anyone publishing skills publicly.","skill-creation-walkthrough",{"claudeCode":12},"SKILL.md frontmatter at skills/skill-creation-walkthrough/SKILL.md",[1855,1856,1858,1860],{"path":275,"priority":276},{"path":1857,"priority":279},"references/description-cookbook.md",{"path":1859,"priority":279},"references/methodology-vs-implementation.md",{"path":1861,"priority":279},"references/skill-template.md",{"basePath":1863,"description":1864,"displayName":1865,"installMethods":1866,"rationale":1867,"selectedPaths":1868,"source":284,"sourceLanguage":18,"type":252},"skills/stakeholder-communication","Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.","stakeholder-communication",{"claudeCode":12},"SKILL.md frontmatter at skills/stakeholder-communication/SKILL.md",[1869,1870],{"path":275,"priority":276},{"path":1871,"priority":279},"references/update-templates.md",{"basePath":1873,"description":1874,"displayName":1875,"installMethods":1876,"rationale":1877,"selectedPaths":1878,"source":284,"sourceLanguage":18,"type":252},"skills/team-onboarding-playbook","Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also triggers when one person owns all the tribal knowledge and you need to capture it, when you keep losing people in their first 90 days, or when a new project has many fresh members joining at once. Useful for engineering, design, product, marketing, and operations roles.","team-onboarding-playbook",{"claudeCode":12},"SKILL.md frontmatter at skills/team-onboarding-playbook/SKILL.md",[1879,1880],{"path":275,"priority":276},{"path":1881,"priority":279},"references/onboarding-checklist.md",{"basePath":1883,"description":1884,"displayName":1885,"installMethods":1886,"rationale":1887,"selectedPaths":1888,"source":284,"sourceLanguage":18,"type":252},"skills/upgrade-flow-design","Designing free-to-paid conversion flows for SaaS products. Trigger moments, paywall design, value demonstration, upsell vs downsell, win-back flows, churn prevention. Honest about paywall-everywhere (gates everything aggressively), free-forever-trap (no upgrade path surfaces), and value-triggered-upgrade (paywall surfaces at moments of demonstrated value) patterns. Triggers on upgrade flow, paywall, free-to-paid, freemium conversion, trial conversion, plan upgrade, subscription upgrade, win-back flow, churn prevention. Also triggers when free-to-paid conversion is low, when paywalls are blocking the wrong moments, or when upgrade flows are being scoped for the first time.","upgrade-flow-design",{"claudeCode":12},"SKILL.md frontmatter at skills/upgrade-flow-design/SKILL.md",[1889,1890,1892,1894,1896,1898,1900,1902,1904,1906],{"path":275,"priority":276},{"path":1891,"priority":279},"references/churn-prevention-upstream.md",{"path":1893,"priority":279},"references/common-upgrade-failures.md",{"path":1895,"priority":279},"references/free-tier-decision-criteria.md",{"path":1897,"priority":279},"references/paywall-presentation-patterns.md",{"path":1899,"priority":279},"references/plan-structure-patterns.md",{"path":1901,"priority":279},"references/trigger-moment-design.md",{"path":1903,"priority":279},"references/upgrade-flow-anti-patterns.md",{"path":1905,"priority":279},"references/upsell-vs-downsell-logic.md",{"path":1907,"priority":279},"references/win-back-flow-patterns.md",{"basePath":1909,"description":1910,"displayName":1911,"installMethods":1912,"rationale":1913,"selectedPaths":1914,"source":284,"sourceLanguage":18,"type":252},"skills/usability-testing","Plan and run usability tests on existing or prototype designs including test design, task scripts, moderation, observation, and findings synthesis. Use this skill whenever the user wants to test usability, run a moderated test, run an unmoderated test, validate a design, find usability issues, or improve task completion. Triggers on usability test, usability testing, moderated test, unmoderated test, task script, think aloud, prototype testing, user testing, design validation, task completion. Also triggers when the user has built something and wants to know if real users can use it before shipping.","usability-testing",{"claudeCode":12},"SKILL.md frontmatter at skills/usability-testing/SKILL.md",[1915,1916],{"path":275,"priority":276},{"path":1917,"priority":279},"references/task-script-patterns.md",{"basePath":1919,"description":1920,"displayName":1921,"installMethods":1922,"rationale":1923,"selectedPaths":1924,"source":284,"sourceLanguage":18,"type":252},"skills/user-feedback-aggregation","Collecting and synthesizing user feedback across channels (support tickets, NPS, in-app feedback, sales calls, social mentions, customer councils) into a continuous signal that informs product decisions. The triage discipline that distinguishes loudest-voice (whoever complains most wins) from averaged-noise (every signal weighted equally) from triaged-synthesis (signal weighted by source quality, frequency, and decision relevance). Triggers on user feedback, customer feedback aggregation, NPS, support ticket analysis, customer councils, feedback synthesis, voice of customer, feedback triage, in-app feedback. Also triggers when feedback channels overflow with volume that does not produce decisions, when the loudest-voice problem is steering roadmap, or when continuous feedback streams need synthesis discipline.","user-feedback-aggregation",{"claudeCode":12},"SKILL.md frontmatter at skills/user-feedback-aggregation/SKILL.md",[1925,1926,1928,1930,1932,1934,1936,1938,1940,1942],{"path":275,"priority":276},{"path":1927,"priority":279},"references/categorization-and-tagging-at-scale.md",{"path":1929,"priority":279},"references/channel-source-weighting.md",{"path":1931,"priority":279},"references/channel-types-and-what-each-surfaces.md",{"path":1933,"priority":279},"references/closing-the-loop-with-users.md",{"path":1935,"priority":279},"references/common-feedback-aggregation-failures.md",{"path":1937,"priority":279},"references/detecting-drift-in-feedback.md",{"path":1939,"priority":279},"references/frequency-vs-intensity.md",{"path":1941,"priority":279},"references/from-feedback-to-product-decision.md",{"path":1943,"priority":279},"references/tooling-considerations.md",{"basePath":1945,"description":1946,"displayName":1947,"installMethods":1948,"rationale":1949,"selectedPaths":1950,"source":284,"sourceLanguage":18,"type":252},"skills/ux-research","Plan and execute user research including research planning, recruiting, interview design, qualitative synthesis, and translating findings into product decisions. Use this skill whenever the user wants to plan user research, design interviews, recruit participants, conduct discovery, run formative research, or synthesize qualitative findings. Triggers on user research, UX research, user interviews, discovery research, generative research, formative research, qualitative research, user insights, research synthesis, recruitment, interview guide, jobs to be done. Also triggers when product decisions are being made without user input and the user wants to fix that.","ux-research",{"claudeCode":12},"SKILL.md frontmatter at skills/ux-research/SKILL.md",[1951,1952],{"path":275,"priority":276},{"path":1953,"priority":279},"references/interview-guide-template.md",{"basePath":1955,"description":1956,"displayName":1957,"installMethods":1958,"rationale":1959,"selectedPaths":1960,"source":284,"sourceLanguage":18,"type":252},"skills/vendor-evaluation","Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor scorecard, vendor comparison, contract negotiation, vendor switch, procurement. Also triggers when a renewal is coming up or when a tool isn't meeting expectations.","vendor-evaluation",{"claudeCode":12},"SKILL.md frontmatter at skills/vendor-evaluation/SKILL.md",[1961,1962],{"path":275,"priority":276},{"path":1963,"priority":279},"references/evaluation-rubric.md",{"sources":1965},[1966],"manual",{"closedIssues90d":8,"description":1968,"forks":238,"homepage":1969,"license":243,"openIssues90d":8,"pushedAt":240,"readmeSize":236,"stars":241,"topics":1970},"Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize.","https://rampstack.co/",[1971,250,1972,1973,1974,1975,1976,1977,1978,1979,1980,1981,1982,1983,1984,1985,1986],"claude","anthropic","mcp","seo","web-development","agent-skills","claude-code","awesome-claude-code","awesome-claude-prompts","awesome-claude-skills","good-first-issue","show-hn","showdev","showcase","product-management","web-design",{"classifiedAt":1988,"discoverAt":1989,"extractAt":1990,"githubAt":1990,"updatedAt":1988},1778696112696,1778696105594,1778696110743,[220,219,218,221,222],{"evaluatedAt":246,"extractAt":1993,"updatedAt":246},1778696113180,[],[1996,2027,2056,2083,2111,2141],{"_creationTime":1997,"_id":1998,"community":1999,"display":2000,"identity":2006,"providers":2011,"relations":2021,"tags":2023,"workflow":2024},1778696691708.3035,"k17br1j5s86ae90zqeyd7zcg2586mkwr",{"reviewCount":8},{"description":2001,"installMethods":2002,"name":2004,"sourceUrl":2005},"Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms\n",{"claudeCode":2003},"ruvnet/ruflo","Performance Analysis","https://github.com/ruvnet/ruflo",{"basePath":2007,"githubOwner":2008,"githubRepo":2009,"locale":18,"slug":2010,"type":252},".claude/skills/performance-analysis","ruvnet","ruflo","performance-analysis",{"evaluate":2012,"extract":2020},{"promptVersionExtension":211,"promptVersionScoring":212,"score":2013,"tags":2014,"targetMarket":223,"tier":224},100,[2015,2016,2017,2018,2019,221],"performance","analysis","optimization","claude-flow","bottleneck-detection",{"commitSha":258,"license":243},{"repoId":2022},"kd7ed28gj8n0y3msk5dzrp05zs86nqtc",[2016,2019,2018,2017,2015,221],{"evaluatedAt":2025,"extractAt":2026,"updatedAt":2025},1778699217174,1778696691708,{"_creationTime":2028,"_id":2029,"community":2030,"display":2031,"identity":2037,"providers":2041,"relations":2049,"tags":2052,"workflow":2053},1778698144006.2202,"k172517ana4f5vj79mb22xzwsx86mksv",{"reviewCount":8},{"description":2032,"installMethods":2033,"name":2035,"sourceUrl":2036},"Audit and consolidate HubSpot reporting dashboards. Identifies unused, duplicate, or outdated dashboards. Must be performed manually — no dashboard API is available.",{"claudeCode":2034},"TomGranot/hubspot-admin-skills","cleanup-dashboards","https://github.com/TomGranot/hubspot-admin-skills",{"basePath":2038,"githubOwner":2039,"githubRepo":2040,"locale":18,"slug":2035,"type":252},"skills/cleanup-dashboards","TomGranot","hubspot-admin-skills",{"evaluate":2042,"extract":2048},{"promptVersionExtension":211,"promptVersionScoring":212,"score":2013,"tags":2043,"targetMarket":223,"tier":224},[2044,2045,2046,221,2047],"hubspot","crm","maintenance","cleanup",{"commitSha":258},{"parentExtensionId":2050,"repoId":2051},"k17c3p8t0thc73pbc8egtz31y986mwr0","kd75kpec7arn6z2wz641vfaj8n86nab6",[2047,2045,2044,2046,221],{"evaluatedAt":2054,"extractAt":2055,"updatedAt":2054},1778698268281,1778698144006,{"_creationTime":2057,"_id":2058,"community":2059,"display":2060,"identity":2066,"providers":2070,"relations":2076,"tags":2079,"workflow":2080},1778694480889.9524,"k17cem4hc58gq77dezte6rz8mx86nkpf",{"reviewCount":8},{"description":2061,"installMethods":2062,"name":2064,"sourceUrl":2065},"Display the current state of the FPF knowledge base",{"claudeCode":2063},"NeoLabHQ/context-engineering-kit","status","https://github.com/NeoLabHQ/context-engineering-kit",{"basePath":2067,"githubOwner":2068,"githubRepo":2069,"locale":18,"slug":2064,"type":252},"plugins/fpf/skills/status","NeoLabHQ","context-engineering-kit",{"evaluate":2071,"extract":2075},{"promptVersionExtension":211,"promptVersionScoring":212,"score":2013,"tags":2072,"targetMarket":223,"tier":224},[2073,2064,221,2074],"knowledge-base","fpf",{"commitSha":258},{"parentExtensionId":2077,"repoId":2078},"k170dd9j7raacsjs3ta67k8cw986m50s","kd7a3rj13ezgx1wgm0jfh08hsx86n0sz",[2074,2073,221,2064],{"evaluatedAt":2081,"extractAt":2082,"updatedAt":2081},1778695034738,1778694480890,{"_creationTime":2084,"_id":2085,"community":2086,"display":2087,"identity":2093,"providers":2097,"relations":2104,"tags":2107,"workflow":2108},1778692726926.7627,"k17dhmskz6t7wpxvd9ygy7fvsh86n695",{"reviewCount":8},{"description":2088,"installMethods":2089,"name":2091,"sourceUrl":2092},"End-of-quarter strategic review in narrative style with a bets scorecard. Use when someone says \"quarter review\", \"strategic review\", \"what happened last quarter\", \"quarterly retro\", \"bets scorecard\", \"review our bets\", \"end of quarter report\".\n",{"claudeCode":2090},"marfoerst/the-pragmatic-pm","pm-strategic-review","https://github.com/marfoerst/the-pragmatic-pm",{"basePath":2094,"githubOwner":2095,"githubRepo":2096,"locale":18,"slug":2091,"type":252},"skills/pm-strategic-review","marfoerst","the-pragmatic-pm",{"evaluate":2098,"extract":2103},{"promptVersionExtension":211,"promptVersionScoring":212,"score":2013,"tags":2099,"targetMarket":223,"tier":224},[1985,2100,221,2101,2102],"strategy","review","scorecard",{"commitSha":258},{"parentExtensionId":2105,"repoId":2106},"k17ehawghqbe3ff7rxmq9cq1xs86nm21","kd731k864fr1ezp8r85ecbhz9986mzz7",[1985,221,2101,2102,2100],{"evaluatedAt":2109,"extractAt":2110,"updatedAt":2109},1778693621016,1778692726926,{"_creationTime":2112,"_id":2113,"community":2114,"display":2115,"identity":2121,"providers":2125,"relations":2134,"tags":2137,"workflow":2138},1778692306427.1023,"k17f0vqhj9x3ee4773kq2m8fph86n5ct",{"reviewCount":8},{"description":2116,"installMethods":2117,"name":2119,"sourceUrl":2120},"Revenue and costs tracker. AWS spend via aws ce, credits tracker, project revenue stages. Shows burn rate, runway estimate, credits expiring.",{"claudeCode":2118},"Lifecycle-Innovations-Limited/claude-ops","ops-revenue","https://github.com/Lifecycle-Innovations-Limited/claude-ops",{"basePath":2122,"githubOwner":2123,"githubRepo":2124,"locale":18,"slug":2119,"type":252},"claude-ops/skills/ops-revenue","Lifecycle-Innovations-Limited","claude-ops",{"evaluate":2126,"extract":2133},{"promptVersionExtension":211,"promptVersionScoring":212,"score":2013,"tags":2127,"targetMarket":223,"tier":224},[2128,2129,2130,2131,221,2132],"finance","aws","cost-tracking","revenue","dashboard",{"commitSha":258},{"parentExtensionId":2135,"repoId":2136},"k17d0t6ns7y6t377pfprg128hd86nm89","kd7d52tcek2e34r805zs06b10d86n39v",[2129,2130,2132,2128,221,2131],{"evaluatedAt":2139,"extractAt":2140,"updatedAt":2139},1778692873720,1778692306427,{"_creationTime":2142,"_id":2143,"community":2144,"display":2145,"identity":2151,"providers":2156,"relations":2164,"tags":2167,"workflow":2168},1778692707070.0664,"k1745c75pw18shtjfgm186w7zn86mb7q",{"reviewCount":8},{"description":2146,"installMethods":2147,"name":2149,"sourceUrl":2150},"用于 README 优先的 AI 代码库进行可信执行和报告的技能。当任务是专门从选定的 smoke test 或已文档化的推理或评估命令捕获或标准化证据，并写入标准化的 `repro_outputs/` 文件（包括在存储库文件更改时生成补丁说明）时使用。请勿用于训练执行、初始代码库引入、通用环境设置、论文查找、目标选择或单独的端到端编排。",{"claudeCode":2148},"lllllllama/ai-paper-reproduction-skill","minimal-run-and-audit","https://github.com/lllllllama/ai-paper-reproduction-skill",{"basePath":2152,"githubOwner":2153,"githubRepo":2154,"locale":2155,"slug":2149,"type":252},"skills/minimal-run-and-audit","lllllllama","ai-paper-reproduction-skill","zh-CN",{"evaluate":2157,"extract":2163},{"promptVersionExtension":211,"promptVersionScoring":212,"score":2013,"tags":2158,"targetMarket":223,"tier":224},[2159,2160,221,2161,2162],"reproduction","testing","code-execution","evidence-capture",{"commitSha":258},{"repoId":2165,"translatedFrom":2166},"kd7629v5mqesxwwe9w7qtfgp7d86n6re","k1718b6r9230y7ft3t8gkmsg2986my9z",[2161,2162,221,2159,2160],{"evaluatedAt":2169,"extractAt":2170,"updatedAt":2171},1778692567369,1778692396032,1778692707070]