Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Circuit breaker, retry, and DLQ patterns for .NET using Polly and Brighter. Use when implementing fault tolerance, handling transient failures, configuring retry strategies, or setting up dead letter queues. Includes Polly HttpClient patterns and Brighter message handler resilience.
Diagnose, review, operate, or deploy a generic rolecard workshop made of a static catalog, package gateway, object storage, OAuth ownership, review workflow, and reverse proxy. Use for health checks, API-contract alignment, publish/update/withdraw flows, privacy review, CORS and callback diagnosis, container or proxy planning, and explicitly authorized deployment. Start read-only; never deploy, rotate credentials, revoke access, or mutate production unless the user clearly authorizes that action and target.
Investigate and root-cause production issues from live OpenTelemetry telemetry (traces, logs, metrics) with the Kopai SDK in TypeScript code mode. Use this skill to debug errors and error-rate spikes, investigate latency/slowness and timeouts, trace requests across services, find failing or cascading services, and correlate logs to a trace — including vague symptom reports like 'why is my API slow', 'getting 500 errors', 'service is down', 'requests are timing out', or 'something is failing in prod', even when the user never says 'traces' or 'observability'. This analyzes existing telemetry to find a cause. Do NOT use it to add instrumentation (use otel-instrumentation), to build dashboards or visualizations (use create-dashboard), or to fix non-telemetry problems like failing CI, lint errors, unit tests, or SQL query tuning.
Use when designing, building, reviewing, or fixing any right-to-left (RTL) user interface—Persian/Farsi (فارسی), Arabic, Hebrew, Urdu—on the web (React, Next.js, Vue, Tailwind, plain CSS) or Flutter, even if the user only says the app is Persian/Iranian without mentioning RTL. Covers layout direction and mirroring, which icons flip and which never do, bidirectional (bidi) text with LTR islands (URLs, emails, phone numbers, code), Persian vs Arabic-Indic vs Latin digits, Jalali (Shamsi) dates, Persian typography (font pairing, line height, the letter-spacing trap, ZWNJ نیمفاصله), font licensing, logical CSS properties, form input direction, and long-text overflow. Also use when Persian/Arabic text renders incorrectly or looks “off,” when localizing an LTR app to RTL, or to audit existing code for RTL violations with the bundled zero-dependency detector. Not for backend-only or non-UI tasks.
Design a Rust public API — trait design, generics versus dyn, sealed traits, what is exported, and which changes break semver. Use when designing or reviewing a crate public surface, when choosing between a generic parameter and a trait object, when adding a trait method or enum variant to a released crate, or when the user asks whether a change is a breaking change.
Build and review Bevy procedural world generation with grid resources, deterministic seeds, reachability checks, chunk or room spawning, background generation boundaries, and gameplay-safe entity materialization. Use when creating tile maps, dungeon-like spaces, mining bases, or generated levels in Rust Bevy games.
Review Rust changes on two axes at once — standards (idioms, ownership, errors, API surface, unsafe) and spec (does the change do what was asked) — with a Rust smell baseline layered on the repo lint configuration. Use when reviewing a Rust diff, pull request, or branch, when asked whether a change is ready to merge, or when a review needs to cover more than what clippy already reports.
Pick the concurrency model from the workload shape — rayon for data parallelism, scoped threads for borrowed stack data, channels for handoff, shared state last — and use the weakest correct atomic ordering. Use when writing or reviewing threaded Rust, when Mutex, RwLock, atomics, or manual Send/Sync appear, when a deadlock or data race is suspected, or when the user asks how to parallelize Rust code.
Rust code quality with Clippy, rustfmt, and cargo tools. Covers linting, formatting, and idiomatic Rust patterns. USE WHEN: user works with "Rust", "Cargo", "Actix", "Axum", asks about "Clippy", "rustfmt", "Rust linting", "Rust best practices", "idiomatic Rust" DO NOT USE FOR: SonarQube - use `sonarqube` skill, security - use `rust-security` skill
Rust security patterns for web applications. Covers memory safety guarantees, dependency auditing, secure coding practices, and OWASP for Rust ecosystem. USE WHEN: user works with "Rust", "Actix", "Axum", "Rocket", "Warp", asks about "Rust vulnerabilities", "cargo audit", "Rust injection", "Rust authentication" DO NOT USE FOR: general OWASP concepts - use `owasp` or `owasp-top-10` instead, other language security - use language-specific skills
Receive and verify Salesforce Outbound Messages (the native "webhook" for Flow/Workflow). Use when setting up a Salesforce Outbound Message listener, parsing the SOAP/XML notification, validating the OrganizationId, returning the required Ack response, or handling Account, Contact, Lead, Opportunity, and Case record changes. Also covers Platform Events / Change Data Capture as the streaming alternative.
Integrate Seam Access Grants for per-entrance, per-credential control over smart lock access. Create access grants specifying who gets access to which doors, when, and how (PIN code, mobile key, Instant Key). Use this skill when someone needs to control which access methods each guest or member gets, issue both PIN codes and mobile keys, manage access per-door (room + lobby + gym), or deliver Instant Key links. Works with August, Yale, Schlage, Kwikset, and other smart locks. Common use cases: hotel guest apps, gym/fitness access, office visitor management.
Set up git guardrails that make coding agents ask or stop before commands that lose work or rewrite shared history, at a guard level the user picks, for whichever agent harnesses they use. Use when the user wants to guard against destructive git operations by coding agents.
Tmux execution support for long-running and persistent commands. Load this skill when you need to: (1) run commands expected to exceed tool timeout (over 60s), (2) start persistent servers or dev processes, (3) run TUI/interactive applications, (4) execute parallel isolated tasks in separate sessions, (5) run remote commands over SSH that must survive disconnection, (6) handle tmux errors like 'capture-pane blocked in interactive_bash'. Trigger phrases: 'run in background', 'start server', 'long-running', 'tmux session', 'keep running', 'persistent process', 'dev server', 'training script', 'git clone large repo', 'docker build', 'capture-pane blocked'.
Administrative workflows for the agent-skills repository. Use when the user wants to contribute a skill, open a pull request, or update an already-installed skill to the latest version. Trigger when users say: "open a PR", "submit my changes", "push this skill", "update my skills", "update the skills repo", or "how do I contribute a skill".
Analyzes staged and unstaged files from the full working tree, groups them into functional clusters (test, docs, chore, directory prefix), generates a conventional commit message per group, detects common issues (secrets, debug statements, large files), and executes one commit per group sequentially after presenting a multi-commit plan for confirmation. Falls through to a single-commit flow when all detected files resolve to one group. With the opt-in --review flag, first runs a coherence review over the working tree (delegating to /code-review) and surfaces its findings as non-blocking warnings before the commit plan. Trigger: When the user says "commit", "smart commit", or /commit. Add --review (e.g. /commit --review, "commit con review") to enable the coherence gate.
Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the user says "finish", "done", or "complete" in that context.
Guides Spring Boot version migrations: 2.7.x to 3.5.x, 3.5.x to 4.x, and minor upgrades within 4.x. Covers Java/Kotlin baseline upgrades, Jakarta EE namespace (javax to jakarta), Hibernate 5/6/7, Spring Security 5/6/7, modular starters, Jackson 3, Spring Framework 7, observability (Micrometer Tracing, OpenTelemetry), property and package relocations, JUnit 6, Testcontainers 2, MockitoBean, HTTP clients, resilience, AOT/native, API versioning, and OpenRewrite recipe automation. Supports all-at-once and gradual strategies with compatibility bridges. Java and Kotlin; Maven and Gradle. Trigger on requests like "upgrade/migrate to Spring Boot 3 or 4", "Spring Boot 2 to 3", "javax to jakarta", "upgrade to 4.1", "OpenRewrite Spring Boot", or any request moving a Spring Boot project to a newer major or minor version. Do NOT use for general Spring Boot development on a fixed version (new endpoints, services, JPA, tests) — use the spring-boot skill for that.
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
Design and build UIs with Google Stitch using @_davideast/stitch-mcp as the proxy and CLI. Covers screen generation, editing, variants, design systems, site building, prompt engineering, and the DESIGN.md spec. Updated for Stitch's March 2026 infinite canvas, 4-mode AI, and first-class design systems.
Integrates shadcn/ui into React apps generated from Stitch designs. Component discovery and installation, token alignment with Stitch design system, customization patterns, and blocks (auth, dashboard, sidebar). Use with stitch-react-components or stitch-nextjs-components.
Converts a Stitch mobile screen, a local HTML file, or a URL into SwiftUI views for native iOS apps — VStack/HStack/ZStack layout mapping, Color asset tokens with dark mode, NavigationStack/TabView routing, and Xcode project structure. Only the Stitch route needs an API key.
Invoke FIRST, before creating, editing, or deleting components, stories, styles, CSS, themes, colors, or design tokens — anything that changes how the UI looks, no exceptions. Also for starting or previewing Storybook to verify UI, requests to show, browse, or list components, stories, or UI states, and docs, props, or usage lookups.
Define well-structured user stories with acceptance criteria, sizing, and dependencies from project context. Use when breaking down features into implementable stories, refining a backlog, turning requirements or ideas into actionable tickets, preparing stories for sprint planning, or when someone says "create stories for this feature" or "break this down into tickets."
Carry UI designed and built in your design system's Storybook into the production product, all the way to a pull request. Assesses the work region by region, sorts real copy from placeholder content, translates the story's markup and styles into the product's own templates, wires it to the product's data, scripts, forms, and links, and proves in a browser that the product matches the story. Use when the user says "ship this story", "take this Storybook page to production", "port the redesign into the site", "carry this over from Storybook", "storybook to product", or points at a story and a product repo. The reverse of product-to-storybook, which brings product screens into Storybook. Also runs a catch-up that carries later Storybook changes over, one pull request at a time.
Implements the Syncfusion ASP.NET Core TimePicker component (EJ2). Use this skill when the user needs to add a time picker, time selection input, time field, or clock picker in an ASP.NET Core application. Trigger this skill for: TimePicker setup, time range configuration, strict mode, time masking, masked time input, globalization, RTL support, localization, accessibility, keyboard navigation, CSS customization, custom styling, form validation with TimePicker, TimePickerFor model binding, time format configuration, time step interval, floating label, clear button, full screen popup, popup behavior, scroll position, server timezone, and any scenario involving ejs-timepicker tag helper or Syncfusion EJ2 TimePicker.
Implements the Syncfusion .NET MAUI DatePicker (SfDatePicker) control for date selection. Use when implementing date pickers, adding date selection UI, or working with the SfDatePicker control. Covers date picker appearance customization (headers, footers, columns), date formatting (20+ predefined formats), date restrictions (min/max dates, blackout dates), and picker modes (Dialog, RelativeDialog).
Implements Syncfusion .NET MAUI DateTimePicker (SfDateTimePicker) control. Use when implementing date and time selection, datetime pickers, or date-time input interfaces in .NET MAUI applications. Covers DateTimePicker setup, formatting dates/times, picker modes (dialog/relative), customization, date restrictions, intervals, events, localization, and accessibility.
Structure a complete system design answer for interview questions or real architecture sessions. Use when asked to design a system, answer a system design interview question, or architect a solution at scale. Produces a structured answer covering requirements, capacity estimates, high-level design, component deep-dives, trade-offs, and follow-up considerations.
Build, review, debug, migrate, or plan TanStack Charts Alpha (0.18.x) charting with current docs. Use for @tanstack/charts, @tanstack/charts/react, @tanstack/charts/react-native, @tanstack/charts/scales/*, defineChart, scales registry (scales.x/scales.y, named scales, multiple axes), svgAnimation, motion(), tooltip/portal, layout stack/group, groupBy/binX/rollingWindow/rank/normalize/fold/waterfall/mosaic, lineY, areaY, barY (corner radius), boxY, violinY, waffleY, ridgelineY, differenceY, linearRegressionY, rect, cell, dot, hexagon, crosshair, whenFocused, decorative, facet, polar, geoShape, treemap, sunburst, sankeyDiagram, hexbin, contour, brushX, zoomX, keyedSelection, colorLegendItems, gradients, focusRing, Chart, Canvas, canvasChartRenderer, grammar-of-graphics marks/channels/scales, and migrations from Recharts, Chart.js, ECharts, Observable Plot, archived react-charts, @tanstack/react-charts, @tanstack/charts-scales, or pre-Alpha TanStack Charts 0.0.x–0.15.x (root x/y scales).
Set up and manage a Tapcart CLI project. Use when the user wants to get started with Tapcart development for the first time, or manage an existing project — including auth, dependencies, linting, logs, and layout dev server. The user only needs to provide their App ID for first-time setup — the agent handles everything else.
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.