Skills
98,067 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use when the user wants to research vulnerabilities and create opengrep/semgrep SAST rules, conduct security research on CVEs or CWEs with web search, generate detection rules from vulnerability analysis, or build comprehensive security scanning coverage for a codebase.
Use the `om` CLI for market data, alerts, scalar metrics and indicators, event-watch journals, research studies, runner/service control, and OpenMarket chart workspace actions. Always use `om` commands instead of calling exchange APIs directly.
Use when the user wants to iteratively improve an artifact under a hard correctness bound while minimizing a measured cost — refactoring a code module to cut complexity while its test suite stays green, OR speeding up a SQL query while it returns the same rows. Each iteration applies one focused change, checks a correctness gate that must pass, measures a metric that must drop, and keeps the change only if both hold, else reverts; loops to a plateau or budget. Not for adding features, fixing bugs, or any change that is allowed to alter behaviour or results.
Review and optimize application data access that uses Entity Framework Core (EF Core). Use for EF Core performance and correctness reviews of services, repositories, imports, and background jobs: slow or memory-heavy queries, excessive round-trips, hidden SaveChanges, premature materialization, dynamic query construction, result-graph tracking, bulk writes, DbContext lifetime or overlapping operations, search semantics, paging, raw SQL, and model/index coverage. Use whether or not EF Core owns the schema. For EF Core, not Dapper or raw ADO.NET.
Translation skill for validated Orbitant blog posts. Takes a Spanish article that has already been reviewed and approved by a human editor, and produces an English version optimised for English-speaking audiences. Keyword selection is not a literal translation but a search-intent-driven choice for the English market. Use this skill only on articles that have completed the full editorial and review process.
When the user wants to optimize order batching, group orders for efficient picking, or reduce picker travel distance. Also use when the user mentions "batch picking," "order grouping," "cluster picking," "multi-order picking," "batch-and-sort," or "zone batching." For wave planning, see wave-planning-optimization. For picker routing, see picker-routing-optimization.
Conduct deep OSINT research on individuals. Build full digital footprint, psychoprofile (MBTI/Big Five), career history, social graph with confidence scores. Recursive self-evaluation until completeness threshold is met. Includes internal intelligence (Telegram history, email, vault contacts) before going external. Use when: "osint", "досье", "research person", "find everything about", "пробей", "разведка", "due diligence", "background check", "digital footprint", "найди всё про", "собери информацию", "кто это", "профиль человека". NOT for: company/product research without a named person, competitive analysis, market research, content generation, or general web scraping tasks.
Local speech-to-text on Apple Silicon with two cross-checking MLX engines: NVIDIA Parakeet TDT v2 (parakeet-mlx) and Qwen3-ASR 1.7B (mlx-audio, hotword biasing). Batch JSONL with word timestamps, confidence, provenance, and an agreement verdict. No NeMo or PyTorch. Use when transcribing audio files, identifying game or legacy voice clips by content, telling speech from SFX, serving an OpenAI-compatible STT endpoint, or dictating. For push-to-talk into any text field, use the Handy app.
Analyze parquet files using Python and Ibis. Use when the user wants to explore, transform, or analyze parquet data files, perform aggregations, joins, or export results. Works with local parquet files and provides database-agnostic data operations.
Particle system modifier development framework for Cocos Creator 2.4.x. Used to create, use, and debug custom particle modifiers, supporting modification of particle position, color, size, rotation, velocity and other properties. Use this skill when you need to implement complex particle effect control in Cocos Creator.
Computational pathology toolkit for analyzing whole-slide images (WSI) and multiparametric imaging data. Use this skill when working with histopathology slides, H&E stained images, multiplex immunofluorescence (CODEX, Vectra), spatial proteomics, nucleus detection/segmentation, tissue graph construction, or training ML models on pathology data. Supports 160+ slide formats including Aperio SVS, NDPI, DICOM, OME-TIFF for digital pathology workflows.
Fetch and analyze protein structures from RCSB PDB. Use this skill when: (1) Need to download a structure by PDB ID, (2) Search for similar structures, (3) Prepare target for binder design, (4) Extract specific chains or domains, (5) Get structure metadata. For sequence lookup, use uniprot. For binder design workflow, use binder-design.
Conduct authorized physical penetration testing against facilities, server rooms, and restricted areas using tailgating, RFID badge cloning, lock bypassing, rogue network device deployment, and security-guard procedure testing. Use as part of a full-scope red team engagement to evaluate physical security controls and their path to network access, always under signed client authorization.
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.
Run the PAIDF Orchestration Image Attribute Augmentation DAG on Kubernetes - person-crop clothing augmentation, attribute search, and augmented dataset generation. Select for requests about image attribute augmentation, person attribute search, person re-identification data, clothing augmentation, attribute captions, augmentation payloads, run status, or result retrieval. Runs environment setup first when controller readiness is unknown. Not for video or defect-image generation.
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`.
Generate, edit, and compose images with GPT Image 2.5, including transparent PNGs with a real alpha channel. Two backends — OpenAI API key or codex CLI (uses your ChatGPT subscription, no key needed). Four modes — one-shot generate, edit or inpaint an existing image, multi-reference composition (up to 16 inputs blended into one), and multi-image batch with verification. Use when the user asks to make an image, generate a poster, draw a mockup, design an icon or sticker, create an ad creative, build an infographic, blend reference images, edit or inpaint an existing image, or produce a cutout asset with a transparent background — "transparent PNG", "no background", "alpha channel", "works on any background". Not for: stripping the background off an existing image you want to keep (that's rembg or ImageMagick, not a generator); file operations that don't change the picture (compression, format conversion, resizing); reading, describing or OCRing an image; video.
Author, scope, and operate Polylane automations — unattended agent runs wired as trigger → instructions → tools → actions → destinations. Use when the user wants something to happen without them — "whenever X happens", "on every deploy", "every morning", "auto-rollback if it breaks" — including reacting to alerts, incidents, deploys, pushes, cron schedules, or webhooks; rolling back bad deployments automatically; auto-triaging alerts into issues; scheduled reports and recurring production health checks; incident-response automation; and routing results to Slack, email, or webhooks. Retrieve from Polylane docs — never guess commands or schemas.
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
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.
Use when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch. Reads the branch diff and commit messages, writes a structured PR body (summary, changes, testing), and optionally creates or updates the PR via the gh CLI.
Use when breaking a large, complex, messy, or hard-to-review pull request into multiple smaller PRs; planning stacked PRs; extracting independent changes from a branch; splitting mixed refactor and behavior changes; managing drift after review feedback; rebasing follow-up PRs as earlier PRs change; or preserving original branch intent while shipping incrementally.
Run a change-gated, branch-scoped lint preflight (ESLint / markdownlint / actionlint) on the files a branch changes versus its base, classify each violation as introduced vs pre-existing, and drive the fix/defer loop via an exit-code contract (0 pass, 1 introduced/blocking, 2 pre-existing only). Use when asked to run preflight, check whether a branch will pass lint before pushing, or as the lint gate inside a ship/PR flow. Lints only the categories the branch touched — not a whole-repo lint — with linted workspaces and the base branch auto-detected, so a consuming repo configures nothing in the common case.
Press release writing in AP style with inverted pyramid structure. Covers formatting, datelines, quotes, boilerplates, and fact-checking. Use for: product launches, funding announcements, partnerships, company news, events. Triggers: press release, pr writing, media release, news release, announcement, product launch announcement, funding announcement, company news, media advisory, ap style, press statement, news wire
Tell it what your product is (URL or description) and it finds 5 competitors globally, fetches their actual pricing pages, extracts every tier and price point, and returns a complete pricing intelligence report: the dominant pricing model in your space, a benchmark price table, feature gate analysis, competitive positioning map, and a concrete recommended pricing strategy for your product. Use when asked to research competitor pricing, find pricing benchmarks, decide how to price a product, understand pricing models in a space, or build a pricing strategy.
Create and manage agentic wallets with Privy. Use for autonomous onchain transactions, wallet creation, policy management, and transaction execution on Ethereum, Solana, and other chains. Triggers on requests involving crypto wallets for AI agents, server-side wallet operations, or autonomous transaction execution.
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.