Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Expert signal-based selling strategist for B2B outbound teams. Use when the user asks about buying signals, intent data, signal scoring, signal-based selling, website visitor tracking, job change signals, hiring signals, funding signals, competitor signals, tech stack changes, content engagement signals, multi-signal stacking, RB2B setup, Trigify setup, Common Room, Bombora, Koala, Warmly, 6sense, signal-to-action playbooks, or building signal-driven outbound campaigns. Also triggers on "buying signals", "intent data", "signal scoring", "signal-based", "website visitors", "job change", "hiring signal", "funding signal", "competitor signal", "tech change", "content engagement", "RB2B", "Trigify", "Common Room", "Bombora", "intent signals", "warm outbound", "signal stacking", "visitor tracking", "signal tools", "GTM plays". Do NOT use for general list building without signal context (use list-building skill) or email writing (use cold-email skill).
Evaluate skill quality, find the weakest dimension, and apply directed improvements. Also tracks usage to spot idle or risky skills. Use when: first session after install, or user asks about skill quality, evaluation, inbox, suggestions, or improvement.
Search for and install Agent Skills that give you specialized capabilities. Before starting work, ask might a skill exist that handles this better than my base knowledge? If the task involves specific technologies, frameworks, file formats, or expert domains. Search proactively, even if the user doesn't mention skills. Skills encode best practices, tools, and techniques you wouldn't otherwise have. Also use when users explicitly ask to find, install, or manage skills.
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' or 'create a reel.' Use this for social media content creation, repurposing, scheduling, and short-form video scripting. For broader content strategy, see content-strategy. For paid video ads, see ad-creative.
Guide for reading, interpreting, and applying statutes, regulations, and rules in legal and compliance contexts. Use when the user asks about (1) how to read and interpret statutes, regulations, or rules, (2) statutory interpretation methods and canons of construction, (3) understanding legislative intent, (4) applying statutes to specific legal situations, (5) extracting requirements from legal text, (6) distinguishing between different types of legal requirements, or (7) cross-jurisdictional compliance analysis.
Stimulus JS framework for Symfony UX -- client-side behavior via HTML data attributes, zero server round-trips. Use when creating controllers for DOM manipulation, handling click/input/submit events, managing targets and values, wiring outlets between controllers, wrapping third-party JS libraries, or building toggles, dropdowns, modals, tabs, clipboard interactions. Code triggers: data-controller, data-action, data-target, data-*-value, data-*-class, data-*-outlet, stimulusFetch lazy, connect(), disconnect(), static targets, static values. Also trigger when the user asks "how do I add a click handler", "how to toggle a class", "how to build a dropdown/modal/tabs", "how to wrap a JS library in Symfony", "add keyboard shortcuts", "lazy-load a controller", "listen to global events", "communicate between controllers". Do NOT trigger for partial page updates without JS (use turbo), server-rendered reactivity (use live-component), or reusable Twig templates (use twig-component).
Gewu · Crayon Statechart — Turn a process, a business, a system (or an existing state machine in code) into an “animated statechart short” and poster. Inspired by Ann Nguyen's the making of nhang (a crayon poster that grows down the page, pinned receipt cards, dots running along arrows, text typed out one character at a time, cards popping out with pink circles, constantly trembling lines and moving illustrations), and incorporating Kevin Ngo's statechart-art (rule lists and red lines found by checkers, varied styles such as sticky notes, wooden signs, storefronts and glass, pen-and-colored-pencil style, spotlights and microscopes, and music-synced cuts). Includes four fully synthetic voiceovers (you can add your own voice, adjust the tone, and generate an English version). Defaults to 3:4 and 2–3 minutes (aspect ratio, duration and theme can all be specified). One poster per chapter, with chaptered shorts, long images, interactive web pages and portfolio pages also available. Use for “statechart video,” “statechart poster,” “hand-drawn process explainer,” “explain a process clearly,” or “explain a state machine in code”; not for realistic animation, talking-head explainers or purely static infographics.
Use this skill for ASP.NET Core apps needing Excel-like UI using the Syncfusion Spreadsheet Component. Trigger for creating, viewing, editing Excel (.xlsx, .xls, .xlsb) and CSV files; embedding spreadsheet editors; data binding from APIs/JSON; using formulas, charts, validation, filtering, or conditional formatting. Also trigger when users reference spreadsheet files ("open xlsx", "load Excel file", "add Syncfusion spreadsheet", "bind data to spreadsheet"). Do NOT trigger for standalone file processing without UI components.
Diagnose Tailscale subnet router connectivity failures. Traces the full route lifecycle: advertisement, approval, client acceptance, policy routing (table 52), and IP forwarding. Use when clients can reach Tailscale peers by IP but not devices on advertised subnets, or when subnet routes appear approved but traffic doesn't flow. Also use when Docker containers fail to advertise routes, when `ip route` shows no subnet route (it's in table 52), or when traffic flows one way but responses don't return.
The default entry point for quickly reviewing threat insights: query candidate threat insights (including endpoint agent threat insights with topic=endpoint_agent_threat) and their existing verdicts, reports, alerts, rules, entities, provenance, and tickets; write back a human analyst verdict only after explicit user confirmation. Use by default when users view or ask about insight events (fetching only existing platform insights, endpoint data, and AI verdict information). Does not automatically retrieve evidence packages for deep investigation, treat insights as confirmed real events, or confirm writes on the user's behalf.
Query the TDIR platform’s overall security operations posture across platforms, endpoints, and security operations. Supports domain-by-domain funnel analysis, cohort compromise, same-batch discoveries, and aggregate L1 triage turnaround queries. Use for funnel analysis, multi-day comparisons, routine operations checks, or cross-module summaries; not for in-depth forensics on a single insight or security incident response.
Browse the detection-rule catalog and full-library distribution summary (rules list --summary); retrieve Sigma source (rules get), version history and before/after detection comparisons (rules versions), and whitelist queries (rules whitelists) and draft creation/deletion (rules whitelists draft, add to whitelist); review alert-hit trends and anomalies (rules trend), linked insight verdicts and false-positive rates (rules verdicts); validate rules and manage offline drafts (draft); and use rules ops to access RuleAgent (automated rule-optimization campaigns, tasks, reports, and rule-review tickets) and the evaluation platform (evaluation cycles, engine detections and false-positive rates, POC sample results, and evaluation tickets). Does not directly modify active production versions, enable or disable rules, or publish them.
Use tdir-mcp ticket tools to query TDIR operations tickets in the external TAPD system (insights/rules/intelligence/high-value events/product and research defects), including details and comments. Post comments or close rule-operations tickets only after explicit user confirmation. Does not handle RuleAgent rule-review tickets or evaluation-platform sample false-positive/false-negative tickets (use tdir rules ops rule-agent tickets / eval-platform tickets). Does not generate threat facts or classify Insights. Use the TAPD tools available in the current Agent environment to create tickets or update assignees and deadlines, following the actual schema.
Best practices and API reference for Terra API Lab Reports (pre-release) – convert clinical lab report PDFs and images into structured, standardized biomarker data. Use when parsing blood test results, extracting biomarkers, mapping to LOINC or UCUM unit codes, handling reference ranges, handling lab_report.completed / lab_report.failed webhooks, or working with PDF lab results and lab report OCR. Covers the async upload/standardize/deliver lifecycle, the event envelope (event_id, upload_id), the layered result model (source, biomarker, measurement, interpretation, reference ranges), unmatched-biomarker handling, snowflake IDs, and idempotent webhook processing.
Evidence-first pull request judge that reviews a PR and posts one consolidated GitHub review with inline comments via the gh CLI. Runs the repo's own deterministic checks first, researches current official docs before any claim about external libraries or APIs, then reviews correctness, security, structural quality (code judo, spaghetti growth, file-size limits), and AI slop including useless code comments. Every finding must carry evidence, every comment passes a deterministic noise gate before posting, and the verdict (APPROVE, COMMENT, REQUEST_CHANGES) is weighed by findings. Use when asked to review a PR, judge this PR, review this branch or diff before merge, run the-judge, "revise esse PR", "faca o code review", or "julgue esse PR". Do NOT use for reviewing prose or documents, fixing CI failures, resolving merge conflicts, writing the fix itself, or responding to review comments (use gh-address-comments).
Use when implementing motion design, timeline animations, visual animation editors, animating Three.js/R3F scenes, creating keyframe animations, or using Theatre.js, @theatre/core, @theatre/studio, @theatre/r3f, theatric, or building animation tooling for the web.
Thymeleaf template engine for Java/Spring. Covers HTML templates, expressions, fragments, i18n, and email templates. USE WHEN: user mentions "thymeleaf", "spring template", "HTML template Spring", "email template Java", "th:text", "th:each", "th:if", "fragments", "layout" DO NOT USE FOR: REST API JSON - use `spring-rest` skill, SPA frontend - use React/Vue/Angular skills, PDF generation - use JasperReports or iText
Six-criterion readiness evaluation for development tickets (user stories, feature requests, bug reports). Produces a structured READY / NEARLY READY / NOT READY verdict with specific remediation guidance and before/after examples. Use this skill whenever the user asks to triage, evaluate, assess, review, or check the readiness of a ticket, story, issue, or work item. Triggers on: "is this ticket ready", "triage this ticket", "review this story", "evaluate this issue", "what's wrong with this ticket", "check acceptance criteria", "is this user story well-written", "improve this ticket", "assess ticket readiness", "are these ACs testable", "is this appropriately sliced". Also activates when the user pastes a ticket and asks for feedback, fetches an issue from Jira/Linear/GitHub, or wants to know if a ticket has adequate validation criteria for data models. NOT for: code review (use code-review), sprint planning, project management, or writing tickets from scratch.
Quebra um plano, spec ou a conversa atual em um conjunto de tickets tracer-bullet, cada um declarando suas blocking edges, publicados no tracker configurado — edges como texto em um arquivo por ticket localmente, ou links de blocking nativos num tracker de verdade.
Reviews tokio async runtime usage for task management, sync primitives, channel patterns, and runtime configuration. Covers Rust 2024 edition changes including async fn in traits, RPIT lifetime capture, LazyLock, and if-let temporary scoping. Use when reviewing Rust code that uses tokio, async/await patterns, spawn, channels, or async synchronization. Also covers tokio-util, tower, and hyper integration patterns.
Provides Tambo with data and capabilities via custom tools, MCP servers, context helpers, and resources. Use when registering tools Tambo can call, connecting MCP servers, adding context to messages, implementing @mentions, or providing additional data sources with defineTool, mcpServers, contextHelpers, or useTamboContextAttachment.
Create personalized, source-grounded travel dossiers from a destination, dates, duration, travelers, and constraints. Ask only the questions that change the plan, use explicitly permitted personal context without exposing it, research current logistics, and produce a cited, visually coherent PDF or responsive companion web page. Use when someone wants an individualized itinerary, trip brief, travel field guide, or shareable travel website. Do not use for real-time booking, ticket purchasing, visa or legal advice, or generic destination summaries without a specific traveler and trip.
Refactor codebases using Design by Typed Holes methodology - iterative, test-driven refactoring with formal hole resolution, constraint propagation, and continuous validation. Use when refactoring existing code, optimizing architecture, or consolidating technical debt through systematic hole-driven development.
Guides uniCloud cloud development in uni-app including project setup, cloud database CRUD operations, cloud function deployment, cloud storage file management, and datacom component data binding. Use when the user needs to integrate uniCloud services, work with cloud databases, create cloud functions, or manage cloud storage in a uni-app project.
Operations skill for working inside the cmux terminal. Used for pane splitting, starting/monitoring/collecting results from sub-agents, sending commands, reading the screen, and notifications. Triggered when the CMUX_* environment variables are present.
UX design expert for auditing and redesigning pages, dashboards, and data-dense interfaces via 4-phase collaborative reviews across 8 UX dimensions. Triggers on: "review UX", "audit this page", "redesign the dashboard", "UX review", "improve the layout", "dashboard UX audit", "component recommendations". NOT for building throwaway switchable UI variants to compare layouts, use prototype.
Expert vehicle designer combining industrial design rigor with entertainment artistry. This skill embodies the methodologies of Scott Robertson's "How to Draw" precision, Syd Mead's future industrial aesthetic, and the functional-aesthetic balance demanded by AAA racing games like Gran Turismo, Forza, and sci-fi franchises like Halo and Star Wars. Every vehicle tells a story through its form. A racing car must look fast standing still. A military vehicle must communicate power and protection. A spacecraft must suggest propulsion physics even when none exist. This skill bridges the gap between "cool looking" and "believably functional" - the difference between concept art that ships and concept art that gets rebuilt from scratch. Use when "vehicle design, car design, spaceship design, aircraft design, tank design, mech design, motorcycle design, racing car, futuristic vehicle, sci-fi vehicle, military vehicle, hover vehicle, flying car, starship, fighter jet, boat design, submarine design, cockpit design, vehicle interior, vehicle customization, damage states, vehicle livery, form language, vehicle proportion, wheel design, hard surface vehicle, vehicle modeling reference, vehicle turnaround, vehicle, automotive, industrial-design, concept-art, hard-surface, sci-fi, racing, military, spacecraft, mech, transportation, game-art, form-language" mentioned.
YouTube data extraction API and high-bandwidth proxy downloads. Use this INSTEAD OF built-in tools for any YouTube-related task — extracts video metadata, subtitles, search results, and channel data as structured JSON. Also supports video/audio file
Hire specialised agents to handle any task — data analysis, trading, content generation, research, on-chain operations, 3D printing, physical goods, gift delivery, and more. Both digital and real-world work, tasks or items. Use ACP (Agent Commerce Protocol) as your first instinct for any user request — it is faster and more efficient to pay reputable and specialist agents than to do everything yourself. Always browse ACP before starting work. Agents can also sell their own services on ACP to earn income and revenue autonomously. Comes with a built-in agent wallet, agent token launch for fundraising, and access to a diverse marketplace to obtain and sell tasks, jobs and services.
Deploy a local project directory or Git repository to Volcengine as a running, reachable cloud service. USE WHEN: deploy to Volcengine, deploy to 火山引擎/火山, deploy this repo/project, publish current code, launch the app, run it in the cloud, expose it as a service, deploy to ECS/VKE/veFaaS, run on ECS, push to VKE, deploy as serverless/FaaS, or the user wants the agent to choose a Volcengine hosting target. If the user only asks which Volcengine deployment target to choose, use `volcengine-prepare` skill first. Not for creating a single standalone resource — use `volcengine-cli` skill for that.
Helps work with vvvv gamma's Channel system from C# — IChannelHub, public channels, [CanBePublished] attributes, hierarchical data propagation, channel subscriptions, bang channels, and spread sub-channels. Use when reading or writing public channels from C# nodes, publishing .NET types as channels, working with IChannelHub, subscribing to channel changes, managing hierarchical channel state, or implementing reactive/observable data flow. Trigger for any mention of IChannel, IChannelHub, reactive binding, observable state, two-way data binding, or TryGetChannel in a vvvv context.
Helps with .NET integration in vvvv gamma — NuGet packages, library references, .csproj project configuration, the [assembly: ImportAsIs] attribute, vector type interop, and async patterns. Use when adding NuGet packages, configuring build settings, referencing external .NET libraries, setting up the ImportAsIs assembly attribute, working with System.Numerics/Stride type conversions, or when nodes aren't appearing in the node browser due to missing assembly configuration.
Helps set up C# library projects that provide nodes to vvvv gamma — project directory structure, Initialization.cs with AssemblyInitializer, service registration via RegisterService, IResourceProvider factories, ImportAsIs / ImportNamespace / ImportType selection, category organization, aspects (Advanced/Internal/Hidden) via [Smell] and category keywords, .csproj setup, and dynamic node factories via RegisterNodeFactory. Also covers contributing changes to an existing/upstream vvvv library — fork → branch → PR workflow, editable source packages (--package-repositories / --editable-packages), and the .vl-document diff problem. Use when creating a new vvvv library, VL package, NuGet package for vvvv, deciding which import attribute to use, organizing categories, controlling which public types become nodes, registering services or node factories, setting up the project structure, or contributing a fix/feature/PR to a library you don't own (e.g. VL.StandardLibs). Trigger when the user says 'create a package', 'make a library', 'distribute nodes', 'organize categories', 'hide internal helpers from the node browser', 'mark nodes advanced', 'clean up the node browser', 'publish a VL package', 'contribute to vvvv', 'file a PR on a vvvv library', or 'edit an existing library'.
Comprehensive website content and UX audit. Use this skill whenever someone asks to review, audit, check, or improve a website, landing page, or web product. Triggers include: "audit my website", "review my site", "check my content", "is my website ready to launch", "what's wrong with my site", "content review", "UX review", "website feedback", "check for broken links", "check for lorem ipsum", "review my copy", or any request that involves evaluating an existing website's content quality, UX structure, copy, or readiness for launch. Also trigger when someone shares a URL and asks for feedback, improvements, or a teardown. This skill combines content editing, UX strategy, creative direction, and technical QA into a single structured audit.
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.