Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
REQUIRED for any Pharos blockchain task. This skill contains the RPC endpoints, chain IDs, explorer URLs, and token addresses needed to run cast/forge commands on Pharos — without reading it you will use wrong network config. Invoke whenever the user mentions "pharos", "PHRS", "PROS", "atlantic-testnet", or wants to do anything on the Pharos network: check balances, query transactions, call contracts, send transfers, deploy or verify Solidity contracts, run batch airdrops, or generate Web3 scripts targeting Pharos Chain / Pharos Network. Do not attempt Pharos on-chain operations without this skill.
Guide for building Android apps that integrate with the Ping Orchestration Android SDK (also referred to as the Ping Identity Android SDK, formerly the ForgeRock Android SDK / forgerock-android-sdk; Gradle artifact: `com.pingidentity.sdks:android`; modules: `journey`, `davinci`, `oidc`, `fido`, `protect`, `externalidp`, `binding`, `oath`, `push`). Covers both new project scaffolding and adding the SDK to an existing app. Use this skill whenever the user is: (1) building any Android app that authenticates against PingOne, PingOne Advanced Identity Cloud (AIC), PingAM, or DaVinci using Journey, DaVinci, or OIDC flows; (2) configuring SDK modules (Journey, DaVinci, OIDC, FIDO/passkeys, Protect, ExternalIdP, OATH, Push, Device Binding); (3) rendering Journey callbacks or DaVinci collectors in Jetpack Compose; (4) troubleshooting Ping authentication flows in an Android app; (5) setting up token or session storage with `EncryptedDataStore`; (6) scaffolding a new Android/Kotlin project for a Ping-authenticated app; (7) implementing OIDC centralized login with `OidcWebClient`, handling browser redirects, or wiring the redirect URI intent filter for OAuth 2.0 authorization code flows. Invoke proactively even when the user phrases it loosely — "add PingOne login to my Android app", "how do I set up Journey in Android", "how do I add OIDC centralized login", "make this look like a Ping sample app", "use the Ping Android SDK", "integrate pingidentity sdk on Android", "use forgerock-android-sdk", or "migrate from ForgeRock to Ping on Android".
Guide for building iOS apps that integrate with the Ping Orchestration iOS SDK (also referred to as the Ping Identity iOS SDK, formerly the ForgeRock iOS SDK / forgerock-ios-sdk; Swift Package: `Ping/ping-ios-sdk`; modules: `PingJourney`, `PingDavinci`, `PingOidc`, `PingExternalIdP`, `PingProtect`, `PingOath`, `PingLogger`, `PingStorage`). Use this skill whenever the user is: (1) building any iOS app that authenticates against PingOne, PingOne Advanced Identity Cloud (AIC), PingAM, or DaVinci using Journey, DaVinci, or OIDC flows; (2) configuring modules (Journey, DaVinci, OIDC, FIDO/passkeys, Protect, ExternalIdP, OATH, Push); (3) rendering Journey callbacks or DaVinci collectors in SwiftUI; (4) troubleshooting Ping authentication flows in an iOS app; (5) setting up token or session storage with `KeychainStorage`; (6) scaffolding a new Xcode project for a Ping-authenticated app; (7) applying Ping Identity branding to a sample app; (8) implementing OIDC centralized login with `OidcWebClient`, configuring `ASWebAuthenticationSession` or `SFSafariViewController`, handling browser redirects, or wiring `onOpenURL` for OAuth 2.0 authorization code flows; (9) analysing a PingAM/AIC Journey export JSON to identify required callbacks and generate a matching iOS sample. Invoke proactively even when the user phrases it loosely — "add PingOne login to my iOS app", "how do I set up Journey in Swift", "add OIDC centralized login", "make this look like a Ping sample app", "use the Ping iOS SDK", "use the PingSDK in my iPhone app", "integrate ping-ios-sdk", or pastes / attaches a Journey export JSON.
Use when building ReactJS web authentication with Ping Identity — scaffolds a complete React SPA authentication flow using the Ping Orchestration JavaScript SDK (`@forgerock/journey-client`, `@forgerock/oidc-client`) against PingOne Advanced Identity Cloud (AIC) or PingAM. Handles Journey client configuration, OIDC token exchange, dynamic Journey callback rendering in React, protected routes, user profile, and logout. Invoke when the user asks to "use @forgerock/journey-client in React", "render Journey callbacks in a React app", "set up Journey authentication with React and Vite", "add PingAM login to my React SPA", "integrate AIC Journey in React", or "build a React app with Ping Identity Journey". Also covers migrating a React app from `@forgerock/javascript-sdk` to `@forgerock/journey-client`.
Write the release notes for a Playwright release - the Node.js notes in docs/src/release-notes-js.md together with the Python, Java and .NET translations, and the GitHub markdown for each language's release. Use when asked to write, translate or publish release notes
Install Polar monetization components from the Elements registry. Use when user needs pricing cards, sponsor grids, subscription badges, revenue displays, or license key inputs. Triggers on "polar", "monetization", "pricing card", "subscription badge", "sponsor grid", "license key", "revenue card", "sponsorship", "pricing page".
Use when setting up or starting a project and you want to install the optimal skill stack for it. Triggers on phrases like: "set up skills for this project", "install project skills", "what skills should I use", "power engineer setup", "configure my skill stack", "power engineer frontend", "power engineer status", or any request to set up Claude Code skills for a new or existing project. Also triggers on targeted requests like "power engineer backend", "power engineer devops", "power engineer ai", "power engineer data", "power engineer docs", "power engineer mobile", "power engineer quick", "power engineer catalog", "power engineer update", "power engineer configure", "power engineer drift". Even if the user just says "/power-engineer frontend" or similar shorthand, this skill handles it.
Create a Pull Request (PR) or Merge Request (MR) from the current branch to a target branch asked of the user, with mandatory blocking quality gates before creating it: run quality-check, code-review, and trace-validate (all three must return an approved verdict) and, if docs/policies/definition-of-done.md exists, verify the code against that Definition of Done. Works on any git repository with a remote: auto-detects the platform (GitHub, GitLab, Bitbucket, Gitea, Azure Repos, etc.) from the remote and uses the available CLI. Auto-generates the title and description from the commits and creates the PR in a single pass. Always use whenever the user asks to create, open, generate, raise, or submit a PR, MR, pull request, or merge request, even if they only say "create the PR" or "push it to develop" without naming the platform.
For scenarios involving batch pull requests to ruan-cat related repositories, syncing changes across repositories, planning a PR strategy for multiple cloned local repositories, and choosing a mixed execution approach of local git/Bash with the GitHub API/MCP. Trigger keywords include "批量 PR", "多仓库同步改动", "对 ruan-cat 的仓库发 PR" and "pr-ruancat-repo".
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
Manages a GitHub Project board + Issues as the source of truth for product backlog, tasks, stories, and bugs. Provides five flows: bootstrap (/track-init), plan an epic with hierarchy (/plan-epic), migrate flat boards to a hierarchy (/plan-migrate), track ad-hoc work (/track), and query (/backlog). Uses gh CLI for project operations and MCP tools for issue creation. Trigger: /track-init, /plan-epic <description>, /plan-migrate, /track <description>, /backlog, "qué tenemos pendiente?", "what's pending?", "acordate que hay que...", "remember to...", or when SDD generates tasks via sdd-tasks.
Build, debug, or plan work with The Prompting Company through its API, MCP Server, CLI, or SDK entrypoints. Use when the user needs public routes, OpenAPI schema guidance, TypeScript SDK integration, CLI workflows, MCP setup, content APIs, app publishing APIs, public markdown access, simulations, visibility analytics, authentication, or API key scopes.
Build a throwaway prototype to answer one design, logic, data-model, state-machine, or UI question before committing to production code. Use when the user asks to prototype, sanity-check an approach, mock up a UI, explore design options, compare flows, or reduce uncertainty with disposable code.
Use this skill for reinforcement learning tasks, including high-performance RL training, custom environment development, vectorized parallel simulation, multi-agent systems, or integration with existing RL environments (Gymnasium, PettingZoo, Atari, Procgen, etc.). Use it to implement PPO training, create PufferEnv environments, optimize RL performance, or develop policies with CNNs/LSTMs.
Expert Python backend code reviewer that identifies over-complexity, duplicates, bad optimizations, and violations of best practices. Use when asked to review Python code quality, check for duplicate code, analyze module complexity, optimize backend code, identify anti-patterns, or ensure adherence to best practices. Ideal for preventing AI-generated code from creating unnecessary files instead of imports, finding repeated validation logic, and catching over-engineered solutions.
Ultimate RabbitMQ expertise skill for production-grade message broker architecture, implementation, and operations. Top 0.01% knowledge covering: (1) Advanced messaging patterns - Dead Letter Exchanges, Delayed Messages, Priority Queues, Consistent Hash Exchange, Sharding, (2) High Availability - Clustering, Quorum Queues, Stream Queues, Federation, Shovel, (3) Performance Engineering - prefetch tuning, connection pooling, batch publishing, memory optimization, flow control, (4) Security - TLS/mTLS, OAuth2, LDAP, certificate rotation, (5) Monitoring - Prometheus metrics, custom health checks, anomaly detection, (6) Troubleshooting - memory alarms, network partitions, queue backlogs, consumer starvation, (7) Multi-tenancy - vhost design, resource limits, isolation patterns, (8) Event-driven architectures - CQRS, Event Sourcing, Saga patterns with RabbitMQ. Use when: building messaging systems, debugging RabbitMQ issues, optimizing performance, designing HA architectures, implementing advanced patterns, production hardening, capacity planning, migration strategies.
Inspect an agent codebase and write a markdown plan wiring Langfuse tracing/observability (session/trace boundaries, sub-agent handoffs, tool wrapping, naming/tagging vocabulary) plus a Ratel-value/agent-health dashboard build-spec. Use to instrument Langfuse, wire up tracing, set up dashboards, decide where Langfuse goes or what to put on the board, onboard a just-signed partner, or `/ratel-langfuse-integrate`. Writes to <repo>/.ratel/; never edits code or calls the Langfuse API. The Langfuse branch of /ratel-observability-assessment; redirects if the vendor is LangSmith; routes to /ratel-langfuse-analyze once traces flow.
Inspect an agent codebase and write a markdown plan wiring LangSmith tracing/observability (run-tree boundaries, sub-agent handoffs, tool wrapping, run-naming/metadata vocabulary) plus a Ratel-value/agent-health dashboard build-spec. Use to instrument LangSmith, add @traceable/wrap_openai coverage, group runs into threads, design dashboards or Monitor charts, decide where LangSmith goes, onboard a just-signed partner, or `/ratel-langsmith-integrate`. Writes to <repo>/.ratel/; never edits code or calls the LangSmith API. The LangSmith branch of /ratel-observability-assessment; redirects if the vendor is Langfuse; routes to /ratel-langsmith-analyze once traces flow.
Create or update component documentation in Sentry's MDX stories format. Use when asked to "document a component", "add stories", "write component docs", "create an mdx file", "add a stories.mdx", or document a design system component. Generates structured MDX with live demos, accessibility guidance, and auto-generated API docs from TypeScript types.
Use when choosing a React component pattern — custom hooks, control props, compound components, headless components, render props, container/presentational, or other architectural patterns. Includes 13 patterns with decision guide and 2025 popularity ranking.
Reverse-engineer minified or obfuscated JavaScript bundles. Primary tool: humanify (humanifyjs) — uses an LLM to rename mangled identifiers back to meaningful names. Default model: gemini-3.8-flash. Use when the user says 'deobfuscate this bundle', 'humanify this', 'rename minified vars', 'reverse engineer this JS', 'what does bundle.js do', or is working in a project with a deobfuscated `og/` or `modules/` folder fed by humanify. Covers humanify CLI invocation, the pseudo-TTY workaround for cursorTo crashes, single-module extraction from a bundle, and chaining with beautifiers.
Turns a Backstage plugin you are developing into a deployable Red Hat Developer Hub dynamic plugin artifact: run @red-hat-developer-hub/cli plugin export to produce dist-dynamic and dist-scalprum, choose shared, embedded and bundled dependencies, package as an OCI image, tgz archive or npm package, push to quay.io or another registry, and generate the SHA-512 or sha256 digest integrity values a deployment needs. Use for "export my plugin", "package the plugin as OCI", "push the plugin to a registry", --shared-package, --embed-package, plugin-manifest.json, or integrity hashes. For a failing export in the rhdh-plugin-export-overlays repository, use /rhdh-overlay instead.
Propagates an rhdh-plugins workspace change through overlays and rhdh-plugin-catalog (midstream): changeset + npm publish, overlays source.json to the Version Packages SHA, then a surgical catalog MR (overlay-repo/, workspaces/, plugin_builds/, .tekton PLR tags like 2.0.0--0.0.3) without a full sync-midstream --force-clone. Use when promoting plugin versions, waiting on npm @red-hat-developer-hub packages, bumping overlays repo-ref, or midstream Hermeto/lock/PLR updates for one workspace. For an overlays workspace edit outside this promotion chain, use /rhdh-overlay.
Diagnose Roblox gameplay, replication, performance, and runtime issues. Use when debugging Roblox bugs, Luau errors, replication issues, RemoteEvent problems, DataStore failures, UI not updating, physics/network ownership issues, memory leaks, or performance regressions in Roblox experiences.
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.
