Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Run an extremely strict maintainability review focused on abstraction quality, oversized files, and growth of spaghetti conditions. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Use when writing or reviewing working text: a repository page, a code comment, a description or help text, a PR, an issue, a CI comment, a Notion page, or a diagram that a colleague will scan to get work done, or when a change moves code across the layers an architecture page declares. Not for a paper, an essay, or any text read start to finish.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, define verifiable success criteria, keep a WORKLOG.md so work can be continued across sessions, and write research to research/ and plans for review to docs/.
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, “model-check this race”, “prove this invariant”, or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
Integrate the ONE store H5 Game SDK (Web SDK) into an HTML5 web game, check the integration status, and review the code before release. Use when the conversation mentions ONE store, OneStore, 원스토어, web game, 웹게임, HTML5 game, H5, WebView game, in-app purchase, 인앱결제, ads, 광고, rewarded or interstitial ads, createSDK, ONEstoreH5, initializeAsync, startGameAsync, purchase, getProductDetailsAsync, showRewardedAsync, or an iframe-hosted game, or when the user sends a command word such as doctor, integrate, iap, ads, embed, fix, or check to this skill. Covers loading the SDK, the boot flow (init, loading, start), lifecycle handling, ad and purchase code, iframe embedding requirements, error (reason) diagnosis, a blank screen in the app, and pre-release checks. When asked to write ad, purchase, or lifecycle code for a ONE store web game, use this skill instead of writing it from scratch, because it contains reference code based on the official sample.
Configure and use the SAP AI Core Orchestration service: build prompt templates, add content filtering, set up document grounding (RAG) pipelines, and call models via the Harmonized API. WHEN: user asks about the orchestration service, Harmonized API, prompt templating with variables, content filtering, grounding, RAG pipeline, document grounding, or building a pipeline that wraps an LLM. DO NOT USE FOR: creating an orchestration deployment — use `aicore-lifecycle-management` for that; credential setup — use `aicore-admin-resources`; browsing or deploying foundation models directly without a pipeline — use `genai-hub-foundation-models`; direct LLM inference without a pipeline — use `aicore-sdk-java` or `aicore-sdk-js`
Implement the confirmed requirements of the current project as actual features, screens and behavior, and perform basic checks appropriate to the implementation scope. Use for requests to write or change code, such as "build a service", "continue development", "implement the next feature" or "complete this based on these materials". Do not use when the request is only to define product direction, generate sample data, connect persistent data, fix an existing issue, validate or deploy.
Design and connect the persistent data structures and safe read/write operations required for the current project's core flows. Use when data must persist across runs, with requests such as "save the data", "connect a database", "connect Supabase" or "I want to view application records". Do not use when only static, temporary or mock data is needed.
Turn the user's business problem, idea, and supplied materials into an implementable product definition. Gradually clarify missing user, business, or UX information, whether the user has no idea, only partial context, or a clear idea with gaps. Use for requests such as “help me define what to build,” “flesh out this idea,” “create a requirements document,” or “create a PRD” when determining the user, problem, scope, acceptance criteria, and experience direction before implementation. Do not use when the product definition and UX direction are already settled and the user only requests code changes.
Reproduce and fix the cause of a current project issue based on the user's action, actual result and desired result. Use when correcting unexpected behavior, such as "I did A, but B happened", "there's an error", "it works locally but not after deployment", "the data isn't saving" or "fix it". Do not use when the user only wants to revert to a previous state without fixing the cause.
Set up Git, AGENTS.md, CLAUDE.md, and the initial commit point for a new project in a practically empty folder. Use for requests such as “set up the project,” “create a new project,” “prepare the workspace for a new project,” or “initialize this empty folder.” Do not use in folders that already contain code or project configuration.
Restore code and project files to a previous working state, or reapply changes that were just reverted, while preserving current work—even if the user does not know Git terminology. Use for requests such as “revert this,” “go back to the previous state,” “undo the recent changes,” “reapply that,” or “put it back the way it was.” Do not use to fix the cause of a current problem or to restore only external data, environment variables, or deployment state.
Generate working Java boilerplate for SAP GenAI Hub using the SAP AI SDK for Java (com.sap.ai.sdk). Covers chat completion, streaming, multi-turn conversations, prompt templates, content filtering, data masking, embeddings, RAG/grounding, prompt registry, and Spring Boot streaming. WHEN: user asks for Java or Kotlin code that calls a GenAI Hub model, wants a Java starter project, asks how to use com.sap.ai.sdk in their app, or asks how to integrate AI Core into a Spring Boot or plain Java application. DO NOT USE FOR: JavaScript/TypeScript code — use `aicore-sdk-js`.
Generate working TypeScript/JavaScript boilerplate for SAP GenAI Hub using @sap-ai-sdk/orchestration, @sap-ai-sdk/foundation-models, @sap-ai-sdk/openai (native OpenAI SDK), @sap-ai-sdk/langchain (LangChain), @sap-ai-sdk/document-grounding (RAG), @sap-ai-sdk/prompt-registry, @sap-ai-sdk/llm-batch (batch jobs), @sap-ai-sdk/rpt (tabular prediction), or @sap-ai-sdk/context-registry (data destinations, tabular artifacts, scenario configurations). WHEN: user asks for TypeScript, JavaScript, Node.js, or JS/TS code that calls a GenAI Hub model, wants a TypeScript starter project, asks how to use @sap-ai-sdk in their app, asks how to use LangChain (JS/TS) with SAP AI Core, or wants JS/TS for RAG/document-grounding, prompt templates, batch LLM jobs, tabular (RPT) prediction, or managing data destinations / tabular artifacts / scenario configurations via the Context Registry. DO NOT USE FOR: Java code — use `aicore-sdk-java`.
Build an InboxParse email integration in a Next.js App Router app: a typed server-only client for the V1 API, a signed webhook receiver, a scheduled sync that stores every email whether or not a webhook arrived, and replies sent only after a person approves the exact text. Use when: (1) an app must receive, store, search or answer email from Gmail or IMAP mailboxes connected to InboxParse, (2) adding or auditing an InboxParse webhook endpoint, sync job or send and reply flow, (3) feeding email into an AI feature without letting the email's author steer it, (4) calling the InboxParse API directly for emails, threads, search, mailboxes, labels, contacts, webhooks or usage, (5) the user mentions: InboxParse, inboxparse.com, email API, email-to-LLM, parse emails, email webhook, X-InboxParse-Signature, whsec_, ip_ API key, INBOXPARSE_API_KEY, email.received, email.ai_processed, ai.suggested_response, /api/v1/emails, rate_limit_exceeded. Carries the facts the API reference leaves out, checked against the implementation: deliveries carry ids, never the email, are retried up to 5 times and disable the subscription after 10 failures; the signature covers the raw body with no timestamp; the list cursor pages on sent_at alone. Next.js App Router; the InboxStore interface is the seam, so Postgres, Supabase or Firestore holds the state. Not a mail server, not an email client UI, and not the InboxParse MCP server.
Links a PostHog error occurrence or session's errors to OpenTelemetry traces, logs with the same trace ID, and Session Replay. Use when the user asks for trace or span IDs on an error, same-trace logs, or backend traces for errors in a session. Starts from an occurrence UUID, session ID, or error tracking issue URL. For a general issue diagnosis or replay summary, use investigating-error-issue or investigating-replay.
Use when working with mise (mise-en-place) or planning to update mise.toml. If the project uses mise, consult it even for one-line edits to mise.toml/hk.pkl, hooks, or CI tool setup, as it has the practices and security defaults you'd otherwise skip. Trigger on the intent even when the user never says “mise” (e.g. “update/pin the node version”, “set up pre-commit”) as long as the project already uses mise. Don't load for routine mise use (run/install/trust) that isn't changing config. Optionally use the skill to transform local development into using mise, aka (mise-fy).
Build India's NHCX (National Health Claims Exchange) provider-side claims integration into an existing HMIS codebase, end to end: beneficiary policy search, coverage eligibility, the payer's insurance plan, pre-authorisation, payer queries, claim, reprocess and release, and payment notices, with the NHCX gateway (JWE, x-hcx headers, ABDM session tokens, registry, callbacks) embedded in the application. Use when adding NHCX or PMJAY cashless claims to a hospital system as a whole, or when unsure which part of NHCX is needed.
Add, create or generate a Dapr Workflow that runs on Diagrid Catalyst — the orchestrator, its activities, and the project wiring. Use for a workflow, orchestration, saga, pipeline or long-running multi-step process. Infers the repo's language
Clarify a real project's unresolved decisions from inspected project facts and return a bounded handoff artifact. Use only when the user explicitly invokes $project-clarify after readiness or when a project needs formal clarification; it does not create a SPEC, tickets, or automatically start another user-invoked stage
Turn a formal SPEC into tracer-bullet vertical slices with blocking edges, then publish them as single-file-per-ticket issues on the local markdown tracker. Use only when the user explicitly invokes $project-tickets; it verifies the SPEC handoff, drafts a quiz-able breakdown, and hands execution to the frontier via light-implement
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
Build, review or research interface motion: press feedback, menus, tooltips, dialogs, sheets, toasts, accordions, tabs, page and shared-element transitions, scroll effects, drag and gestures, number and icon changes. Decides whether something should animate at all, then picks the tool, properties, curve, duration or spring, interruption and reduced-motion behavior, with tested modern-CSS recipes and runnable assets. Also studies recorded motion from Seenry references
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Implements a PostHog API (headless) survey inside the user's own codebase so it renders with their UI components and captures the exact events PostHog expects, then verifies the first response arrived. Use when asked to implement a survey, build a headless survey, build a custom survey UI, render a survey in my app, or wire up a survey of type `api` in a browser, server, or custom mobile UI. Covers the posthog-js event contract, server-side SDK capture, and post-implementation verification through MCP. To design or create the survey definition, use creating-surveys instead. For a survey that is implemented but not showing or not recording, use debugging-surveys.
Design and build web interfaces at design-studio quality, not AI-template quality. Use for any new page, landing page, dashboard, app shell, pricing, settings, form or single component, web or mobile (native app screens with seenry-apps), for redesigns and visual polish, and for matching a reference. Designs the brand's identity first, the way studios do (a truth, a type voice, one color field, one graphic device, one image treatment), studies real identities, studio sites and category leaders from Seenry MCP, builds the page as an application of that identity on a proven product and motion floor, and does not finish until a strict slop check passes and a blind critic scores the page at big-company level
Design and build native-feeling mobile app screens and flows (SwiftUI, UIKit, React Native, Expo, Flutter, mobile web prototypes) that match top App Store apps. Use for onboarding, tab and stack navigation, lists, forms, settings, paywalls, players, sheets and empty or error states. Researches whole journeys in real apps via Seenry MCP (the flow from the app it is based on, the look from the app it should look like), then enforces navigation doors, a mechanical slop pre-flight and a beat-the-reference gate
Operate Veer-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Veer's embedded browser through the `veer` CLI. Use when the user says "$veer-cli", "Veer worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Veer terminal", "handoff" / "handover" / "give this to another agent", "Veer browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Veer state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
Comprehensive reference for authoring FlyDSL GPU kernels on AMD GPUs. Covers the layout algebra, tiled copy/MMA, buffer ops, loop-carried range loops, SharedAllocator (LDS), autotuning, and common patterns. Use when writing, reviewing, or understanding FlyDSL kernel code.
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
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.