Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
MinerU document extraction CLI that converts PDFs, images, and web pages into Markdown, HTML, LaTeX, or DOCX via the MinerU API. Supports token-free flash extraction for quick start, precision extraction with table/formula recognition, web crawling, batch processing, and piped workflows.
Use when writing or reviewing n8n SDK code that wires IF, Switch, Merge, error outputs, or any multi-input/multi-output connection. Triggers on .add(), .to(), .input(n), .output(n), .onTrue, .onFalse, .onCase, .onError, useDataOfInput, merge, switch, IF nodes, error branches, fan-out, fan-in, or any review of the workflow's connections object.
Create infographic prompts and render workflows with Nano Banana 2.1, with adaptable low-noise presets for posts, decks, reports, and explainers. Trigger on infographic, Nano Banana, Gemini image, executive visual, blog diagram, or presentation visual. Do NOT use for logos, memes, raw dashboards, or non-infographic image edits.
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs. Use after corrections or discarded proposals. Not for ordinary deletion, deprecation, migration, or exclusions materially required for safety, accuracy, compatibility, audit, quotation, or requested comparison.
Based on the body of an NSFC proposal and the application code recommendation library, gives you 5 sets of application code 1/2 (primary/secondary) recommendations with reasons; output to NSFC-CODE-vYYYYMMDDHHmm.md (read-only, does not modify the proposal)
Отправка блока PageCraft в глобальный каталог на рассмотрение и отслеживание модерации — подать заявку, проверить статус (pending/approved/rejected), прочитать причину реджекта, отозвать заявку. Используй когда пользователь говорит «отправь в каталог», «подай блок на рассмотрение», «опубликуй в общий каталог», «какой статус заявки», «почему отклонили блок», «отозвать заявку». Вызывай через тул `Skill(pagecraft-block-catalog)`, не через `Read .../SKILL.md`.
ThinkPHP framework vulnerability security audit tool. Performs white-box static auditing of common ThinkPHP mechanisms such as authorization, CSRF, template escaping, ORM writes (Mass Assignment), and debug/config exposure, mapping them to a general vulnerability type taxonomy (AUTH/CSRF/TPL/XSS/LOGIC/CFG/SESS/SQL, etc.).
Authoring Pi TypeScript extensions - ExtensionAPI, custom tools, commands, UI hooks, resources_discover, `registerProvider()`, and how extendResources merges skill paths after base reload. Use when the user builds or debugs pi extensions, registers tools, adds /commands, hooks events, integrates TUI components, or ships extension examples. Use for "how do I extend pi", "extension API", "registerTool", "registerProvider", even if pi-mono is not mentioned.
Run a structured quality audit on a product decision or its rationale — a build/buy/sunset/re-platform/pricing call, a decision log, a retrospective, or any "we decided X because…". Produces a severity-rated issue list with concrete fixes — catches outcome-based reasoning (resulting), deliberation mismatched to reversibility, uncalibrated confidence, confirmation/anchoring/framing/sunk-cost bias, missing pre-mortems, and undocumented reasoning. Use when reviewing a major decision or its write-up, or as a validation step after a decision is made.
Every Pointhound flight search, plus a local SQLite of every deal you've ever seen, balance-aware reachability, and... Trigger phrases: `find award flight`, `redeem credit card points for flight`, `pointhound search`, `where can I fly with my points`, `check pointhound for new deals`, `use pointhound`, `run pointhound`.
Pricing model design, competitive positioning, value metric selection, price testing, and pricing page optimization. Use when the user asks about pricing strategy, pricing models, price testing, value-based pricing, or competitive pricing analysis.
Project documentation scaffolding. Covers about.md, specs.md, architecture.md, project-context.md, and user stories. Use when creating or maintaining project documentation in a .project/ folder, scaffolding specs, architecture docs, or user stories. Keywords: project setup, documentation, specs, architecture, stories.
Unified project scaffolder that works across all platforms. Scaffold .agent folders, backend (NestJS), frontend (NextJS), mobile (Expo), and browser extensions (Plasmo) with interactive prompts. Supports both monorepo and separate repository structures, and can add components to existing projects.
Execute a comprehensive React project health audit. Analyzes the tech stack, architecture, state management, testing, code quality, performance, CI/CD, and documentation. Produces a shareable Markdown report with section scores and a weighted overall score. Use when the user asks to audit a React project, run a health check, evaluate frontend quality, or assess technical debt. Triggers on: 'react audit', 'health audit', 'react health', 'frontend audit', 'next.js audit', 'vite audit', 'project quality check'.
Structure, tone, and content conventions for writing effective project README files, covering hooks, quick starts, feature presentation, badges, and common documentation sections. Use when writing a new README, rewriting an existing one, or reviewing README quality for a repository, library, or CLI tool.
Executes automated refactoring for specific files, directories, or semantic queries. This skill should be used when the user asks to refactor specific files or directories, simplify recently changed code, clean up dead code in a limited scope, or invokes "/refactor".
Use this skill to write package release notes, changelog entries, and hosted release descriptions from supplied drafts or verified changes, or to review release copy for completeness, consistency, and wording. The work can cover a commit, commit range, pull request, branch, tag, diff, or every change since the latest release. Don’t use it for ordinary commit summaries unless they’re intended for use in release notes or a changelog
Publish the next stable release by the project's own stable process — check that the main branch is green, choose the version and write its notes (through write-release-notes), publish whatever platforms still go out by hand, then push the version tag once the user has the notes, watch the build and check what it published and which release is marked latest. Use when the user asks to release, cut, ship or publish a stable version, push a version tag, or invokes /release-stable. Stops at a red main branch or a missing instruction instead of guessing; never moves, deletes or force-pushes a version tag.
Relight a still image — change the lighting setup, color temperature, direction, or mood — on RunComfy via the `runcomfy` CLI. Routes to Qwen Edit 2509's dedicated `relight` LoRA endpoint for purpose-built relighting, with fallback to identity-preserving edit endpoints (Nano Banana 2 Edit, GPT Image 2 Edit, FLUX Kontext Pro) when prose lighting language is enough. Use for product relighting (studio softbox → window light), portrait mood shift (overcast → golden hour), or color-grade change. Triggers on "relight", "relighting", "change the lighting", "make it golden hour", "studio lighting", "rim light", "blue hour", "soft window light", "change light direction", "color temperature", or any explicit ask to alter how a still is lit.
Safely analyze, disassemble, decompile, or debug unknown binaries, executables, DLLs, malware, firmware, and packed or obfuscated code. Use for reverse engineering, suspicious-file triage, unpacking, Ghidra/IDA/radare2/x64dbg/GDB help, IOC extraction, YARA, or questions about what a binary does.
Use when writing a literature review article (narrative, scoping PRISMA-ScR or systematic). Scaffolds a 7-part skeleton with a scope and non-overlap statement, summary-table stubs and reporting-guideline wiring, without inventing citations. Original research is /write-paper.
Read-only review of Plans, implementation, continuation rounds, or other scoped artifacts against intended behavior, docs, acceptance criteria, tests, and risk. Use for balanced, adversarial, multi-aspect, compliance, architecture, test, library, performance, or security review.
Facilitates structured team reflection through retrospectives, post-mortems, after-action reviews, and weekly/quarterly reviews, producing root cause analysis and SMART action items with psychological safety. Use when conducting sprint retrospectives, project post-mortems, weekly reviews, quarterly reflections, after-action reviews (AARs), or when user mentions "retro", "retrospective", "what went well", "lessons learned", "reflection", or "how can we improve".
Make a SaaS demo or explainer video with Pexo. Describe your software (or paste your app URL or a screenshot) and Pexo writes the script, generates the visuals, picks the models, adds narration and captions, and returns a finished, publish-ready video — for your landing page, onboarding, or sales. Use for SaaS and software videos: "saas video", "saas demo video", "software demo", "app explainer video". NOT for live screen recording — Pexo generates the visuals.
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.
Best-practices reference for the ScraperAPI Node.js / JavaScript SDK (scraperapi-sdk npm package). Consult whenever the user is writing, debugging, or reviewing JavaScript or TypeScript code that calls ScraperAPI. Use when user asks: "scrape a website with Node.js and ScraperAPI", "ScraperAPI JavaScript example", "how do I use scraperapi-sdk in Node", "ScraperAPI TypeScript", "ScraperAPI async await Node.js", "ScraperAPI POST request JavaScript", "Node.js ScraperAPI render", "ScraperAPI account info Node". Covers both CommonJS and ESM import styles, Promises and async/await, all request parameters, POST/PUT requests, account info, error handling, and credit costs. Note: Transmits user-supplied queries, URLs, and content to ScraperAPI.
SERP landscape analysis for SEO strategy decisions. Use this skill when the user wants to understand what a search results page actually looks like for their target keywords — including AI Overview presence and attribution, SERP feature composition, how Google is interpreting query intent, which competitors dominate specific keyword sets, and where organic rankings actually translate to visible traffic. Trigger on requests like "analyze the SERP for [keyword]," "why isn't my content getting traffic even though it ranks," "what does Google show for [keyword]," "which keywords are worth targeting," "is [keyword] dominated by AI Overviews," "who owns the SERP for [topic]," "SERP analysis," or "keyword landscape." Note: Transmits user-supplied queries, URLs, and content to ScraperAPI.
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.
