Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Use when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - gathers well-sourced, current information from the internet to inform technical decisions
Application resilience patterns. Circuit breakers, retries with backoff, bulkheads, timeouts, fallbacks, and health checks. Polly (.NET), resilience4j (Java), cockatiel (Node.js). USE WHEN: user mentions "circuit breaker", "retry", "backoff", "bulkhead", "resilience", "fault tolerance", "Polly", "resilience4j", "fallback" DO NOT USE FOR: error handling basics - use language skills; monitoring - use `opentelemetry`
Manage the PR review iteration loop: poll for reviewer feedback, assess suggestions with evidence, implement fixes, resolve threads, and drive CI/CD to green. Works standalone on any PR (bug fix, refactor, hotfix, feature) or as a composable module invoked by /ship. Spec-aware when a SPEC.md is provided, but does not require one. Triggers: review, review loop, PR feedback, iterate on PR, resolve reviews, CI/CD resolution, green pipeline, address reviewer comments.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along four independent axes — Standards, Spec, Architecture, and Divergent design — each run as a parallel sub-agent so contexts stay clean, then verified against false positives and reported side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Orchestrates the RLM repo workflow end-to-end with phase gates, locked artifacts, addenda, traceability, and automatic bootstrap/upsert of AGENTS/PLANS scaffolding. Trigger phrases: "Implement requirement <run-id>", "Run RLM Phase <N>", "resume requirement", "lock Phase <N>", "verify locks".
Ruby language conventions, idioms, and modern features (3.x+) for writing idiomatic Ruby code. Covers error handling patterns, performance optimization, and Ruby-specific idioms. Use when writing or reviewing pure Ruby code, using modern Ruby features (pattern matching, ractors, RBS), optimizing Ruby performance, or establishing Ruby conventions. For Rails-specific guidance use the rails skill. For design patterns use design-patterns-ruby. For testing use rspec. For code style use rubocop.
Machine learning in Python with scikit-learn. Use for supervised learning (classification, regression), unsupervised learning (clustering, dimensionality reduction), model evaluation, hyperparameter tuning, preprocessing, or building ML pipelines. Provides comprehensive reference documentation for algorithms, preprocessing techniques, pipelines, and best practices.
Scrapling web scraping reference for this project. Provides fetcher selection (Fetcher/DynamicFetcher/StealthyFetcher), selector patterns, session management, anti-bot bypass, adaptive/self-healing selectors, Spider framework for crawling, proxy rotation, CLI commands, and MCP server for AI integration. Use when implementing web scraping, handling protected sites, or building data extraction pipelines.
Build, review, debug, configure, migrate, or plan Sentry observability in TypeScript/JavaScript apps with current docs and official @sentry/* packages. Use for Sentry JS SDK 11 (and v10→v11 migration), Sentry.init, DSN, dataCollection, span streaming, beforeSendSpan, ignoreSpans, errors, tracing, Session Replay, profiling, logs, metrics, source maps, releases, Seer, OpenTelemetry, enableOpenTelemetrySetup, @sentry/nextjs, @sentry/react, @sentry/node, @sentry/browser, @sentry/vue, @sentry/svelte, @sentry/sveltekit, @sentry/nuxt, @sentry/astro, @sentry/remix, @sentry/react-router, @sentry/solid, @sentry/solidstart, @sentry/tanstackstart-react, @sentry/nestjs, @sentry/hono, @sentry/elysia, @sentry/bun, @sentry/deno, @sentry/cloudflare, @sentry/aws-serverless, @sentry/electron, @sentry/react-native, @sentry/bundler-plugins, wizard, sentry CLI, vite/webpack plugins, captureException, setUser, and setAttribute.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's ticket tracker (GitHub or local markdown), triage label vocabulary, domain doc layout, and review-prep conventions (commit style and breadcrumb schema). Run before first use of `to-tickets`, `to-spec`, `tdd`, `improve-codebase-architecture`, `wayfinder`, or `prepare-for-review` — or if those skills appear to be missing context.
Build Shopify applications, extensions, and themes using GraphQL/REST APIs, Shopify CLI, Polaris UI components, and Liquid templating. Capabilities include app development with OAuth authentication, checkout UI extensions for customizing checkout flow, admin UI extensions for dashboard integration, POS extensions for retail, theme development with Liquid, webhook management, billing API integration, product/order/customer management. Use when building Shopify apps, implementing checkout customizations, creating admin interfaces, developing themes, integrating payment processing, managing store data via APIs, or extending Shopify functionality.
Compatibility entry point for deepening one non-trivial area of a roadmap design without reopening the whole interview or generating tasks. Use when the user says /slice, names a UX/API/data/worker/infra/security area, or provides a legacy slice that must be reconciled.
Use when locking module boundaries, class/API shape, or dependency direction after a design/spec is clear; when new packages, ports, or IO edges are about to be planned; when unit tests need many mocks; or when a review/refactor shows coupling or God-class smell. Do not use as the main skill while product decisions are still open (that is grill).
Draft specs, analyze requirements, plan implementation, implement from specs, review against specs (generator≠evaluator), extract specs from existing code, run surgical bugfix specs, multi-session handoff/progress, and size greenfield/brownfield work. Use when the user wants testable requirements, living specs, spec-driven development, session handoff, bugfix with regression fences, Design-First vs Requirements-First, or /draft-spec /plan-impl /implement-spec /review /extract-spec. Do not use for C4/solution architecture packets (use solution-architecture), DevOps/CI-CD strategy design, README authoring, Agent Skill optimization, AFK/Ralph automation products, or trivial one-line fixes.
Create new spec-driven tickets and resume existing ones through the full lifecycle: research, specification, planning, and implementation. Use when: the user describes new work to be done; continuing a previously started ticket; a feature, bug fix, or task needs planning and implementation; starting or resuming planned work on a project with specs/. Triggers on: 'new ticket', 'new feature', 'fix bug', 'implement', 'create ticket', 'I want to build', 'let us work on', 'add feature', 'continue ticket', 'resume work', 'pick up where we left off', 'work on ticket', 'existing ticket', 'check ticket status', 'what is the state of ticket'.
Design and generate Kotlin Spring HTTP APIs with correct controller signatures, DTOs, validation, serialization assumptions, error handling, and web tests. Use when building or changing REST endpoints, choosing between MVC and WebFlux, modeling request and response payloads, standardizing error responses, or avoiding Kotlin-specific validation and Jackson mistakes.
Expert guidance for SQLite database with better-sqlite3 Node.js driver including database setup, queries, transactions, migrations, performance optimization, and integration with TypeScript. Use this when working with embedded databases, better-sqlite3 driver, or SQLite operations.
Documentation-first development methodology. The goal is AI-ready documentation - when docs are clear enough, code generation becomes automatic. Triggers on "Build", "Create", "Implement", "Document", or "Spec out". Version 3.5 adds Phase 2.5 Adversarial Review and renames internal verification to Spec Gate (structural completeness). Clarity Gate is now a separate standalone tool for epistemic quality.
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration, including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
Senior Payment Solutions Architect for Stripe (2026). Specialized in secure checkout flows, complex billing models (usage-based/hybrid), global tax compliance via Stripe Tax, and high-performance Next.js 16 integration. Expert in building PCI-compliant, idempotent, and resilient payment systems using Checkout Sessions, Payment Elements, and Server Actions.
Full session shutdown — digest, retro, merge worktree branches, worktree cleanup, close session state, and commit handoff. This is the single entry point for ending a session. Triggers on: 'teardown', 'clean up', 'wrap up', 'session end', 'end session', 'close session', 'done', 'log off', 'sign off', or automatically when the decision budget is reached.
Use when the user has a coding prompt — a feature, bug fix, or refactor — and wants it implemented end to end by a self-checking software loop, not a single pass. It refines the prompt into an executable plan (running the plan-loop internally), then executes the plan task by task: an Engineer subagent implements each PR-sized task editing only source, a separate QA subagent authors the tests that prove the task's acceptance criteria (or grades quality only when tests already cover them), runs the task's tests plus the full accumulated regression suite, and grades the code against a strict conciseness/readability/style-match rubric; the Engineer and QA loop on each task until the tests pass and the quality gate holds, then it commits and opens a pull request for the task — stacked PRs (one per task, each based on the prior) by default, or one combined PR — and moves to the next task. Author and critic have disjoint write scopes (Engineer owns source, QA owns tests) so neither can game the gate. Not for producing a plan without building it (that is plan-loop), and not for tuning a metric on an existing artifact under a fixed correctness bound (that is optimize-loop).
Test-driven development, including frontend slices verified against a Figma design source via Storybook stories and an agent-browser visual gate. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", or wants integration tests.
Build Temporal applications in Python using the temporalio SDK. Use when creating workflows, activities, workers, clients, signals, queries, updates, child workflows, timers, retry policies, saga/compensation patterns, testing, or any durable execution pattern in Python.
Audit and refactor UI code so every color value comes from the theme. Replace hex codes, rgba(), hsl(), oklch() literals, and named CSS colors with theme palette tokens (primary, secondary, error, warning, info, success, background, text) and the alpha() helper for transparency. Use when writing or reviewing any UI component, when starting a new MUI or design-system theme, when a designer hands off colors as hex annotations, when seeing color literals scattered across component files, or when an LLM produced styling with hardcoded hex values. Counterweight to LLM training corpora dominated by tutorial code that inlines hex codes and rgba literals instead of role-based theme tokens.
Improve documentation and comment prose so it describes the current state of the code directly and reads clearly in plain language, cutting history, transitions, and trivial detail. Works in two modes: on the current changes (session edits, uncommitted work, or the branch diff) or on named files/folders. Use when the user wants to clean up, tighten, or improve docs or comments — in a file, folder, project, or in what was just changed ('tidy the comments in this diff', 'clean up the docs we just edited', 'fix docs before committing') — make docs clearer / more concise / more readable, remove 'previously / now / no longer / migrated from / instead of' phrasing, make docs timeless, or asks to 'improve docs prose'.
Guides TinyRobot Vue AI chat UI implementation, setup, and code generation. Use when the user mentions TinyRobot, OpenTiny TinyRobot, Bubble, Sender, Prompts, chat container, message list, conversation tools, or asks to build chat interfaces with TinyRobot components.
Current Ethereum development tools, frameworks, libraries, RPCs, and block explorers. What actually works today for building on Ethereum. Includes tool discovery for AI agents — MCPs, abi.ninja, Foundry, Scaffold-ETH 2, Hardhat, and more. Use when setting up a dev environment, choosing tools, or when an agent needs to discover what's available.
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.