Claude Skills
The open format is called Agent Skills and works in Claude Code, Codex, Cursor and other agents — most people know it as Claude Skills.
Every Agent Skill we could find on GitHub, deduplicated by content. 79 341 files from 1 736 authors, of which 61 700 are unique — the rest is the same skill repackaged into someone else's repository. For each one: what it weighs in tokens, whether it ships runnable scripts, and which MCP servers it needs.
Use when reviewing GitHub pull requests with gh CLI - creates pending reviews with code suggestions, batches comments, and chooses appropriate event types (COMMENT/APPROVE/REQUEST_CHANGES)
Generate a Kafka consumer group lag dashboard. Use when the user asks to monitor lag, build a dashboard for consumer lag, or wire up Prometheus exporters for Kafka. Do NOT trigger for producer metrics, broker JMX, or Streams-specific monitoring.
Enrich a customer-orders stream with loyalty tier using Flink SQL on Confluent Cloud. Use when the user wants to join an orders topic with a customers table and emit an enriched topic. Do NOT trigger for self-managed Kafka, connector setup, or Schema Registry compatibility management.
Helps with stuff.
Set up end-to-end Change Data Capture (CDC) pipelines on Confluent Cloud using Debezium source connectors, Flink for transformation, and Tableflow for data lake integration. Supports JSON_SR, Avro, and Protobuf formats. Handles schemaless topics (plain JSON without SR) and multi-event topics. This skill handles the complete workflow from database to Iceberg/Delta tables. Use this skill when users want to capture database changes and materialize them into Iceberg or Delta Lake tables via Confluent Cloud Tableflow. Trigger phrases include "CDC to Tableflow", "database to Iceberg", "database to Delta Lake", "stream database changes to data lake", "set up Tableflow pipeline", "schemaless topic to Tableflow", or "multi-event topic to Iceberg". Do NOT trigger for general CDC, Debezium, or database replication requests that do not involve Tableflow or Iceberg/Delta Lake as the destination.
Review a Confluent agent skill in this repo against the Agent Skills spec (agentskills.io), Confluent conventions in CLAUDE.md, the PR template gates, and the evals-as-contract rule. Use this skill whenever the user asks to review, audit, validate, or lint a skill; opens or inspects a PR that adds or modifies anything under `skills/`; asks about spec conformance, lazy-loading, frontmatter shape, trigger overlap, or eval coverage; or wants a pre-merge sanity check on skill changes. Do NOT trigger for general code review of application code; security review; auditing schemas, producer/consumer configs, PII tagging, or Terraform generation for Schema Registry (handled by `kafka-schema-registry`); runtime/log analysis of skill behavior (use `tools/skill_review_dashboard.py`); or any changes that don't touch the `skills/` tree.
Generate a Confluent Cloud topic creation script with idempotency checks. Use when the user asks to create a topic, provision topics, or write a `create-topics.sh` for Confluent Cloud. Do NOT trigger for self-managed Apache Kafka, schema registration, Terraform generation, or Kafka Streams topology authoring.
Create Confluent-specific skills for external users. Use this skill when users want to create, build, or author a new skill related to Confluent Cloud, Confluent Platform, Apache Kafka, WarpStream, Flink, Connectors, Schema Registry, Tableflow, CDC pipelines, or any Confluent product. Skills can be use-case focused (like data enrichment, CDC to Tableflow, stream processing workflows) or component-specific (like a Flink skill, Schema Registry skill, or Connector skill). Do NOT use this skill when users want to directly use Confluent products (e.g., build a pipeline, write a producer, deploy Flink SQL) — use the appropriate product-specific skill instead. This skill is specifically for creating new skills, not for using existing ones.
Generate a Schema Registry compatibility report for Avro schemas in a project. Use when the user asks to check Avro compatibility, validate schema evolution, or report breaking changes. Do NOT trigger for Protobuf, JSON Schema, or Kafka client code generation.
Use when the user wants to integrate a Kafka client into an existing application or scaffold a Java Kafka client project (Maven or Gradle based) for Confluent Cloud, local Docker, or WarpStream. Covers the Apache Kafka Java clients (KafkaProducer/KafkaConsumer/KafkaShareConsumer) with Avro, JSON Schema, or Protobuf serializers. Also use when the user wants to optimize Java Kafka client configuration for WarpStream. Do NOT trigger for Kafka Streams apps (use kafka-streams-programming), Flink, connectors, or Kafka Python client (use developing-kafka-python-client).
Build a Confluent Cloud topic provisioning script with retention and compaction. Use when the user asks to create a topic, write a `create-topics.sh`, set retention, set compaction policy, provision topics for Confluent Cloud, or generate idempotent topic scripts.
Architect, build, and debug Kafka Streams apps (JVM-embedded stream processing). Use when user mentions KStream, KTable, topology, TopologyTestDriver, StreamsBuilder, interactive queries, GlobalKTable, joins/windows/aggregations, or debugging issues (rebalancing, state stores, lag, deserialization errors). Also use when user wants to optimize Kafka Streams for WarpStream or tune Kafka Streams client configuration for WarpStream. Do NOT trigger for Flink, connectors, CDC, or plain producer/consumer.
Use when the user wants to build a Python Kafka producer or consumer, add Schema Registry to existing Python code, migrate from raw JSON to schema-backed serialization, or scaffold a confluent-kafka-python project for Confluent Cloud, local Docker, or WarpStream. Also use when user wants to optimize Python Kafka client configuration for WarpStream.
Build and deploy Apache Flink user-defined functions (UDFs) in Java for stream processing over Kafka. Use this skill when users want to create scalar UDFs, user-defined table functions (UDTFs), or process table functions (PTFs) in Java, deploy them to Confluent Cloud or local Docker environments, and invoke them from Flink SQL or the Table API. Trigger on: Flink UDF, custom Flink function, process table function, PTF, UDTF, Flink user defined, extend Flink SQL, stateful stream processing with Flink. Do NOT trigger for: Kafka Streams UDFs (use kafka-streams-programming skill), general Flink job development without custom functions, CDC streaming data piplines that include Flink (prefer the confluent-cloud-cdc-tableflow skill), Flink connector setup, or Kafka producer/consumer code.
Scan a project to identify Kafka applications, extract schemas from data models, tag PII fields, generate Terraform for Confluent Schema Registry registration, and produce a migration report with rollout ordering. Use this skill when a user asks to analyze a folder or repo for Kafka usage, extract schemas, audit producer/consumer configurations, or generate Terraform for Schema Registry.
Use this skill to assess and plan a migration from AWS MSK (Managed Streaming for Apache Kafka) to Confluent Cloud. Triggers on user intent like "migrate MSK to Confluent Cloud", "move off MSK", "MSK to CC cutover", "Zero-Cut migration from MSK", "kcp scan my MSK", or any discussion of MSK-to-CC assessment, planning, cluster sizing, Cluster Linking setup, Gateway-based switchover, or post-cutover validation. Do NOT trigger for non-MSK Kafka sources (open-source Kafka, Aiven, Confluent Platform, Redpanda) — this skill is MSK-only. Do NOT trigger for greenfield Confluent Cloud projects with no existing Kafka source. Do NOT trigger for general Kafka programming questions (producer/consumer code, Kafka Streams) unrelated to migration.
Generate CI/CD installation scripts for AWS CDK projects. Use when setting up deployment pipelines, creating install.sh scripts, configuring GitLab CI, or setting up AWS CodeBuild for CDK deployments.
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python. Use when creating CDK stacks, defining CDK constructs, implementing infrastructure as code, or when the user mentions CDK, CloudFormation, IaC, cdk synth, cdk deploy, or wants to define AWS infrastructure programmatically. Covers CDK app structure, construct patterns, stack composition, and deployment workflows.
Estimate AWS costs for CDK projects using real-time pricing data. Use when calculating infrastructure costs, generating pricing reports, or analyzing CDK resource costs before deployment.
Build production web scraping on Bedrock AgentCore Browser — connect Playwright over signed CDP WebSocket, drive extraction with an LLM agent over fixed tool primitives (navigate, scroll, extract-by-selector, screenshot), reuse login state via Browser Profiles with a DCV live-view login flow, detect login walls without false positives, and route through an external proxy. Use when scraping dynamic or login-gated sites (X/Twitter, Reddit, Instagram, YouTube, forums) with AgentCore Browser, when scraped results come back empty on lazy-loaded pages, when Google SSO fails silently in the cloud browser, or when a target site blocks AWS egress IPs.
Build an OAuth + MCP protocol facade in front of Bedrock AgentCore Gateway or Runtime so strict MCP clients (Claude Code, Cursor, Amazon Quick, mcp-remote) can connect. Use when an MCP client fails OAuth discovery ("Fix highlighted fields", DCR errors), when tools beyond 30 silently disappear (Gateway tools/list pagination), when tool calls return 404 or "Unknown tool" (dual session-id, tool name prefix), or when adapting Cognito to RFC 9728/8414 metadata, redirect_uri rewriting, or Gateway schema limits.
Systematic E2E testing workflow with evidence capture and reporting. Use when running integration tests, validating complete user flows, capturing test evidence, or generating test reports.
Publish HTML/Markdown design documents on GitLab Pages with selection-driven discussion. Reviewers select any text in the published doc; a floating 💬 bubble opens a prefilled GitLab Issue (title + anchor link + selection quote + label) in a new tab. GitLab handles auth via the user's existing session — no OAuth, no PAT, no API calls. Works on gitlab.com, self-hosted, and proxy-fronted GitLab.
Migrate Quip documents to GitLab Wiki with full content preservation. Use when converting Quip docs to wiki, migrating documentation, or setting up GitLab wiki from Quip sources.
Comprehensive security and compliance scanning for AWS CDK projects. Use when running security audits, checking license compliance, scanning container vulnerabilities, or running aggregated SAST/IaC/secret analysis before deployment.
Strands conversation/context manager patterns, including sliding window with summarization. Use when building agents with context management, preventing session pollution, or implementing conversation compaction.
Install, diagnose, and run the self-contained Red Card runtime through Codex in the ChatGPT macOS app from any task or project. Use when the user invokes $redcard or asks Codex to install, configure, troubleshoot, or run Red Card. Codex owns every shell command and requests scoped outside-sandbox execution for installation, dependency downloads, and real runs that need macOS hardware or app access; the user only handles required approval, macOS, Chrome, and Google-account UI actions.
Use when adding, fixing, or improving authentication in any app — login, logout, signup, route protection, JWT/access token validation, refresh token rotation, MFA, passkeys, step-up auth, SSO, RBAC, Organizations for B2B multi-tenant SaaS, custom login domains, ACUL, or Universal Login branding. Use to audit a tenant (CheckMate) or fix findings. Use even if Auth0 isn't mentioned — any time a developer asks how to authenticate users, secure an API, debug a 401, CORS error, callback URL mismatch, redirect loop, or 429 rate limit, or migrate from Clerk, NextAuth.js, Firebase, Supabase, Cognito, or Passport.js. Covers React, Next.js, Vue, Nuxt, Angular, Express, Flask, FastAPI, Spring Boot, Go, Swift, Android, Flutter, PHP, Laravel, ASP.NET Core, React Native, Expo, Ionic, and all Auth0 SDKs.
> Use when adding or editing Auth0 guidance in this repo's single auth0 skill — a new framework, feature, tooling, or pattern reference — to get the file structure, router wiring, and validation right the first time. Use even if the request just says "add a reference" or "document X in the skill" without naming the router.
Simulate rigorous, fair peer review on a paper — in two modes. (A) Red-team YOUR OWN draft before submission to predict the reviews you'll get and get a fix list. (B) Review SOMEONE ELSE'S paper when you're an assigned reviewer or helping your advisor — produce a fair, venue-formatted, submission-ready review. Use whenever the user gives a paper (PDF, .tex, .md, arXiv link, or pasted text) and wants to predict reviews, find weaknesses before reviewers do, stress-test a submission, OR write a real review of another paper. Grounded in official NeurIPS/ICLR/ACL reviewer guidelines; every criticism pinned to a location, and checked against ACL's H1–H17 list of illegitimate critiques. 两种模式:审自己的稿(投稿前红队)/ 审别人的稿(当审稿人或帮导师),按会议官方标准评,绝不脑补、绝不发不正当批评。
>- Use when you need to map a pile of old URLs to live pages and turn them into migration/replatform/catalog restructure, turn a Google Search Console 404 export into live redirects, or WordPress→Shopify URL transforms 404s", "redirect the dead links", "we relaunched and lost our rankings". Recovers SEO equity and rescues users after a URL structure changes. Not for creating a single one-off redirect (do it in admin).
>- "give me landing page concepts", "LP ideas", "landing page angles", a campaign or ad landing page, pages for a new audience/segment, a seasonal/event/promo page, or a geo/local page. Also use when a chosen concept gets picked and needs building out into an actual page (section-by-section blueprint), or when auditing an existing landing page against best practice. not the product. Not for full-site information architecture, product detail pages, collection pages, or blog/SEO content (a landing page has ONE goal, no site chrome). Use an SEO/content skill. Not for the ad or email creative itself, though message match with the page matters.
>- dead/discontinued/zero-inventory products, clean up catalog debris, kill ghost review stars (empty star ratings a theme still renders after a review app was uninstalled), remove orphaned metafields left by an uninstalled app, strip HTML artifacts from product descriptions (double-nested bold, fully-bold paragraphs, empty tags), or fix messed-up / mangled product descriptions in bulk. Mutating FINDING what's wrong (use shopify-catalog-audit) or filling missing metadata like SEO titles and alt text (use shopify-seo-metadata).
>- Use when a store owner is doing bulk data work through the Matrixify (formerly "bulk edit metafields", CSV or Excel import, "my import deleted my metafields", "my import wiped my tags", MERGE vs REPLACE vs UPDATE, "how do I undo an import", building a Matrixify sheet by hand or programmatically, or a data migration between stores/platforms. Covers products, variants, metafields, collections, redirects, customers, and menus. Not for minting category (taxonomy) metafields, which Matrixify cannot do (use shopify-category-taxonomy); not for one-off single-record edits via the Admin API (use the relevant entity skill).
>- Use when someone wants to find product-data problems across a Shopify missing photos / thin or missing descriptions / pricing anomalies", "$0 or compare-at-inverted prices", "products missing type or vendor", "catalog quality sweep", "product data health check", "which listings are broken", problems, it does not change anything. Not for FIXING the problems it finds (use shopify-catalog-cleanup for debris/archiving, shopify-seo-metadata for missing SEO meta, shopify-alt-text for missing image alt text).
>- recipe, FAQ, Article/BlogPosting, CollectionPage, AboutPage, or Organization schema; chasing Google rich-results / rich-snippet eligibility; debugging a Search Console "Invalid object type" or "missing field" schema error; or a request like "add schema to my store", "add recipe schema", or "why isn't my product showing rich results". This skill adds SUPPLEMENTAL JSON-LD the theme cannot emit dynamically, stored in a metafield and rendered by one Liquid snippet. Not for meta titles, meta descriptions, canonical tags, or Open Graph (use shopify-seo-metadata for those).
>- alt attribute, accessibility alt text for product images, alt text for Files library images, image SEO, or a WCAG/accessibility pass that flags images text", "images have no alt", "add alt attributes for accessibility", "image SEO sweep". One mutation, fileUpdate, covers both product media and the Files library. Not for meta titles/descriptions (use shopify-seo-metadata).
>- Use when you assign the Shopify Standard Product Taxonomy category, "set the product category", "categorize the catalog", or fill the category / taxonomy Caffeine content), a.k.a. product category attributes / taxonomy attributes, including the attributes a Google feed asks for. Covers bulk classification, discovering a category's attributes and allowed "category metafields show blank/null", "my Color attribute won't save". Not for bulk CSV data loads (Matrixify can't do this; see shopify-matrixify for bulk data).
>- Use when a store has missing SEO titles or meta descriptions and you want to sweep", "SEO meta backfill across products/collections/pages/blog posts", "missing page titles", "fix blank search-appearance metadata", "generate SEO (SEO title, meta description) on products, collections, pages, and blog articles, never touching human-written values. Not for image alt text (use shopify-alt-text) or JSON-LD (use shopify-json-ld).
Scan the system with fresh eyes. Surface what's alive, what's connecting, what's trying to emerge. Route insights where they belong.
Open the floor for your AI's curiosity. Use when wrapping or at natural pauses.
Refresh the current session's LOG with a fresh extraction. Use as the last step of /wrap, or any time the session has continued and you want the capture current. Idempotent — safe to invoke multiple times.
Create a living task doc from natural language. Use when you want to track work, capture a new project, or create a thinking log that accumulates context across sessions.
Pressure test an idea through core lenses. Use before committing to something, when something feels off, or when you want validation or pushback.
Pick up a workstream across sessions. Load context, find texture, align, then go. Use when jumping back into something that has history.
End work session intentionally. Use at natural stopping points, before context limits, or when switching contexts.
Build topic reserves by searching your entire system, or run discovery mode to find what connects across territories. Use when consolidating scattered knowledge on a topic, before writing/sharing, or when curiosity has no specific target.
한국 홈택스 전자세금계산서 발급·수정발급·조회 범용 워크플로. 매출 세금계산서 작성, 거래처·공급가액·세액·품목 입력 보조, 발급 직전 QA, 수정세금계산서, 발급 후 조회. 세금계산서 발행, 전자세금계산서 발급, 세금계산서 끊어줘, 수정세금계산서 요청 시 사용. 동료·일반 사업자용. 자동 발급 금지.
한국 홈택스 부가가치세 신고 범용 워크플로. 일반/간이 확인, 미리채움 조회, 세금계산서·사업용카드·현금영수증 대조, 매입세액 공제·불공제 점검, 엑셀 합계 대조, 제출 직전 체크리스트. 부가세 신고, 매출세액, 매입세액, VAT, 홈택스 부가가치세 요청 시 사용. 동료·일반 사업자용. 자동 제출·납부 금지.
한국 홈택스 세무 작업 통합 진입점. 부가세 신고, 종합소득세 신고, 전자세금계산서 발급, 신고 준비, 영수증·카드 분류 요청을 받아 적절한 하위 스킬로 라우팅. 세무 도와줘, 세금 신고, 홈택스, 부가세, 종소세, 세금계산서 발행, 영수증 정리, 신고 준비 등 포괄 요청 시 사용. 동료·일반 사업자 범용. 자동 제출·발급 금지.
한국 사업자용 영수증·카드·현금 지출 분류. 계정과목 제안, 부가세 매입세액 공제/불공제 후보, 종합소득세 필요경비 후보 구분, 엑셀 분류표 작성. 영수증 분류, 카드 내역 정리, 계정과목, 접대비, 공제 여부 요청 시 사용. 동료 범용.
한국 부가세·종합소득세 신고 전 준비 가이드. 신고기한, 모을 자료 체크리스트, 폴더 구조, 홈택스·카드·은행 다운로드 목록, 사업용카드 등록 안내. 신고 준비, 서류 모으기, 세무 폴더, 무엇을 받아야 해 요청 시 사용. 동료 범용. 홈택스 제출 자체는 vat-hometax/income-tax-hometax로 연결.
한국 홈택스 종합소득세 신고 범용 워크플로. 모두채움/일반신고, 사업·근로·기타소득 조회, 단순·기준경비율 vs 간편장부 선택 점검, 엑셀 수입·경비 대조, 공제 누락 체크, 제출 직전 QA. 종합소득세, 종소세, 경비율, 모두채움, 5월 신고 요청 시 사용. 동료·일반 납세자용. 자동 제출·납부 금지.
>- Specialized agentic and context engineering prompt methodology for Claude. Use when designing AI agents — system prompts, tool definitions, context window architectures, failure mode planning, multi-agent coordination, an agent," "architect an agent's context," "design tool definitions," "agent system prompt," "context window architecture," "tool interface design," "evaluate agent behavior," "multi-agent coordination," "context engineering for agents," "ACI design." Provides 12 tested approaches for agent architecture (designing agents, not using them). Do NOT use for evaluating or scoring individual non-agent prompts (use rootnode-prompt-validation if available). Do NOT use for general software architecture that hosts agents (use standard technical reasoning for that).
>- Analyzes Claude Project context budget under the automatic-RAG-by-window my context budget," "how much context am I using," "is my project too big," "optimize my token usage," "tier my files," "optimize for RAG," "improve retrieval quality," "should I keep compressing," "am I over-compressing," forgets my instructions," "responses getting generic," "content not found in my knowledge files." Also use when a project audit scores Knowledge Architecture ≤ 3. Do NOT use for content placement decisions (use rootnode-memory-optimization if available), full project audits (use rootnode-project-audit if available), or behavioral tuning (use rootnode-behavioral-tuning if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.
>- Detects seven structural anti-patterns in Claude Projects that cause unpredictable output, ignored instructions, and degraded quality. Diagnoses Monolith, Orphan File, Echo Chamber, Phantom Conversation, Kitchen Sink, Misaligned Hierarchy, and Blurred Layers. Use when user says "what's wrong with my project," "Claude ignores my instructions," "diagnose my project," "why is output inconsistent," "review my project setup." Also trigger on getting overridden," "my Project isn't behaving as designed." Use alongside rootnode-project-audit if available for deeper structural analysis. Activate whenever the user describes symptoms of unreliable, inconsistent, or degraded Claude Project output, even if they do not name a specific pattern. Do NOT use when the user's primary request is Memory-layer rebalancing (use rootnode-memory-optimization if available) or scoring a single prompt (use rootnode-prompt-validation if available).
>- Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).
>- Diagnoses and fixes Claude behavioral issues in system prompts and Projects using tested countermeasure templates. Use when "Claude is too verbose," "keeps hedging," "agrees with everything," "claims it did something it didn't," "won't use a tool," "fix Claude's output," "tune Claude's behavior," "Claude ignores my preferences," "adds unsolicited (output-content + persistent-preference), hedging, verbosity, list overuse, fabricated precision, over-exploration, tool miscalibration (over- and under-triggering), LaTeX defaulting, editorial drift, self-referential fabrication. Also use when auditing a system prompt for behavioral calibration or recalibrating a pre-4.7 prompt, and when users describe recurring output problems without naming a tendency. Do NOT use for scoring a prompt's overall quality — use rootnode-prompt-validation if available.
>- Independent re-derivation gate for proposed changes during autonomous execution. Evaluates a change (code diff, config edit, engine evolution, schema change) against the work's authority matrix and a 4-check narrowness, and regression risk. Returns structured JSON with pass/fail per check, an overall verdict (APPROVE / REQUEST_CHANGES / REJECT), and blockers. Profile-driven thresholds (strict for unattended runs, lenient for desk supervision). Use when an autonomous agent proposes an engine change, when reviewing a Claude Code-authored modification before merge, or when an unattended profile requires independent re-derivation. "is this change safe," "is this safe to merge," "should I let this land," "run the critic." Do NOT use for handoff-readiness checks (use rootnode-handoff-trigger-check), general code review, or design-time correctness. Authority matrix required.
>- Guides selection of identity, reasoning, and output approaches for Claude approach," "which approach fits this task," "recommend a prompt pattern," "compare reasoning methods," "map this task to the right approach," "what combination of approaches," "which identity fits," "which reasoning method." which approach to use," "my output lacks domain depth." Covers decision-tree logic across 8 identity approaches, 18 reasoning variants, and 10 output formats. After selection, use the relevant catalog skill if available to retrieve full templates. Activate whenever approach-selection across multiple categories is the primary decision. Do NOT use when the user already names a specific approach to retrieve (use the relevant catalog skill directly if available) or for evaluating existing prompts (use rootnode-prompt-validation if available).
Claude Skills — questions
Answers built from the skills we actually parsed.