Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use the Paragraph CLI and MCP server to manage posts, drafted content (X posts, LinkedIn posts, newsletters, X Articles), publications, subscribers, and coins on paragraph.com. Trigger when the user asks to publish, create, update, or manage newsletter content on Paragraph via CLI or MCP.
View, extract, edit, and manipulate PDF files. Supports text extraction, text editing (overlay and replacement), merging, splitting, rotating pages, and getting PDF metadata. Use when working with PDF documents for reading content, adding/editing text, reorganizing pages, combining files, or extracting information.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Guides authorized penetration testing—scoping and rules of engagement, reconnaissance, vulnerability identification, exploitation within scope, post-exploitation documentation, evidence and remediation reporting, and retest validation. Emphasizes written authorization, RoE boundaries, and safe/legal testing. Use for pentest, penetration test, ethical hacking, authorized assessment—not enterprise adversary simulation or purple-team campaigns (red-team-specialist), dedicated network/AD/infra pentest (network-pentester), deep web/API-only assessments (web-pentester), SOC alert triage (soc-analyst), incident command (incident-responder), forensic imaging (digital-forensics-analyst), binary/firmware RE (reverse-engineer), LLM/adversarial AI testing (ai-redteam), or implementing cloud guardrails (cloud-security-engineer).
Performance optimization specialist for profiling, caching, and latency optimization. Use when "performance, latency, slow query, profiling, caching, optimization, N+1, connection pool, p99, performance, profiling, caching, latency, optimization, async, database, load-testing, ml-memory" mentioned.
Complex research requiring deeper analysis, multi-step reasoning, and sophisticated source evaluation for technical, academic, or specialized domain queries needing expert-level analysis, high-stakes decisions, or multi-layered problem solving.
When the user wants to create a personal budget, track income vs. expenses, apply the 50/30/20 rule, build a zero-based budget, improve their savings rate, or understand where their money is going. Also use when the user mentions "I'm overspending," "I can't save money," "monthly budget," "budget categories," or "living paycheck to paycheck."
Batch-generate unique, spec-verified, brand-checked personalized first lines for large prospect lists (100s) using Apollo hiring signals, Clay/company news, and LinkedIn activity, gated through qualify_lead and check_my_copy, delivered as a review CSV or Gmail drafts (never sent). Use when: "personalize outreach for [N] prospects", "generate unique first lines", "find personalization angles for this list", "research these companies for outreach", "first lines for my prospect list", "batch personalization", "personalize at scale". Not for a single prospect's full cadence (prospect-research-to-cadence-skill).
Turn a user-provided photograph into a minimal two-sided 2:3 zine-style postcard. Preserve the original photo above, then create a sparse hand-drawn source-specific motif, minimal metadata, three sampled color swatches, and a matching functional postcard back
Use when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
Use when the user wants to set up, scale, validate, or harden NVIDIA physical AI infrastructure for synthetic data generation workflows across local MicroK8s or Azure AKS, including Kubernetes clusters, inference endpoint deployment, OSMO deployment, workload submission readiness, and infrastructure failure recovery. Trigger keywords: physical ai infrastructure, resilient scaling, SDG infrastructure, microk8s, azure aks, NVCF deployment, NIM Operator, OSMO deploy, workflow scaling. Don't trigger for: OSMO log summarization or workload-only operations unless infrastructure setup, scaling, validation, or recovery is requested.
Use when running video data augmentation and auto-labeling workflows on OSMO: flow selection, preflight, submit-time interpolation, monitoring, and output retrieval. Trigger keywords: video data augmentation, data enrichment, auto labeling, VDA demo, OSMO workflow, pseudo labeling.
Portfolio-level pipeline forecast + health rollup: stage-by-stage conversion vs benchmark, risk-adjusted forecast (commit/best/worst scenarios), probability calibration, and a pipeline report card. Pulls deals from HubSpot via the Epiphan AI MCP (execute_sql / hubspot_search_deals); CSV export is a fallback only. Use when: "analyze pipeline health", "pipeline health", "risk-adjusted forecast", "forecast accuracy", "which stage do deals stall in", "pipeline report card", "scenario planning", "deal slippage". For per-deal momentum scoring use deal-momentum-analyzer-skill; for kill/recover triage use dead-deal-recovery-skill.
Use when user requests diagrams, flowcharts, sequence diagrams, class diagrams, component diagrams, ER diagrams, architecture charts, or visualizations — including generating a diagram from existing source code, or rendering/extracting PlantUML embedded in a Markdown file to images (e.g. preparing docs for Confluence/Notion). Also use proactively when explaining systems with 3+ components, APIs, data flows, or class hierarchies. Generates .puml files and exports to PNG/SVG via Kroki API (no local install required).
Pre-listing platform compliance checks and automatic fixes. For images awaiting listing, generates reports on approval or rejection risks for Amazon / TikTok Shop / Temu / Shopee / Taobao, and can fix them into compliant images with one click. Use when the user asks “Will this be rejected?”, “compliance check,” “white background doesn’t meet requirements,” “main image specs,” or “it was rejected after upload.”
Understanding Claude Code's plugin registry structure, installation scopes, and common issues. Use when troubleshooting plugin installation problems, understanding why plugins show as installed incorrectly, or manually fixing registry entries.
Map the Pragmatic Institute Competitive Landscape — identify competitive and alternative offerings, assess their strengths and weaknesses, and develop a strategy for winning (knowing when to fight and when to run). Use when a PM says “competitive analysis”, “competitors”, “battlecard”, “how do we win against X”, “alternatives”, or “where do we play”. Includes the Solution Matrix (customer impact vs. depth of investment). Produces a Competitive Landscape analysis and a Solution Matrix as a Markdown or Word .docx artifact.
Build a Pragmatic go-to-market launch plan and readiness checklist. Use when the PM asks to plan a launch, GTM, go-to-market, launch readiness, launch checklist, release announcement, or “get sales and marketing ready”. Coordinates the Programs and Enablement columns of the framework around a market window. Produces a Launch Plan as a Markdown or Word .docx artifact.
Create Pragmatic Institute buyer and user personas — archetypes grounded in real market evidence, written so the team stays connected to real people. Use when the PM asks about personas, "who is the buyer", "who is the user", target audience, ICP, or wants to make a persona come alive. Distinguishes the buyer (makes/influences the purchase) from the user (uses it daily). Produces a Buyer Persona and a User Persona as a Markdown or Word .docx artifact.
Assemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market problems, requirements and use scenarios if present, and gathers anything missing inline. Produces a Product Requirements Document as a Markdown or Word .docx artifact.
Write Pragmatic Institute use scenarios — short stories that put a market problem in context from the persona's point of view (a component of requirements). Use when the PM asks for “use scenarios”, “a day in the life”, “user story context”, “problem statements”, or needs to reframe a feature request as a real problem so development understands the WHAT (not the HOW). Produces a Use Scenarios document as a Markdown or Word .docx artifact.
Use when writing or modifying Python code that calls polars `DataFrame.join` or `LazyFrame.join` and any downstream step depends on the result's row order — attaching a looked-up column back onto order-sensitive data, positional alignment with a numpy array or `pl.Series`, `hstack`, or reproducible output. Skip for joins whose output you immediately re-sort or treat as an unordered set.
Develop a competitive positioning strategy for a solopreneur business. Use when deciding how to differentiate from competitors, what market position to own, how to frame your offering against alternatives, and how to communicate that position. Covers positioning frameworks (Jobs-to-be-Done, against/for, category creation), positioning statements, and translating position into messaging. Trigger on "how do I differentiate", "positioning strategy", "how to stand out", "differentiate from competitors", "market positioning", "what makes me different", "competitive positioning", "own a position".
Run an independent, report-only overall audit of a delivered design document or multi-story feature. Verify story completion, assembled behavior, design alignment, documentation, and relevant tests, then report whether blocking findings remain.
Use when the user is planning a two-arm comparison (an A/B test, a simple RCT, a behavioral study, or a two-model/two-config evaluation) and needs to size it and preregister it before collecting data — finding the per-group sample size that hits target statistical power for the smallest effect worth detecting, auditing the design against a validity checklist, and locking it in a preregistration. Only for a single two-arm comparison with one primary outcome. Not for factorial, repeated-measures, clustered/multilevel, time-series, adaptive, or survival designs; not for analyzing data already collected; not for choosing the outcome or manipulation from domain knowledge.
Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that involves writing governance metadata to flows. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app
Pro+ subscription required. Tenant-wide Power Automate monitoring using the FlowStudio MCP cached store: failure rates, run-health trends, maker/app inventory, inactive owners, and compliance/health reports. Use only for aggregated tenant views. For one environment, one flow, run control, or root-cause debugging, use power-automate-mcp, power-automate-debug, or the server monitor-flow bundle. Requires FlowStudio for Teams or MCP Pro+.
Browse, slice, and analyze the curated American Reindustrialization directory — with diffs, geo clusters, sector... Trigger phrases: `look up american reindustrialization companies`, `find reindustrialization jobs`, `browse american manufacturing directory`, `sector heatmap of reindustrialization companies`, `use american-reindustrialization`, `run american-reindustrialization`.
Agent-ready Bambu print monitoring with exact plate previews and start/finish payloads. Trigger phrases: `what is my Bambu printer doing`, `post when this print starts and finishes`, `send this Bambu print to Discord`, `show my Bambu plate preview`, `when will the Bambu print finish`, `monitor my Bambu print`.
Production Part Approval Process (PPAP) — verify PPAP submission level, audit all 18 elements, check completeness for customer approval, prepare PSW. Use when a supplier needs to submit parts for approval, when reviewing a PPAP package, or when determining which PPAP level is required. Covers AIAG PPAP 4th edition with Ford, BMW, VW, and Stellantis OEM-specific requirements.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
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.