Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use this skill when a process step should call a common service without custom code — REST, Slack, email, Kafka, AWS, Salesforce, and similar — even if connectors aren't mentioned. Finds, configures, and applies Camunda 8's pre-built connector templates to BPMN elements with c8ctl. Not for building new connectors; use camunda-connectors-development. Covers c8ctl template discovery, configuration, application, and updates.
Connect the Vercel AI SDK to iMessage. Build AI agents and assistants that communicate over iMessage using chat-adapter-imessage, the official Photon adapter. Local mode (runs on your Mac) and remote mode (Photon's production infrastructure). Covers createiMessageAdapter, postMessage, editMessage, deleteMessage, react, startGatewayListener, types, and integration with the Chat SDK. Keywords: vercel ai sdk, imessage, chat adapter, ai agent, chatbot, conversational ai, messaging, apple messages, vercel, nextjs, ai assistant, chat sdk, real-time, macos.
Use when writing new code, naming modules/files/functions/variables, reviewing or refactoring for readability, reducing complexity, deciding whether an abstraction belongs, or reviewing with CUPID; also the constructive hacker ethos (curiosity, craftsmanship, open-source contribution, remove drudgery; never unauthorized access). Behavior-preserving refactors within a function, class, or file route to the `refactoring/` sub-skill. Pairs with language skills (typescript, go, lisper). DO NOT USE for behavior changes (`testing` (TCRDD reference)), cross-file dependency untangling (`mikado-method`), or pure simplicity/YAGNI debates (`simple`)
Transform the agent into a Cloud Solution Architect following Azure Architecture Center best practices. Use when designing cloud architectures, reviewing system designs, selecting architecture styles, applying cloud design patterns, making technology choices, or conducting Well-Architected Framework reviews.
Whole-codebase code quality audit system with 9 specialized sub-skills covering security, SOLID principles, architecture, error handling, performance, test quality, code smells, design patterns, and framework best practices. Produces a scored health dashboard (0-100 per category), severity-rated findings (P0-P3) with severity rationales, and copy-pasteable fix prompts; also does PR-style diff review vs a base branch. Strictly read-only — never modifies user code. Use when the user says "codeprobe", "audit", "full code review", "code health", "check my code", "security scan", "code smells", "SOLID check", or asks how healthy, risky, or maintainable a codebase is. (For reviewing just the working diff, the built-in /code-review may be more appropriate unless the user asks for codeprobe.)
Use this skill when users need to evaluate potential co-founders, assess founder compatibility, design equity splits, or navigate co-founder relationships. Activates for "should I work with this person," "co-founder fit," "equity split," or founding team questions.
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails. Also use when the user says 'cold call script,' 'phone script,' 'phone prospecting,' 'voicemail script,' 'call opener,' 'gatekeeper script,' 'dial block,' 'cold calling,' 'SDR script,' 'outbound calling.' For multi-channel sequence design, see outbound-sequence. For post-call analysis, see call-debrief. For discovery call planning, see discovery-call.
Synchronize Comet's Chinese and English docs, README, Skills, release notes, and website pages while preserving confirmed semantics, repository structure, submodule boundaries, and focused validation. Use when documentation changes must stay bilingual, or when Chinese wording needs a corresponding English version.
Prepare a Comet release or release notes update based on the real version and branch scope, keeping the changelog user-facing, the bilingual website docs consistent, generated assets validated, and the Git delivery boundary explicit. Use for beta, hotfix, version checks, release notes, or release readiness checks.
Unified pipeline for content production and distribution. Material collection → drafting → layout → cover → Moments copy → multi-platform conversion → one-click distribution. Covers WeChat official account writing, Xiaohongshu carousel images, Jike copy, podcast audio, brand videos, and Chrome CDP automated publishing.
Format commit messages, branch names, PR titles, and issue titles to the Conventional Commits 1.0.0 spec. Use BEFORE running `git commit`, `git checkout -b`/`git branch`, `gh pr create`, or `gh issue create`; before writing any commit message, branch name, PR title, or issue title; and whenever staging changes to commit or asked to \"commit\", \"make a PR\", \"open an issue\", or \"create a branch\" — or when another skill needs a spec-compliant commit message.
Language-level TypeScript conventions for every project, framework or not — compiler strictness, banning unsafe types, inference and `satisfies`, discriminated unions and branded ids, narrowing, generics, utility types, nullability, async, errors as `unknown`, module and language hygiene. The base skill that `react`, `angular`, `vue`, and `architecture-and-design` build on. Use it when writing, reviewing, or refactoring TypeScript, setting up `tsconfig.json`, or when the user says "TypeScript", "tsconfig", "strict mode", "type error", "any", "generics", "type safety", "utility types", "discriminated union", or "narrowing".
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
Creates and launches PostHog surveys through MCP, including NPS/CSAT popovers, hosted feedback forms, and headless surveys. Guides survey type selection, audience targeting, draft review, and launch readiness. Use when asked to create a survey or form, or before calling survey-create. For investigating an existing survey's delivery or responses, use debugging-surveys instead.
Assess Splunk data-model and report-acceleration readiness, summary coverage, and troubleshooting evidence without changing a deployment. Use for data-model object readiness, acceleration enablement, build or lag state, incomplete summaries, report acceleration, summary sharing, and choosing whether an acceleration mechanism fits a repeated search objective. Require validated field and CIM prerequisites, preserve ownership and deployment boundaries, and route SPL, normalization, governance, one-search tuning, and active platform incidents to their owners.
Data visualization with chart selection, color theory, and annotation best practices. Covers chart types (bar, line, scatter, heatmap), axes rules, and storytelling with data. Use for: charts, graphs, dashboards, reports, presentations, infographics, data stories. Triggers: data visualization, chart, graph, data chart, bar chart, line chart, scatter plot, data viz, visualization, dashboard chart, infographic data, data presentation, chart design, plot, heatmap, pie chart alternative
Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy, capture-replay (Rust), Kafka, ingestion-sessionreplay (Node), recording-api (Node), SeaweedFS, and common failure modes like orphaned processes, stuck phrocs workers, and trigger misconfiguration.
Use for Deepgram speech and voice production workflows: speech-to-text transcription, live captions, diarization, audio intelligence, Aura text-to-speech, Flux and Voice Agent live audio, model selection, cost/limits/privacy checks, artifact custody, and production QA.
Use natural language to create, query, edit, publish or delete DingTalk digital employees, manage their capabilities and resources, check execution status, save local Profiles, and connect to DSH. Use when the user asks to create or manage digital employees, change personas/roles/response modes, publish or ask about retiring a capability, check execution status or traces, manage digital employee Skills/MCP, convert an existing digital employee to a local Profile, or connect to local DSH. Command prefix: dws dingtalk-tag
Use this skill when the user is invoking doca_flow_dpa_perf on DPA-capable hardware (ConnectX-7 minimum supported, ConnectX-8 recommended, or BlueField-3) to measure rule update / disable rates on the DPA-offloaded DOCA Flow path — picking the active / passive device split, choosing workload-shape axes (burst, queue, completion threshold, workers, hash pipe algo, PSL tables), or reading Kops/sec iteration stats and the optional self-test. Trigger even when the user does not explicitly mention "doca_flow_dpa_perf" or "DPA Provider" — typical implicit phrasings include "how fast can the DPA program path-selector entries", "baseline rule-update rate on ConnectX-8", "tool reports zero ops on my BlueField", "self-test sentinel never shows on tcpdump", or "is my BlueField-2 DPA-capable". Refuse and route elsewhere for the host / DPU-CPU Flow path (doca-flow-perf), Flow pipeline tuning (doca-flow-tune), writing doca-flow / doca-dpa applications, or DOCA install — those belong to other skills.
Use this skill for DOCA GPI work—configuring a GPU Packet Initiator so device code issues RDMA operations straight out of GPU-resident buffers via doca_gpi objects: domain creation and channel limits, attribute objects, the doca_gpu_gpi_channel* handoff consumed inside device code, and DOCA_ERROR_* triage on doca_gpi_* entry points such as doca_gpi_gpu_channel_get. Also load it for implied asks like "how many channels fit in a GPI domain" or "device code issuing one-sided RDMA". Refuse and route to the proper owner for Send/Receive semantics (doca-gpunetio), host-managed QP lifecycle (doca-rdma), Arm-side origination (doca-rdmi), or generic CUDA tutelage.
Not for writing library code (name that library skill). Use this skill whenever another DOCA skill says “prefer the structured tool per doca-structured-tools-contract”, or when the user wants a one-shot answer consolidating what multiple manual commands would produce—DOCA env / version / devices / capabilities / validate / host vs DPU state. Trigger even without the phrases “structured tool” or “doca-env --json”—typical phrasings include “is there one command that tells me everything about my DOCA install”, “what version is X capability available since”, “every PF/VF/SF visible on this BlueField with PCIe address”, or “will this pipe pass validate before commit”. Refuse and route elsewhere for general DOCA orientation, library API how-to, or install-from-scratch guidance—those belong to the per-library skill, doca-public-knowledge-map, or doca-setup
Email marketing design with layout patterns, subject line formulas, and deliverability rules. Covers welcome sequences, promotional emails, transactional templates, and mobile optimization. Use for: email marketing, newsletter design, drip campaigns, email templates, transactional emails. Triggers: email design, email template, email marketing, newsletter design, email layout, email campaign, drip campaign, welcome email, promotional email, transactional email, email subject line, email header image, email banner
Throw typed errors with TRPCError and error codes (NOT_FOUND, UNAUTHORIZED, BAD_REQUEST, INTERNAL_SERVER_ERROR), configure errorFormatter for client-side Zod error display, handle errors globally with onError callback, map tRPC errors to HTTP status codes with getHTTPStatusCodeFromError().
Governs Event Schema Sets, the Fabric registries of event types and message payload schemas. Covers create, rename, update and delete of a definition, and listing, property reads or base64 decoding. Every Event Schema Set task belongs here. Ingestion pipelines are eventstream-cli.
Use this skill whenever building, debugging, or extending a privacy-preserving payment dApp on the Midnight Network using the 1AM wallet, Compact smart contracts, and Next.js. Triggers include: any mention of Midnight Network, Compact contracts, tNIGHT tokens, 1AM wallet integration, ZK proving assets, midnight-js SDK, or deploying/calling circuits (deposit, withdraw). Also use when the user encounters errors like "Invalid character 'm' at position 0", "offset: null" GraphQL errors, balanceUnsealedTransaction failures, or WASM/WebSocket issues in Next.js with Midnight packages. Use this skill even for partial tasks like wiring a single provider, decoding ledger state, or debugging a stuck deploy transaction.
Orchestrate approved, bounded work through a same-directory Codex App fork: create and name the execution task, ask it to run spec-executor, route decisions through Codex Task Messenger, validate the returned receipt, and archive a completed child. The source may come from any planning workflow. Requires Codex App task tools and codex-task-messenger.
Convert a specific existing Lightning web component (LWC) into a declarative HXL / Agentforce widget, end to end. Gates on experience-lwc-widget-assess and stops when a widget cannot serve the LWC's purpose; otherwise hands the derived field shape to platform-widget-generate and wires the widget as the Lightning Type renderer. TRIGGER when: the user wants to convert, migrate, port, rebuild, or turn a named LWC into a widget or declarative Agentforce widget, or asks for a widget built from an existing LWC component. DO NOT TRIGGER when: the user only wants to know whether an LWC can become a widget (use experience-lwc-widget-assess), or wants a widget for a data shape, entity, or Lightning Type with no existing LWC (use platform-widget-generate or platform-lightning-type-widget-coordinate).
Configure Frigate NVR with optimized YAML, object detection, recording, zones, and hardware acceleration. Use when setting up Frigate cameras, troubleshooting detection issues, configuring Coral TPU/OpenVINO, or integrating with Home Assistant.
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.
