
Claude Skills by KevinZai
github.com/KevinZaiGenerate bulk pages for SEO programmatic content. Creates templated pages for location-based, comparison, alternative, integration, and use-case pages. Designed for MyWiFi Networks and DMHub marketing sites. Agents can use this for autonomous SEO content creation.
Topic cluster strategy — pillar pages, cluster content, and internal linking maps
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produc...
基于项目内容分析主题和关键词,生成客座博客搜索策略。提供 Google 高级搜索语法、客座博客资源列表(从 resources/guest-blog-sources.md 读取)和投稿邮件模板(从 templates/guest-blog-pitch.md 读取)。自动评估客座博客质量(DA、相关性、流量),提供个性化的投稿建议和优先级排序。
Pull Google Search Console data and perform search performance analysis. Use when asked about search rankings, clicks, impressions, CTR, index coverage, Core Web Vitals, or sitemap status. Trigger phrases: "search console", "GSC", "search performance", "clicks and impressions", "CTR analysis", "index coverage", "core web vitals", "URL inspection", "sitemap status", "ranking data", "search queries", "keyword positions".
Create an SEO content brief for writers. Use when the user says "content brief", "SEO brief", "writing brief", "brief for", "writer brief", "outline for SEO", or asks about creating a structured brief to hand to a writer for producing search-optimized content.
Captures domain SEO state — current rankings, competitors, tools, goals
Unified SEO health dashboard — combines technical, content, backlinks, and performance data
Technical SEO and GEO optimization for Next.js + shadcn/ui projects. Meta tags, Open Graph, JSON-LD structured data, sitemaps, robots.txt, Core Web Vitals, local/GEO SEO, hreflang, canonical URLs, and keyword optimization. Use when: user wants SEO, meta tags, structured data, sitemap, local SEO, or search optimization.
Routes SEO requests to the right specialist skill within ccc-seo
Analyze Google search results (SERP) for any keyword. Use when the user says "analyze the SERP", "what ranks for", "SERP analysis", "competitive analysis for keyword", "content brief", "what's ranking", "search results for", "who ranks for", or asks about ranking content patterns for a keyword.
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what p...
Add social media integration to Next.js + shadcn/ui projects. Open Graph previews, Twitter cards, social share buttons, embed feeds (X, Instagram), Discord widget, social proof counters, and share tracking. Use when: user wants social sharing, OG tags, embedded social feeds, share buttons, or social proof.
CCC domain — complete testing ecosystem — 15 skills in one. TDD, E2E, verification, QA, regression, visual testing, and load testing.
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
Load testing with k6 and Artillery — scripts, scenarios, thresholds, CI integration, bottleneck analysis.
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix ...
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
Generates a complete testing strategy for any project — analyzes codebase, recommends test types, sets coverage targets.
Routes your testing task to the right specialist skill within ccc-testing.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
A comprehensive verification system for Claude Code sessions.
Visual regression testing patterns — screenshot comparison, Percy, Chromatic, baseline management, CI integration.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Build a real-time support chat system with a floating widget for users and an admin dashboard for support staff. Use when the user wants live chat, customer support chat, real-time messaging, or in-app support.
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscriber...
Build apps with the Claude API or Anthropic SDK. TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`/`claude_agent_sdk`, or user asks to use Claude API, Anthropic SDKs, or Agent SDK. DO NOT TRIGGER when: code imports `openai`/other AI SDK, general programming, or ML/data-science tasks.
Analyze and refresh CLAUDE.md files against the latest CC Commander template
Persistent AI memory across Claude Code sessions — semantic search, auto-capture, knowledge compounding. Use when the user says 'remember this', 'search memory', 'what do we know about', 'install memory'.
Master guide to Claude Peers — the built-in MCP server for multi-instance communication, coordination, and parallel development workflows
Audit your CLAUDE.md against the actual codebase — find stale instructions, missing context, and optimization opportunities. Use when 'audit claude md', 'check claude md', 'is my claude md accurate', 'optimize instructions'.
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
CloudCLI — bridge to web-based Claude Code sessions for mobile access
OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex".
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs...
Shared state bridge between Claude Chat, Cowork, and Code. Uses markdown files at ~/.claude/compass/ as the synchronization layer. Tasks and state persist across all Claude surfaces without needing a database or MCP server.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, yo...
Pre-execution confidence assessment. Rate confidence 0-100% across 4 dimensions before proceeding with any plan. Prevents wrong-direction work and saves tokens. Inspired by SuperClaude Framework's confidence checking pattern.
Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
Visual context window budget analyzer — shows usage gauge, identifies bloat sources, recommends when to save session and compact
Fetch curated API documentation using the chub CLI before writing code. Use when calling external APIs (OpenAI, Stripe, Anthropic, etc.) to get accurate docs instead of hallucinating. Install chub via: npm install -g chub
Tool output sandboxing — 98% context reduction via FTS5
Proactive contextual suggestion system with 5 configurable levels. Monitors user activity (file types, commands, errors) and suggests relevant CCC domains, commands, and prompts at natural breakpoints. Respects assistance level from bible-config.json or KZ_ASSIST_LEVEL env var.
Daily scan for new Claude Code techniques and best practices. Multi-agent approval pipeline routes GitHub/npm findings through evaluator and security agents before queueing.