Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Review privacy, data retention, deletion, export, consent, telemetry, analytics, backups, account closure, children/minors, store disclosures, and data lifecycle for SaaS, apps, games, desktop utilities, developer tools, marketplaces, and support systems. Use when product decisions touch user data, tracking, storage, privacy claims, compliance risk, or trust.
Product changelog and release notes that users actually read. Covers categorization, user-facing language, visuals, and distribution. Use for: release notes, changelogs, product updates, feature announcements, versioning. Triggers: changelog, release notes, product update, version notes, what's new, feature announcement, product changelog, update log, release announcement, version release, product release, ship notes
Plan and review products end to end across strategy, market research, product design, UI, monetization, distribution, operations, promotion, customer support, and lifecycle management. Use when designing a new app, SaaS, game, utility, web product, desktop product, product roadmap, launch plan, or full product operating system.
Develop and critique product positioning for SaaS, apps, games, developer tools, utilities, marketplaces, and launches across audience, category, wedge, alternatives, differentiation, proof, messaging hierarchy, and landing-page narrative. Use when a product sounds generic, targets too many people, competes poorly, or needs a sharper market story.
When the user wants to break down revenue and costs by specific products, services, or segments. Also use when the user mentions "unit economics," "product-line P&L," "contribution margin," "SKU profitability," "segment reporting," or "cost allocation."
Translate a tracking plan into an SDK-specific instrumentation guide. Shows how to make identify, group, and track calls using the target analytics SDK with real template code, architecture guidance, and constraint documentation. Outputs .telemetry/instrument.md. Covers 25 analytics destinations across product analytics, CDPs, product adoption, web analytics, error monitoring, feature flags, and session tools. Use when the user has a tracking plan and needs to know how to implement it with a specific SDK like Segment, Amplitude, Mixpanel, PostHog, Accoil, Google Analytics, Sentry, LaunchDarkly, or via generic HTTP POST. Also use when user asks 'create instrumentation guide,' 'how to implement tracking,' 'SDK guide,' or 'generate implementation guide.'
Wave-based comprehensive project documentation generator with dynamic task decomposition. Analyzes project structure and generates appropriate documentation tasks, computes optimal execution waves via topological sort, produces complete documentation suite including architecture, methods, theory, features, usage, and design philosophy.
Deploys the complete SDD architecture with engram persistence and ai-context/ memory layer in the current project. Also runs an opt-in interactive wizard mode (/project-setup --interactive) that bootstraps only a project CLAUDE.md with stop-between-question confirmation. Trigger: /project-setup, /project-setup --interactive, initialize new project, setup SDD, configure claude project, bootstrap claude, init project claude, create project CLAUDE.md.
Generates structured project status reports from monday.com - a customizable AI work platform with dedicated products for work management, CRM, dev, service, and campaigns. Surfaces overdue items, blockers, workload distribution, and recent activity across one or more boards. Use when user asks for "project status", "board summary", "what's overdue", "status report", "how's the project going", "weekly update", "board overview", "progress update", or "team workload".
When the user needs to research a prospect before a sales call, wants a pre-call intelligence brief, needs to understand a potential customer or partner, or says things like 'research this company,' 'I have a call with [company],' 'what should I know about,' 'prep me on this prospect,' 'look into [company] before my call.' For discovery call planning, see meeting-prep.
Converts a working Claude Code prototype into a structured Figma design file — exploding each interaction flow into separate frames, using the target file's design system components, and annotating interaction details natively in Figma. Use this skill whenever the user asks to turn a prototype into Figma frames, generate design specs from a prototype, create a Figma handoff from code, explode a prototype into states, or make a prototype reviewable by cross-functional partners. Also trigger when the user mentions "prototype to Figma", "design review from prototype", "async feedback on prototype", "break prototype into flows", "Figma specs from code", or wants to make a working prototype legible to non-technical stakeholders. Even if the user just says "put this in Figma" or "make this reviewable" in the context of a prototype, use this skill.
Python interface to PROJ (cartographic projections and coordinate transformations library). Handles transformations between different Coordinate Reference Systems (CRS) and performs geodetic calculations (distance, area on ellipsoids). Use for coordinate transformations, CRS conversions, geodetic calculations, UTM projections, GPS coordinate conversions, ellipsoidal distance calculations, and spatial reference system operations.
Python project scaffolding and development with modern tooling. Use when creating new Python projects, setting up virtual environments, configuring dependencies, or working with Flask web applications. Triggers on mentions of Python setup, uv, Flask, pytest, or project initialization.
Receive and verify Razorpay webhooks. Use when setting up Razorpay webhook handlers, debugging X-Razorpay-Signature verification, or handling payment events like payment.captured, payment.failed, order.paid, refund.processed, or subscription.charged.
React performance optimization guidelines from Vercel Engineering. This skill should be used proactively when writing, reviewing, or refactoring React code to ensure optimal performance patterns. Triggers on tasks involving React components, bundle optimization, or performance improvements.
Migrate from @trpc/react-query (classic) to @trpc/tanstack-react-query. Run npx @trpc/upgrade CLI for automated codemod. Manually migrate remaining patterns: hook-based to options-factory, utils.invalidate to queryClient.invalidateQueries with queryFilter, provider changes.
Automatically process multiple recruitment markdown documents, recognize images in the documents (including online image links), extract key information (position, salary, deadline, etc.), filter by user criteria, and generate a structured summary report
Run a bounded red-teaming autoresearch loop to generate LLM guardrail training data. You (the agent running the skill) are the attacker and the judge: you craft attacks and label every response. The only model the harness calls is the target under test, over any OpenAI-compatible API (OpenRouter, Moonshot/Kimi, Fireworks, Ubicloud, OpenAI, or custom), with its key in `.red-team/.env`. Every attempt (pass and fail) is written to JSONL ready for fine-tuning guardrails in Llama Guard format. Use when asked to red-team or stress-test an LLM for harmful content, jailbreaks, prompt injection, or backdoor/trigger behavior; to build a safe/unsafe dataset; or to mine novel attacks at scale. Complements the hacker skill (code/infra exploitability): this skill targets model behavior and produces data.
Discover and install related skills from inference.sh skill registry. Helps find complementary skills for your AI workflow. Use for: skill discovery, workflow expansion, capability exploration. Triggers: related skills, find skills, skill discovery, complementary skills, expand workflow, more capabilities, similar skills, skill suggestions
Use this skill when releasing a new version of a GitHub project, covering the full process of version number management, CHANGELOG syncing, writing release notes, creating tags, CI build monitoring, release verification, and history cleanup. Applies to any GitHub-based software project such as desktop apps, CLI tools, web apps, and libraries/SDKs. Triggers when the user mentions "发布" (release), "release", "打 tag" (tagging), "新版本" (new version), "更新版本号" (updating the version number), "写 release notes" (writing release notes), "发布失败了" (release failed), "CI 挂了" (CI is down), "Actions 配额告急" (Actions quota running low), "短时间内多次发版" (multiple releases in a short time), "monorepo", "批量打包" (batch packaging), "多 skill 发布" (multi-skill releases), "skill zip", "专家套件 zip" (expert suite zip). Also used to reject the anti-pattern of treating a release as a CI verification mechanism ("打 tag 看一下", just tag it and see). Do not use for non-GitHub projects (such as pure GitLab / Gitea projects) or manual release scenarios that require no CI.
Config-first setup wizard for a remindb MCP server — run it as `/remindb-setup` (interactive), `/remindb-setup automode` (hands-off), or `/remindb-setup only-config` (bridge hosts: author `.remindb/` only, no env wiring). Two passes. First-time (no server attached yet): detect the host, author the `.remindb/` config (ignore/pinned/temperatures/config.json) BEFORE compiling, compile the source, seed adjacent context, install the MCP plugin, then wire the MCP env. Verify (server attached): MemoryStats + `remindb://doctor`, reconfigure, and reseed onto existing nodes. Use on first-time workspace memory setup, when remindb tools are missing/misconfigured, on "no results"/wrong-workspace symptoms, to reconfigure an existing brain, or for bridge hosts that own env wiring externally (e.g. Hermes Agent).
Read this skill for every frontend, UI, or UX task, including small fixes, styling, components, interaction design, accessibility, reviews, and design-only advice across web, native, game, and embedded interfaces. For new or changed design decisions, visually research at least two comparable products and read relevant UX/UI guidance before proposing or coding. Study videos or live interactions for flows and motion, then visually verify the result.
Evidence-first research workflow for external web/source research and internal codebase investigation. Use when the user invokes $research, asks to research, investigate, audit what exists, compare options, understand current implementation, gather evidence, inspect docs, look up current facts, or answer repo-grounded questions before implementation. Prefer optional parallel agents for broad, separable research lanes such as external sources, codebase evidence, docs, risks, and competitor or alternative analysis.
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.