Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Upload local images in Markdown files to an image hosting service via PicList HTTP Server and replace them with cloud links. Use this skill when the user needs to upload images in Markdown, process Markdown that contains local image references, batch-process multiple Markdown files or directories, or replace local paths with cloud links for cross-device access.
Pino (fast JSON structured logger for Node.js, the standard logger for Fastify) reference. logger, child logger, log levels (info / warn / error / debug / trace), transport, pretty print (pino-pretty), redaction (masking sensitive data), serializers, async / sync logging, file output, structured logging.
Claude IS the pixel artist — designs and places every pixel directly via Python/Pillow (scripts/pixelstudio.py). No Aseprite, no MCP server. Creates sprites, characters, items, tiles/tilesets, animations (idle/walk/run/attack), applies limited palettes, hue-shifted ramps, dithering, shading, selective outlines, and exports PNG / animated GIF / spritesheet+JSON for game engines. Can also STUDY a pixel-art file the user provides and grow its knowledge base. PREFER THIS SKILL over pixel-art-creator / pixel-art-animator / pixel-art-professional / pixel-art-exporter (those require the aseprite MCP) unless the user explicitly asks for Aseprite. Trigger on pixel art, sprite, sprite sheet, 8-bit, 16-bit, retro game art, tileset, pixel animation, GIF sprite, วาด pixel art, สร้าง sprite, ทำ pixel art, พิกเซล, ตัวละครเกม, ไอคอนเกม, เรียนรู้จากไฟล์ pixel art.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Install and use Playwright via a standalone .mjs script (not through npx playwright test / *.spec.ts) to verify code quickly, one-off: screenshot localhost/file://, read console/pageerror, measure getBoundingClientRect when an element is not visible or not clickable, bypass auth via addCookies+addInitScript; for MULTI-STEP work, use the persistent-session mode connectOverCDP (tabs/cookies persist across turns, no writing the whole scenario blind). Use when the user says 'verify bằng playwright', 'chụp ảnh trang', 'test nhanh UI bằng script', 'verify nhiều bước', 'giữ session giữa các lần chạy', 'claude-in-chrome bị chặn localhost', 'không click được / không thấy phần tử', or invokes /playwright-verify. DIFFERENT from uat-nonit-testcase (UAT test case set for non-IT) and claude-in-chrome (extension, blocked by localhost/file://) — this is the GENERAL guide applicable to every task.
Generate ReactFlow diagrams as .rfd.json files using a predefined library of custom node types, edge presets, and layout templates. Use when the user wants to visualize architectures, workflows, data flows, or concepts, or wants to convert analysis of a codebase into a diagram viewable in a ReactFlow-based SPA.
Turn a specific LinkedIn post (its URL) into a ready-to-launch outreach campaign. Use this whenever a request references a LinkedIn post or pastes a post URL: only this skill scrapes the post's likers and commenters into an audience before writing the sequence, so prefer it over any generic campaign or sequence writer when a concrete post is involved. Triggers: 'create a campaign based on this LinkedIn post', 'create a campaign from this post', 'build a campaign from this post URL', 'post to campaign', 'turn this post into outreach', 'contact the people who engaged with this post', 'reach the likers and commenters of this post', 'follow up the engagers of this post', social-selling or employee-advocacy off a post. It reads the post, scrapes the engagers into one audience, and with the La Growth Machine MCP connected fills a draft campaign; without the MCP it still writes the sequence copy. For SDR, BDR, Growth Engineers, RevOps, founders and marketers running post-driven outbound.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./docs/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Price a product or service for a solopreneur business. Use when deciding how much to charge, choosing between pricing models, structuring tiers, handling price objections, and adjusting prices over time. Covers value-based pricing, competitor benchmarking, psychological pricing tactics, pricing tiers design, and price testing. Trigger on "how should I price this", "pricing strategy", "what should I charge", "pricing tiers", "am I undercharging", "pricing model", "how to price my product", "raise my prices".
Use when starting a session on an existing WordPress site, or when the user says 'prime yourself', 'what builder does this site use', or 'give me a site briefing'. Loads the active site, detects the builder, loads inline schemas, reads the stored per-site brief, and sets the do-not-write-raw-HTML rule.
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
Pure Python DICOM for medical imaging (CT, MRI, X-ray, ultrasound). Read/write DICOM, pixels as NumPy, edit tags, windowing (VOI LUT), PHI anonymization, build DICOM, series→3D volumes. Use histolab for WSI pathology; nibabel for NIfTI.
A strategic advisor for QA, quality, testing, and automation processes. Acts as a senior QA lead. First interviews the user and scans the project to build rich context, then identifies the highest-impact gaps and delivers a prioritized step-by-step roadmap, routing execution to specialized skills. Trigger this skill when the user wants to set up QA from scratch, improve an existing process, set up test automation, decide where to start with testing, or run a QA maturity review — e.g. "set up QA for this project", "improve our QA/testing/automation process", "where should we start with testing", "we have no tests, help", "review our quality process". Also trigger this skill when the user describes problems like "low/poor quality", "missing/a lot of bugs", "no testing".
Retrieve the requirements linked to a pull request and extract its documented expected behavior and unresolved decisions. Reuse existing requirement-review comments when available. Supplies intent to qa-review-pr; does not review code or infer requirements from implementation. Skip extraction when no linked issue exists.
Low-latency synchronization with WebTransport, pub/sub messaging, CRDTs, and AI stream orchestration. Covers bidirectional streaming, transactional outbox patterns, sequence tracking, and collaborative editing. Use when building real-time collaborative UIs, implementing pub/sub messaging, handling WebTransport or WebSocket connections, orchestrating live AI token streams, or resolving conflicts with CRDTs.
Implement adaptive learning with ReasoningBank for pattern recognition, strategy optimization, and continuous improvement. Use when building self-learning agents, optimizing workflows, or implementing meta-cognitive systems.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
When the user wants to optimize retail store replenishment, calculate reorder points for stores, or manage continuous replenishment. Also use when the user mentions "store replenishment," "auto-replenishment," "min-max inventory," "store orders," "DC to store," "continuous replenishment," or "vendor-managed inventory (VMI)." For initial allocation, see retail-allocation. For DC operations, see warehouse-design.
Reverse-engineers a UI animation from a screen recording. Extracts frames with ffmpeg, tracks motion per frame with OpenCV, fits easing and spring curves, annotates choreography (leads, lags, over-stretch), and emits CSS, Motion/Framer Motion, SwiftUI, React Native, or UIKit code plus a handoff motion spec. Use when the user shares or uploads a screen recording or video of a UI animation, or asks to "reverse engineer this animation", "recreate this animation", "match this easing", "extract the animation curve", "figure out the spring from this video", "copy this transition from a video", "how does this animation work", or "reproduce this motion". For designing new motion from scratch or reviewing motion code, use ui-animation instead.
Review a change along one specific quality dimension — bugs, design, simplicity, maintainability, testability, test quality, type safety, contracts, operational readiness, docs, prose value, change intent, defect-class completeness after a fix, or context-file adherence. Loads exactly one dimension reference and reports findings graded by consequence; applies a caller-supplied acceptance policy when a gate verdict is requested. Use when verifying a change before merge, auditing a diff for a named concern, or running a manifest acceptance gate.
Give an existing video a narration makeover - rewrite the script in a new tone (tighter, warmer, more formal, more energetic), pick a fitting voice, regenerate the voiceover, and re-align the visuals to the new timing. Use when the user says "make the narration less robotic", "rewrite the voiceover to sound friendlier", "this video sounds too stiff, revoice it", "change the tone of this video", or "redo the narration in a different style".
Reviews and tunes SAST tool configurations against OWASP ASVS 4.0.3 and CWE Top 25. Auto-invoked when reviewing Semgrep rules, CodeQL queries, SAST CI integration, or false positive triage workflows. Produces a SAST maturity assessment covering rule authoring, severity tuning, custom rule development, and CI integration patterns.
Splits a full sales demo into a chaptered, async-reviewable format built around buyer decision points (Integrations, Security, Pricing tiers shown, the feature that solves their specific problem) rather than a generic feature-by-feature or course-style structure. Adds an opening "what's in this demo" card so a prospect can decide where to jump before watching, and makes every section label and recap stand on its own with zero live-rep context, since no one is present to narrate or answer questions. Use when the user says "make this demo watchable without me in the room", "split this demo so the prospect can jump to what matters", "turn this into an async-shareable demo", "let the champion forward this and have stakeholders skip to their part", or "make my demo self-navigable".
Translate market-moving news into investable alpha hypotheses by mapping observed demand changes to revenue lines, supply chains, small-cap financial elasticity, market misclassification, validation metrics, downside risks, and position-sizing conditions. Use when the user shares news, product launches, technology breakthroughs, procurement signals, supply-chain changes, earnings-call clues, or asks for Serenity-style alpha analysis, small-cap beneficiaries, or "news to financial statement" translation.
Use to stand up a headless Omni-Channel Supervisor Configuration by deploying the classic OmniSupervisorConfig (parent plus supervisor-user and queue companions) in one atomic Metadata API deploy, idempotent via the deploy state. Requires active supervisor users, Omni base settings, and the monitored queues. Triggers: set up Omni Supervisor, configure the classic Supervisor Command Center. Do not use to create supervisor users, assign the ContactCenterSupervisor permission set, or deploy queues, service channels, or presence statuses.
Orchestrate Salesforce deployments with dependency resolution, package.xml generation, targeted test execution, error diagnosis, and rollback strategies. Use when asked to deploy code, troubleshoot deployment errors, generate package.xml, set up CI/CD pipelines, or validate deployments. Activate on mentions of "deploy", "deployment", "package.xml", "CI/CD", "GitHub Actions", "validation error", or "deployment failure".
Help users discover and select the right Salesforce skill for their task. Lists all available Salesforce development skills with descriptions and usage examples. Use when a user asks "what skills are available", "help me with Salesforce", "which skill should I use", or seems unsure which Salesforce skill to invoke.
Definition-of-done checklist for shipping a new write, signal, table, edge, or query to the ax graph. Use when adding a SurrealDB table/edge/field, an ingest derive-stage, a new analytic query, or any new ax capability - before opening the PR. Ensures every write gets an on-demand read AND a proactive (agent-facing) read AND docs/distribution, not just the write. Triggers on "ship", "new signal", "new table/edge", "new lens/query", "wire this up", "is this done", or finishing an ax feature branch.
Get a video under a hard time limit by deciding what to cut and what to compress, while protecting a must-keep list and the core message. Use when the user says "get this under 2 minutes", "shorten this to 60 seconds", "it needs to fit in 90 seconds for the campaign", "cut this down but keep the demo", or gives a video plus a time budget it currently blows through.
Use this skill to author and iterate on Signadot plan specs: discover schema/actions, compose params and steps, create/run plans, inspect outputs and logs, and tag validated plans. It is not for conceptual explanations or running existing tagged plans to validate code changes.
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.
Extract a complete design system from any website, local directory, or public GitHub repo using the skillui CLI. Generates SKILL.md, DESIGN.md, and token files (colors.json, spacing.json, typography.json) that Claude reads automatically. Use when the user wants to extract a design system or design tokens from an existing site or codebase before building a UI, wants a reference design system to match, or says things like 'extract the design system from', 'get the tokens from', 'pull styles from this site', 'clone the look of', or provides a URL/repo and wants to match its visual language.
Turn a behavioral or compliance training topic - giving feedback, de-escalation, harassment policy, security awareness - into a story-driven animated scenario video: illustrated characters, setup, tension, response, a narrated takeaway after each beat, and a closing what-to-do checklist. Use when the user says "make a soft skills training video", "scenario-based training on X", "compliance training video", "turn this policy into a training video", or "behavioral training for managers".
Convert a PowerPoint standard operating procedure deck into a narrated training video plus a written job aid (a condensed, scannable quick-reference companion authored as the project's article). Preserves compliance-critical exact wording instead of paraphrasing it. Use when the user says "turn this SOP deck into a training video", "convert this PowerPoint procedure into a video and job aid", "make a training video from this SOP presentation", or hands over a procedure deck and asks for both a video and a reference sheet.
Produce two artifacts from one procedure in a single pass: a narrated SOP walkthrough video and a step-by-step written SOP with an annotated screenshot per step, with identical step numbering across both. Use when the user says "make an SOP video and doc", "I need this procedure as a video and a document", "create the SOP for this process", "standard operating procedure with screenshots", or "document this workflow for the rollout".
Diagnose failed Spark jobs, unhealthy Livy sessions, and performance bottlenecks in Microsoft Fabric via read-only CLI triage. Use ONLY for FAILED/unhealthy runs; running a notebook and reporting its success status is `spark-authoring-cli`. Use when the user wants to: (1) diagnose why a Spark job, notebook run, or Lakehouse job failed, (2) triage stuck or dead Livy sessions, (3) identify OOM, shuffle spill, or data skew, (4) retrieve driver/executor logs or Spark Advisor findings, (5) copy event logs and start a local Spark History Server, (6) diagnose Spark activities in a failed pipeline run. Triggers: "diagnose my failed notebook", "why did my spark job fail", "triage spark failure", "diagnose pipeline run failure", "why did my pipeline fail", "livy session stuck in starting", "spark executor OOM", "check spark advisor findings", "shuffle spill diagnosis", "why did my lakehouse job fail", "diagnose lakehouse table load", "data skew diagnosis", "open spark history server locally", "spark job triage".
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.