Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Claude Code CLI tool expertise. Features: autonomous coding, slash commands, MCP servers, Agent Skills, hooks, plugins, CI/CD integration. Capabilities: setup/config, troubleshooting, skill creation, MCP integration, enterprise deployment, workflow automation. Actions: configure, troubleshoot, create, deploy, integrate Claude Code. Keywords: Claude Code, Anthropic, CLI tool, slash command, MCP server, Agent Skill, hook, plugin, CI/CD, enterprise, CLAUDE.md, agentic coding, terminal tool, workflow automation, code generation, skill creation, configuration, authentication, API key. Use when: learning Claude Code features, configuring settings, creating skills/hooks, setting up MCP servers, troubleshooting issues, CI/CD integration, enterprise deployment questions.
Finalize a completed Beads feature by reconciling documentation, validating delivery, recording implementation, reviewing drift, and executing `pr`, `merge`, or `ready`. Use when asked to close a feature, prepare it for delivery, or reconcile implementation and documentation after its implementation coordinator closes.
Reference for Cloudflare Workers AI, running AI models on serverless GPUs through the env.AI.run() binding. Covers the AI binding in wrangler.jsonc, model selection (@cf/meta/llama, Flux and Stable Diffusion image generation, BGE embeddings, vision models), streaming responses, AI Gateway caching, RAG with Vectorize, Vercel AI SDK integration and OpenAI-compatible endpoints, plus rate limits, neuron pricing and a production checklist. Use when implementing AI inference in a Cloudflare Worker, generating text or images at the edge, configuring Workers AI bindings, adding AI streaming, wiring up AI Gateway, building embeddings or RAG on Workers, or debugging AI_ERROR, rate limit errors, model not found, model unavailable, token limit exceeded, neurons exceeded, quota exceeded or streaming failures.
Review code for API shape, error handling, backward compatibility, and product-vs-library fit. Use when reviewing public APIs, library interfaces, error types, dependency choices, or product code being over-engineered, or when deciding between "ship the dumb version" and "design for stability". Do NOT use for deletion-focused or anti-bloat review (use code-review-russ-cox).
Review a change or audit existing code through the Russ Cox lens — necessity, layering, minimal seams, error/logging/testing discipline, and anti-bloat. Use when reviewing diffs, new features, or dependency additions, or when asked to "audit this package", "refactor/polish this code", "find design, implementation, or style problems", "do we need this?", or "is this too complex?". Do NOT use for public API shape or product-vs-library tradeoffs (use code-review-mitsuhiko) or invariant/cost honesty (use code-review-burntsushi).
Local mirror of OpenAI Codex product documentation (learn.chatgpt.com/docs): CLI, Cloud, web app, IDE extension, hooks, skills, plugins, MCP, subagents, AGENTS.md, prompts, rules, sandboxing, models, pricing, security, and configuration. Use whenever the user asks how Codex behaves, how to install or configure Codex, or what a Codex flag, slash command, or feature does (including informal phrasing such as "hooks", "--resume", "sandbox modes", "cloud environments"). Read this skill's references/ before generic web search for Codex product questions. Do NOT use for Claude Code, Cursor, or other agents -- in particular, do not use for "Claude Code hooks" or general OpenAI API, ChatGPT, Realtime, or non-Codex coding help.
Deliver an approved task through an auditable multi-model panel with test, review, and verification evidence. Use when the user requires a recorded panel trail for implementation. For the normal fast path, use implement-and-review or implement-tasks.
How the reference commerce agents of either role are structured, covering the loop, where each rule lives, skills, the backend interface, delegates, and model fields. Load when designing or reviewing the structure of a shopping or merchant agent.
The reference agents' cache-stable request assembly, covering the static system and per-request context split, the fixed tool list, the rolling conversation breakpoint, which config fields are prompt bytes, and verification. Load when writing or reviewing a commerce agent's prompt assembly, when cache reads are zero, or when a turn's latency or cost is the question.
The reference presentation-tool contract, covering server-side enrichment, suggestion chips, the event stream, progressive rendering, both roles' built-in components, and adding a vertical component. Load when building or reviewing how a commerce agent's output reaches a frontend.
Integrate or upgrade the Contentsquare React Native SDK -- Session Replay, screen tracking, transactions, analytics, masking, privacy opt-in/out. Always starts with a mandatory Contentsquare project healthcheck (ask for the data source IDs or resolve the Android and iOS bundle ids, call the healthcheck endpoint, report project health) before any other work. Use when working with Contentsquare, CSQ, StartConfig, AnalyticsOptions, CSQMask, CSQWebView, @contentsquare/react-native-bridge, or migrating from the legacy `Contentsquare` API to `CSQ`.
Export the conversation context. Write the purpose, intent, design decisions, and constraints shared in the conversation to the `.dev/contexts/` directory, and if a PR exists, also post them as a PR comment. Hand off to the next worker (reviewer, AI in another session, bug-hunting AI, etc.). Use when the user says "export the context", "export the conversation context", or "save the conversation to .dev".
Import conversation context. Reads past conversation context stored in the `.dev/contexts/` directory and uses it for continuing development or reviews. Use when the user says "load the context", "import conversation context", or "read the .dev context".
Create a GitHub pull request safely and reliably using project conventions. Make sure to use this skill whenever the user asks to create a PR, submit changes for review, open a pull request, or mentions "PR", "プルリク", or "pull request". It handles commit verification, branch validation, and PR creation using the gh CLI.
Professional data visualization creation using D3.js with support for interactive charts, custom visualizations, animations, and responsive design. Use for: (1) Creating custom interactive charts, (2) Building dashboards, (3) Network/graph visualizations, (4) Geographic data mapping, (5) Time series analysis, (6) Real-time data visualization, (7) Complex multi-dimensional data displays
Master dispatcher for deobfuscation workflows. Loads the right combination of deobf and reverse-engineering skills based on target type — native binary, JavaScript, VM-protected, packed, or CTF. Use when you need comprehensive deobfuscation capabilities for any target.
Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated packages, open dependency PRs, scan for package updates, audit for CVEs, or flag breaking changes in upgrades. Trigger when a user says "check for outdated packages", "update my dependencies", "open PRs for dependency updates", "scan for CVEs", or "which packages need upgrading".
Use when building React "Bring Your Own Screen" (BYOS) custom UI on top of a Descope flow — takes exported flow JSONs, extracts the real interaction IDs and outputs, generates BYOS components that match hosted parity, and avoids the rediscovery-the-hard-way failure modes (silent form rejection, shared screen-name collisions, anonymous-session stickiness, nested-form hydration errors, wrong form keys, dead-end buttons, missing OAuth provider field).
Plan developer documentation by choosing content types, defining scope, making documentation decisions, researching features, planning scenarios, and turning user needs into a practical documentation plan. Use when planning READMEs, getting-started guides, concepts, tutorials, how-to guides, API references, troubleshooting docs, changelogs, release notes, Agile docs work, or multi-doc launch plans.
Research product and feature facts for developer documentation by mapping source-of-truth owners, validating behavior hands-on, interviewing SMEs, and turning uncertainty into doc-ready notes. Use when feature specs are incomplete, implementation details need user-facing meaning, SMEs disagree, or docs require evidence before planning, drafting, release notes, API docs, tutorials, scenarios, or troubleshooting content.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs
A rigorous diagnostic loop for serious errors and performance regressions. Reproduce → minimize → hypothesize → test → fix → regression test. Use when the user says "diagnose this"/"debug this", reports an error, says something is broken/throwing an exception/failing, or describes a performance regression.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Generate and update documentation from what the code already knows: API references from doc comments (KDoc/Dokka, dartdoc, DocC, rustdoc, Doxygen), REST docs from an OpenAPI spec, README scaffolding from package metadata, changelogs from conventional commits, and architecture diagrams from module structure. Also fills in missing doc comments and finds docs that drifted from the implementation. Use when someone says “generate the docs”, “document this API”, “add KDoc/dartdoc/DocC/rustdoc comments”, “write docstrings/TSDoc/Doxygen comments”, “set up Dokka”, “write the README”, “generate a changelog”, “the docs are out of date”, or the Hungarian “generáld a dokumentációt”, “dokumentáld ezt az API-t”, “írd meg a README-t”, “frissítsd a changelogot”. Not for prose docs written from scratch with the user (that is doc-coauthoring), not for looking up someone else's library docs (that is find-docs).
Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.
Type-safe Drizzle ORM patterns for Cloudflare D1 databases: schema definition, migration management with Drizzle Kit and drizzle.config.ts, relations and relational queries, joins, prepared statements, the D1 batch API for transaction-like work, and Workers/Wrangler integration. Documents 12 known pitfalls including D1 transaction errors (SQL BEGIN is unsupported), foreign key constraint failures during migrations, module import errors under Wrangler, missing D1 bindings, migration apply failures, schema TypeScript inference errors, prepared statement caching, rollback patterns, TypeScript strict mode errors, remote versus local database confusion, and mixing wrangler.toml with wrangler.jsonc. Use when building a D1 schema, writing type-safe queries, running or repairing Drizzle migrations, or hitting D1_ERROR, BEGIN TRANSACTION, d1 binding, or schema inference errors.
Use when choosing between TypeScript and ECMAScript features. Use when writing portable code. Use when considering enum or namespace. Use when targeting multiple JavaScript environments. Use when writing library code.
Performance optimization for premium animated websites. Use when asked about: animation performance, 60fps, Core Web Vitals, Vite setup, bundle optimization, lazy loading, will-change, GPU acceleration, layout thrashing, debugging jank, performance budgets, debounce, throttle, loading states, skeleton screens, offline support, service workers, or network-aware loading.
Generate EliteForge frontend projects with the same logic as cisdigital-generator-app. Reuse the exact project type to template mapping for frontend_app/frontend_ui/frontend_sdk, naming rules for company/product/service, and onebase-cli command assembly. Use when users ask to scaffold EliteForge frontend app projects, Vue3 component monorepo projects, JS SDK/lib projects, or request a dry-run command preview aligned with this generator. Always require user-provided required parameters and never infer missing required fields.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.