Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Use this skill to find and remove dead code, unused dependencies, duplicate logic, and unused exports using detection tools (knip, depcheck, ts-prune, deadcode, staticcheck). Trigger on "clean up dead code", "remove unused", "find dead code", "reduce bundle size", "dependency audit", or when the codebase feels bloated. For simplifying living code (readability, naming, complexity reduction) without detection tools, use code-simplifier instead. Use this skill during maintenance windows or before major refactors.
Refactor Django/Python code to improve maintainability, readability, and adherence to best practices. Transforms fat views, N+1 queries, and outdated patterns into clean, modern Django code. Applies Python 3.12+ features like type parameter syntax and @override decorator, Django 5+ patterns like GeneratedField and async views, service layer architecture, and PEP 8 conventions. Identifies and fixes anti-patterns including mutable defaults, bare exceptions, and improper ORM usage.
Refactor React and TypeScript code to improve maintainability, readability, and performance. This skill transforms complex React components into clean, well-structured code following modern React 19 patterns. It addresses component bloat, prop drilling, unnecessary re-renders, and improper hook usage. Leverages React 19 features including the React Compiler for automatic memoization, Actions for form handling, useOptimistic for immediate UI feedback, the use() hook for async data, and Server Components for optimal performance.
[Deprecated] Use when building frontend Web apps that talk to CloudBase Relational Database via @cloudbase/js-sdk – provides the canonical init pattern so you can then use Supabase-style queries from the browser. New environments should use PostgreSQL with app.rdb() — see postgresql-development skill instead.
Use the official Remix CLI for authentication, config inspection, game creation, uploads, and analytics. Trigger this skill when a task involves `remix login`, `remix whoami`, `.remix-cli.json`, `REMIX_API_KEY`, or terminal-based game management on Remix.
Learn this codebase from its live files — evidence-qualified lessons and a browser workbook for unfamiliar or agent-authored code. Prefer optional tools silently when already available; otherwise use bundled scripts with the same UX (no tool jargon in user chat, no confidence inflation). Ask only before install/config changes. Hard overclaim rule: unsupported → shrink scope or refuse — never "continue weaker?". Scripts and the agent take turns; follow nextAsks on script output.
Use when working on BK-CI repository integration, repository authorization, Webhooks, SCM integration, PAC switches, and differences between repository types. Prefer this when the user mentions Git/SVN/GitHub/TGit, Webhooks, repository authentication, PAC repositories, or commit records.
(NS) Generate structured requirements.md from scope descriptions, stack context, and design briefs for a product version. Use when starting a new version, the user asks for requirements, RF/features document, or before task generation when requirements.md is missing — even if they only describe the feature in chat. Follow SDD planning gates in nextstage-harness. Do NOT generate task files (use task-generator).
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code quality, DRY, refactor review.
Generates the Red Hat Developer Hub dynamic-plugins.yaml configuration that makes an exported Backstage frontend plugin appear in RHDH: derive the Scalprum name from plugin-manifest.json or the package name, and write the pluginConfig.dynamicPlugins.frontend block with dynamicRoutes, menuItems, mountPoints, appIcons, apiFactories, routeBindings, entity tabs, cards, context menu items, and provider components. Use for "generate the wiring for this plugin", "which mount point does this card need", entity page customization, importName, or a plugin that installs but never renders. To apply the configuration to a running instance instead, use /rhdh-local.
Enforcing the RED-GREEN-REFACTOR loop: write one failing test and watch it fail, write minimal code to pass, then refactor green. Use when starting implementation of a new feature or bugfix, or writing any new production code. Requires pasted failure output as proof of RED; code written before its test must be deleted, not stashed. Skip for exploratory spikes or when only modifying existing tests.
Use when the user installs or starts using Runway Dev, needs to sign in or create a Developer Portal account, connect Dev MCP, verify account/project access, or finish setup after a developer_not_found error. Guide the user through the browser steps and continue with the task once setup succeeds
Profile before optimizing, cut allocation out of hot paths, and treat LTO, codegen-units, PGO and target-cpu as the last five percent. Use when Rust code is too slow, when a benchmark regresses, when reviewing code that allocates or formats inside a loop, when release-profile or codegen flags come up, or when the user asks how to make Rust faster.
SaaS architecture mastery for Senior Full-Stack Developers. Use when the user needs to explain SaaS architecture, multi-tenancy, design scalable systems, evaluate architectural trade-offs, or prepare answers on system design. Activates on words like SaaS, multi-tenant, arquitectura, escalabilidad, tenant isolation, subscription, billing, feature flags, scaling. Specialized in platforms like HostelOS and Digitaliza.
CI-only self-healing workflow using gh-aw (GitHub Agentic Workflows) for active runtime recovery on pull requests and scheduled runs. When a CI check fails (test, build, lint, deploy, scan), this skill diagnoses the failure from CI logs, proposes a verified patch as a PR comment or follow-up commit, and commits a HEAL entry to `.learnings/HEALS.md`. Verify-before-persist discipline preserved: a HEAL is only `verified` if a re-run check passes in the same workflow; otherwise it ships as `pending-verify` for human follow-up. Recurrent heal patterns across PRs accumulate `Recurrence-Count` and append a `Handoff` block at ≥3 to flag promotion via self-improvement-ci. Use this skill when: you want headless heal-loop execution in CI/scheduled pipelines, you want recurring failure patterns captured automatically, or you want PRs that surface non-obvious environmental / tooling fixes without human triage. For interactive/local sessions, use `self-healing` instead.
Set up the `clickhouse-js` repository in a fresh checkout so the agent can run tests, lints, type checks, builds, or examples. Use this skill before invoking any `npm run test:*`, `npm run lint`, `npm run typecheck`, `npm run build`, or `npm run run-examples` script — or after pulling changes that touch any `package.json` (root, `examples/node`, or `examples/web`). Covers Node.js version requirements, installing dependencies across the npm workspaces and the two independent example packages, building the workspace packages so inter-package imports resolve, and starting ClickHouse via Docker Compose for integration tests. Do NOT use this skill for downstream user projects that merely depend on `@clickhouse/client` or `@clickhouse/client-web`; it is specific to contributing to the `ClickHouse/clickhouse-js` repo itself.
Build, restyle, or review accessible React interfaces that use shadcn/ui, Radix UI primitives, and Tailwind CSS. Use for component composition, responsive layouts, semantic design tokens, dark mode, forms, dialogs, tables, keyboard interaction, and safe Tailwind configuration in React, Vite, or Next.js projects. Do not use for canvas art, posters, font bundles, non-React frameworks, or general brand design.
Prepare a feature branch for a pull request: verify scope, sync when needed, test, review, push and open or update the PR. This skill MUST be used when the user requests this branch-to-PR workflow or explicitly invokes ship-it (開 PR、準備 PR、整理分支交付). It SHOULD be used when the user asks to prepare a completed feature for review. It MUST NOT be triggered solely by a push, merge, release, deployment request or a general readiness question.
Automated sitemap generation for all locale URLs, robots.txt configuration, and llms.txt for AI crawler optimization. Use when setting up sitemap.xml, configuring crawling rules, or improving discoverability for search engines and AI systems.
Expert in Solana blockchain development - Anchor framework, SPL tokens, program development, and high-performance dApp architectureUse when "solana, anchor framework, spl token, solana program, solana dapp, metaplex, phantom wallet, solana nft, solana, anchor, rust, spl-tokens, web3, blockchain, defi, nft" mentioned.
Specification quality checker for spec-generator documents. Validates requirement.md, design.md, tasks.md for consistency, completeness, and quality. Detects requirement ID mismatches, missing sections, contradictions, and ambiguous expressions. English triggers: "inspect specs", "check specification quality", "validate requirements" 日本語トリガー: 「仕様書を検査」「品質チェック」「仕様を検証」「spec-inspect実行」
Share a local iOS build with a registered iPhone that is not connected to this Mac. Cuts a cloud-signed build, uploads it to Speedflight (speedflight.dev), and posts a link in the chat that installs from Safari. Use it proactively, without being asked, whenever the user wants a build on their device and the device is not plugged in or reachable (run-on-device fails, "send me the build", "I'm away from my desk", "put this on my phone"). Also use on "/speedflight" or "share a build", to set up Speedflight for a repo, and when the user asks to add a device or a teammate's phone to Speedflight (mints an enroll link, pulls the UDIDs down, registers them with Apple).
Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.). Use when writing queries, optimizing slow SQL, translating between dialects, or building complex analytical queries with CTEs, window functions, or aggregations
SQLAlchemy Python ORM. Covers models, sessions, and queries. Use for Python database applications. USE WHEN: user mentions "sqlalchemy", "declarative_base", "DeclarativeBase", "Session", "Query", "relationship()", "alembic", asks about "python orm", "sqlalchemy models", "sqlalchemy async", "sqlalchemy relationships", "python database" DO NOT USE FOR: Node.js/TypeScript ORMs - use `prisma`, `drizzle`, or `typeorm` skills; Django ORM - use Django-specific resources; raw SQL - use `database-query` MCP; NoSQL - use `mongodb` skill; other Python ORMs (Peewee, Pony) - not supported
Comprehensive guide for building solutions with the sqlx Rust library. Use this skill whenever the user wants to: write SQL queries in Rust with compile-time checking; connect to PostgreSQL, MySQL, or SQLite databases using async Rust; set up connection pools with sqlx; run database migrations; use query macros (query!, query_as!, query_scalar!); map SQL rows to Rust structs with FromRow; handle transactions in Rust; use #[sqlx::test] for database testing; work with JSON columns in SQL; use PgListener for PostgreSQL LISTEN/NOTIFY; handle sqlx errors properly; configure sqlx feature flags in Cargo.toml; set up offline mode with cargo sqlx prepare; use QueryBuilder for dynamic queries; or implement the repository pattern with sqlx. Make sure to use this skill when the user mentions sqlx, Rust database, Rust PostgreSQL, Rust MySQL, Rust SQLite, Rust SQL toolkit, compile-time query checking, async database Rust, database migrations Rust, sqlx pool, sqlx macros, or any SQL database interaction in Rust.
Converts a Stitch screen, a local HTML file, or a URL into clean, platform-agnostic HTML5 + CSS — semantic markup, CSS custom properties for theming, dark mode via prefers-color-scheme, mobile-first responsive, zero framework dependencies. Works in browsers, WebViews, Capacitor, and Ionic. Only the Stitch route needs an API key.
Reviews Svelte components for idiomatic patterns, identifies anti-patterns carried over from React/Vue/Svelte 4, and suggests Svelte 5 refactorings. Use when writing or reviewing Svelte components, asking "is this idiomatic", "Svelte way", doing Svelte 5 migration, or encountering smells like: effect assigns state, prop copied to $state, global store by default, $bindable everywhere, clickable div, createEventDispatcher, export let, on:click, slot-shaped APIs, lifecycle-driven code, imperative DOM wiring, immutable-update ceremony, context value replacement, shadcn-svelte form structure, Field.* components, bits-ui form controls, or component APIs that hide ownership. This is the general-purpose entry point for Svelte component review; delegates to sveltekit for routes/load/actions/server concerns and to focused references for details.
Build, refactor, review, and debug native Apple-platform software in Swift. Use when working on `.swift` files, SwiftUI views, Observation-based state, `@Bindable` and binding flow, SwiftData-backed UI, scenes and windows, search/navigation structures, UIKit/AppKit interop, Liquid Glass adoption, macOS-native UX, or SwiftUI performance/accessibility. Trigger on requests to create or polish iOS, iPadOS, macOS, or visionOS features; clean up SwiftUI view structure; diagnose jank or invalidation storms; review app quality; or make a feature feel like a good Apple-platform citizen.
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.