Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.
Parses complex OpenAPI specs and generates Drift test cases from them. Use whenever the user wants to generate, write, or scaffold Drift tests from an OpenAPI spec — especially when the spec contains complex schemas: anyOf/oneOf/allOf, discriminators, polymorphism, inheritance, $ref chains, regex patterns, enums, or optional fields. Use when the user asks to "create tests for an endpoint", "cover all response variants", "generate test cases from the spec", or says anything like "each viable combination of responses". Use when the user is trying to understand what values are valid for a complex schema field, or when they paste a spec path and ask what tests to write.
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agent_insights_issue entities, offers to turn Diagnostics on when the project has it switched off, then fills the gaps with list (filters, sort, a time window); without the MCP it reads the same via the SDK (agent_insights and search_traces), so it works with no MCP. Returns a ranked shortlist, each item ready to hand to the explain skill. Use for "what is broken in production", "which traces need attention", "find failing or slow traces", "which tool calls are failing", "triage my agent". Not for offline experiment results (use evaluate or compare) and not for root-causing one trace (use explain).
Root-cause a specific Opik trace, or a pattern across traces, and return a grounded explanation. Uses the hosted Opik MCP when it is connected, and falls back to SDK scripting otherwise. Returns the root cause, the evidence spans as clickable Opik UI links, and one suggested next step. Use for "why did this trace fail", "explain this trace", "debug this trace", "why is my agent slow or wrong". Not for adding tracing to an app (use the instrument skill) or for changing code.
Бот или интеграция в Пачке: что выбрать (входящий вебхук, бот с событиями, приложение с авторизацией), создание и настройки бота, токены и права, доступ к чатам, приём событий (подпись, повторы, защита от дублей, история событий), кнопки, формы, разворачивание ссылок, витрина. Когда: «сделать бота», «уведомления из CRM или CI в чат», «входящий вебхук», «исходящий вебхук», «бот команд или уведомлений не получает сообщения», «проверить подпись вебхука», «кнопки в сообщении бота», «форма, модальное окно», «превью ссылок, unfurl», «права токена бота», «токен бота утёк», «опубликовать бота в витрине», "build a Pachca bot", "incoming webhook", "outgoing webhook", "bot gets no events", "verify webhook signature", "message buttons", "modal form", "link unfurling", "reissue a leaked bot token". Not for: an AI agent that answers in threads or does not hear a mention → pachca-ai-agent; an app acting for an employee → pachca-oauth; scripts, pagination, 429 → pachca-api; writing messages yourself → pachca-messaging.
This skill should be used whenever the user mentions "pbir", "pbir-cli", "Power BI reports", or "PBI reports", works with .pbir, .pbip, or .pbix files, or wants to refresh, screenshot, or visually verify a report that is open in Power BI Desktop. Covers creating, exploring, formatting, validating, and publishing Power BI reports through the pbir CLI and object model, plus driving Power BI Desktop (canvas reload, page screenshots) and querying connected or local semantic models.
Expert in generating, parsing, and manipulating PDF documents using tools like PDFKit, PDF.js, and Puppeteer. Use when creating PDFs, extracting content, merging documents, or filling forms. Triggers include "PDF", "generate PDF", "parse PDF", "extract PDF", "merge PDF", "PDF form", "PDFKit".
Camp Personalization vs No Personalization playbooks by outreach category - Inbound, Postbound, Bridgebound, and Outbound. Use when deciding personalization level, building automated sequences, or creating messaging templates.
This skill should be used when the user needs to consume the Pier Cloud (Lighthouse) API for cloud cost management — including JWT authentication, listing contexts, workspaces, workspace groups, and FinOps data views. Trigger whenever there is a need to integrate, automate, or debug calls to the Pier Cloud platform via Python, Node.js, or cURL.
Use when the user wants to create, read, or rewrite a Pipefy HTML interface: a standalone page whose content is one HTML document, optionally showing live data from pipes and tables. Covers choosing data sources, creating the page, and rewriting it. Needs HTML interfaces enabled on the organization. For the main portal, its grid-layout pages, and sub-portals, use `pipefy-portal-setup`.
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
Build, revise, resize, export, and quality-check editable Point paid-social templates in PowerPoint and Canva-compatible formats. Use for seasonal or campaign social assets that require separate editable copy, logos, benefit rows, legal footers, and illustrations; approved Point brand assets; preview PNGs; transparent illustration exports; or production preflight.
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
Set up and run Airtable-based product operations workflows — roadmap management, customer feedback synthesis, launch coordination, OKR cascading, sprint planning, release tracking. Use when the user wants to track product work, manage feature requests, build a roadmap, set up a feedback intake portal, prioritize initiatives, run launch checklists, or align OKRs across teams. Adapts to org size (solo founder, small team, mid-size product org, enterprise product portfolio) and existing tooling (Jira / Linear / Productboard / Aha integration; Salesforce / Zendesk / Gong feedback ingestion). Can scaffold either as a pure-Airtable workspace or as Airtable backing a custom branded UI on Vercel for public-facing portals. Asks scope questions first; doesn't impose framework. Focuses on cross-functional product operations.
Set product vision, positioning, market strategy, and portfolio direction with a CPO methodology. Route tactical prioritization, specifications, and backlog decisions to `product-methodology`; do not use this skill for delivery-level product decisions or unrelated requests.
Manage projects, tasks, and priorities effectively as a solopreneur. Use when organizing work, tracking progress, managing deadlines, coordinating with contractors or clients, or building project management systems. Covers task management methods, prioritization frameworks, project planning templates, tool selection, and personal productivity workflows. Trigger on "project management", "manage my work", "organize tasks", "project planning", "task management", "prioritization", "stay organized".
Develop evidence-backed structural security hardening proposals from disclosures, findings, source code, or Codex Security scans. Use for systemic improvements, alternatives beyond individual patches, architectural tradeoffs, or implementation planning. Also use when a top-level scan requests final-report hardening guidance
Write, configure, and remotely update PUDA Python edge services. Use when creating or editing driver.py or main.py, adding @command or @safety, scaffolding from the SDK/API or GUI edge templates, integrating a new machine, building GUI-controlled instruments from manuals or screenshots and task instructions, or running puda machine update.
Implement code against an existing Quint specification. Uses Research → Plan → Implement workflow (ACE-FCA style) grounded by the spec as the source of truth. Use when the user wants to refactor code, add a new feature, or close a gap between implementation and spec — with the Quint spec as the formal constraint that all changes must satisfy.
Use when a React Native app uses or is choosing the react-native-video library — playing/controlling video or audio, the v6 `Video` component or the v7 `useVideoPlayer`/`VideoView` player API, source/props/events (onLoad, onProgress, onEnd, paused, resizeMode, source, drm), HLS/DASH, DRM (Widevine/FairPlay, `@react-native-video/drm`), captions/tracks, Picture-in-Picture, background or lockscreen audio, fullscreen, buffering, offline/downloading, or native iOS/Android setup; also when deciding between v6 and v7 or migrating between them. Triggers on "react-native-video", "RNV", `Video`, `useVideoPlayer`, `VideoView`, and similar.
Run Rejudge — send a question to separate reviewers and a judge, returning one reviewed result (the rejudge tool inside Pi, else the rejudge CLI; read-only). Use when the user says /rejudge or wants a multi-model review. For one external reviewer, use ask-agent-cli instead.
Use to unblock Blocked, stalled, or pending-decision items in a development plan; not to write a plan from scratch, conduct an overall review, or implement a plan. Investigate and resolve blockers; when user input is needed, use blocking questions via tools; hand off external dependencies through CRD; record decisions and update the plan.
Review digital artifacts against the user’s task, creative direction, functional and accessibility requirements, and actual delivery medium. Inspect renders, native files, playback or interaction as appropriate; exercise relevant failure and recovery paths and report evidence-backed findings. Use for design review or a manifest gate. Design guidance belongs to design; implementation and restyling stay with the invoking workflow.
Autonomous PR review that posts high-signal, human-voiced comments under your account. Use when reviewing someone else's PR or your own manifest-driven PR, when you want a precision-tuned review you can walk away from, or when the user asks to review a PR, post a PR review, autoreview, loop review, or watch a PR.
Review any prose against its register's writing standard — a README, a spec, a design doc, a blog post, marketing copy, or a draft you paste in. Detects whether the text is documentation or human-voiced writing, applies that register's rules plus the rules holding in both, and reports graded findings with the fix. Use when checking a document's style, asking whether a draft reads as AI-written, reviewing writing before publishing, or asking for a writing review outside a manifest run
Authoring and debugging scripts for Rhinoceros 3D (Rhino 8 and later). Use when asked to write RhinoScript (VBScript / .rvb / .vbs), RhinoPython, or RhinoCommon-based scripts; automate Rhino modeling tasks; build command macros; manipulate Rhino geometry, layers, blocks, or document objects; pick objects from the viewport; control redraw and undo; or load and run scripts from the Rhino Script Editor. Covers `rhinoscriptsyntax`, `scriptcontext`, the `Rhino.*` RhinoCommon namespaces (`Rhino.Geometry`, `Rhino.DocObjects`, `Rhino.Input`, `Rhino.UI`, `Rhino.Display`, `Rhino.FileIO`), and the Rhino 8 unified Script Editor.
Run one exact Ticket through recovery and autonomous work to a ready pull request, keeping its Manifest, progress and completion record on that same Ticket, and land it only when told to. Use when orchestrate, an agent runner, or a person supplies a specific issue, tracker item, or file Ticket to work end to end. This skill does not select backlog work or enforce Auto eligibility at dispatch.
Reviews Rust code for ownership, borrowing, lifetime, error handling, trait design, unsafe usage, and common mistakes. Use when reviewing .rs files, checking borrow checker issues, error handling patterns, or trait implementations. Covers Rust 2024 edition patterns and modern idioms.
Explore an existing PostgreSQL database before answering questions about its data or writing SQL. Use this skill whenever a user asks for a query or a data-backed answer against an unfamiliar schema (counts, missing or failed records, recent changes), asks where a business concept lives, or asks how tables, joins, views, routines, triggers, RLS, or extensions work. Find the relevant objects with read-only pg_catalog queries, then request approval before inspecting data-derived statistics or rows. Not a schema-design or migration guide
Use when the user wants Facebook research or workflow guidance for lead generation, influencer discovery, brand monitoring, competitor analysis, content analytics, trend research, or audience analysis, including page or profile audits, post, reel, photo, or comment extraction, group monitoring, transcript retrieval, and Facebook ad or advertiser analysis.
Use the Scrapfly RPA API to run typed workflow graphs against managed cloud browsers, retrieve produced artifacts (HTML snapshots, downloads, HTTP response bodies, JS return values), and route those artifacts into Scrapfly's managed bucket or your own customer GCS or S3 bucket. Use when the user asks to "run an RPA workflow", "fetch artifacts from a run", "configure BYOS storage", "set up customer GCS or S3 for RPA", "test a storage destination", or any task involving the /v2/rpa/* endpoints.
Review Django security audit patterns for settings and middleware. Use for auditing SECRET_KEY, DEBUG, CSRF, and auth decorators. Use proactively when reviewing Django apps (settings.py or manage.py present). Examples: - user: "Audit my Django settings.py" → check SECRET_KEY, DEBUG, and ALLOWED_HOSTS - user: "Check Django views for auth" → verify @login_required and permission classes - user: "Review Django CSRF config" → check middleware and @csrf_exempt usage - user: "Scan for SQL injection in Django" → find raw SQL usage instead of ORM - user: "Audit Django REST framework config" → check default permissions and auth
Use whenever an agent considers or prepares to commit changes, including grouping hunks, composing or revising messages, commit-related staging, and commit creation. Also use for prospective planning before implementation, requested history updates or rebases, cherry-picks or merges that create commits, and scripts or tests that create commits. Don’t use for read-only inspection of existing history when no commit or history update is being prepared
Audit or fix real codebases for SEO: metadata, rendering, crawlability, indexability, canonicals, schema, snippets, OG/social previews, i18n, hreflang, sitemaps, robots, internal links. Also Google-grounded AEO/GEO work for AI Overviews and AI Mode, ecommerce/local details and agent browsing. Do NOT use for paid ads, rank tracking, link building or link schemes.
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.