Skills
97,501 packaged capabilities and playbooks for agents. Install any of them with one command.
All
This skill should be used when creating, validating, or converting Product Requirements Documents (PRDs) to LLM-native format. Use this skill when the user asks to write a PRD, review a PRD for compliance, convert an existing PRD to machine-readable format, or ensure PRD quality for AI agent consumption. This skill is optimized for users working with agentic coding frameworks who need strict requirement specifications to prevent context poisoning, hallucination, and mesa-optimization.
When the user wants to predict future cash consumption and “Runway” using time-series AI models. Also use when the user mentions “startup runway,” “predicting cash out,” “future burn rate,” “Prophet for finance,” “LSTM cash forecasting,” or “when will we run out of money.”
Design and audit enterprise procurement security review readiness, vendor risk questionnaires, security evidence packets, DPAs, subprocessors, insurance, policies, SOC/ISO evidence, pen test summaries, AI/data-use answers, redlines, gap handling, and sales/legal/security handoff. Use when deals stall on vendor review or buyer assurance.
Generates professional product images for e-commerce platforms (Amazon, Shopify, eBay, etc.). Supports 8 visual styles and 6 scene types optimized for different product categories. Use when the user mentions “商品图”, “product images”, “Amazon listing”, “电商图片”, or needs e-commerce product photography.
Use when asked about "product-led growth", "PLG strategy", "self-serve growth", "freemium model", "free trial design", "product-led sales", "PQL", or "bottoms-up growth". Helps design and optimize product-led growth motions where the product drives acquisition, activation, and monetization. Based on frameworks from Elena Verna and Hila Qu.
Build and manage a product roadmap for a solopreneur business. Use when deciding what to build next, prioritizing features, planning product development over quarters, communicating plans to customers or stakeholders, or managing scope and expectations. Covers prioritization frameworks, roadmap structure, customer feedback integration, and saying no to feature requests. Trigger on "product roadmap", "what to build next", "feature prioritization", "roadmap planning", "product strategy", "feature requests".
Plan, focus, and complete work with energy management, time blocking, goals, projects, tasks, habits, reviews, priorities, and context-specific productivity systems; use when (1) the user needs help with productivity, focus, time management, planning, priorities, goals, projects, tasks, habits, or reviews; (2) they want a reusable structure or workspace for organizing work; (3) ongoing work should be routed through a dedicated productivity framework.
Inspect a Kotlin + Spring repository before making changes or answering implementation, debugging, build, architecture, or review questions. Use when the agent must map modules, Spring Boot/Kotlin/Gradle/JDK versions, compiler plugins, profiles, dependencies, runtime stack, and architectural boundaries so later advice stays compatible with the real project.
Project documentation structure creation assistant. Acting as a senior product manager, it uses multi-turn dialogue to deeply understand project requirements, analyse their soundness and offer best-practice suggestions, and finally generate a complete technical documentation system. **When to use:** - A new project starts and a documentation system needs to be set up (recommended first step) - An existing project lacks standard documentation and needs to be completed - Code already exists but documentation is missing, and documentation needs to be backfilled from the code - Professional product and architecture analysis advice is needed **Two supported working modes:** - Mode A: new project documentation creation (from requirements to documentation) - Mode B: code-based documentation backfill (from code to documentation) **Relationship with other skills:** - This skill creates complete documentation (PRD, SAD, development guide, etc.) - project-workflow executes development tasks based on the documentation - Recommended flow: project-docs-setup → project-workflow **Triggers:** - "创建项目文档" / "初始化项目文档" / "设置项目文档" - "根据代码生成文档" / "回补项目文档" / "补充项目文档" - Directly describing project requirements, e.g. "帮我创建一个在线教育平台的文档"
Use when managing prompts in production at scale: versioning prompts, running A/B tests on prompts, building prompt registries, preventing prompt regressions, or creating eval pipelines for production AI features. Triggers: 'manage prompts in production', 'prompt versioning', 'prompt regression', 'prompt A/B test', 'prompt registry', 'eval pipeline'. NOT for writing or improving individual prompts (use senior-prompt-engineer). NOT for RAG pipeline design (use rag-architect). NOT for LLM cost reduction (use llm-cost-optimizer).
Engineers prompts into clear, structured, model-optimized instructions using the 4-D methodology (Deconstruct, Diagnose, Develop, Deliver) with architecture-specific tuning. Use when a draft prompt, instruction set, or agent skill description needs refinement for clarity or improved performance.
Audit a recently written Playwright test as a fresh pair of eyes. Reviews only the most recent uncommitted changes via git diff, checks compliance with the project's Playwright scripting rules, architecture, and POM conventions, and reports findings before optionally applying fixes.
Python library for working with DICOM (Digital Imaging and Communications in Medicine) files. Use this skill when reading, writing, or modifying medical imaging data in DICOM format, extracting pixel data from medical images (CT, MRI, X-ray, ultrasound), anonymizing DICOM files, working with DICOM metadata and tags, converting DICOM images to other formats, handling compressed DICOM data, or processing medical imaging datasets. Applies to tasks involving medical image analysis, PACS systems, radiology workflows, and healthcare imaging applications.
PyGraphistry visualization: bindings, color/size/icon encodings, layout controls, static export, and privacy-safe link sharing. Use when asked to "color nodes by type", "set point size", "add icons to nodes", "layout my graph", "export graph as PNG", "share a graphistry link privately", or "url_params". Also triggers on "encode_point_color", "bind(point_label=...)", "settings(url_params=...)", "badge", "static graph image", or "iframe embed". Proactively suggest when the user has a working plot but wants to customize its appearance or control link sharing and privacy.
Builds clinical deep-learning pipelines with PyHealth using its Dataset → Task → Model → Trainer → Metrics pattern. Covers loading MIMIC-III/IV, eICU, OMOP, SleepEDF, ChestXray14 and EHRShot data, defining prediction tasks (mortality, readmission, length of stay, drug recommendation, sleep staging, ICD coding, EEG events), models such as Transformer, RETAIN, GAMENet, SafeDrug and StageNet, training with Trainer, and ICD/ATC/NDC/RxNorm code lookup and cross-mapping. Use when building a clinical prediction model on EHR data. Use when working with MIMIC or eICU datasets. Use when recommending drugs or staging sleep from signals. Use when mapping medical codes between ICD, ATC, NDC or RxNorm. Not for generic PyTorch on tabular data.
Control PyMOL molecular visualization through Claude Code. Use when asked to "visualize protein", "render structure", "show cartoon", "color by chain", "ray trace", "set up pymol", "install pymol", or work with molecular graphics. Handles setup, visualization commands, and publication-quality figure generation.
Complete mass spectrometry analysis platform. Use for proteomics and metabolomics workflows—feature detection, peptide/protein identification, label-free and isobaric quantification, adduct/accurate-mass annotation, and complex LC-MS/MS pipelines. Supports extensive file formats and algorithms. For simple spectral comparison and small-molecule library matching use matchms.
Use when defining or evolving public interfaces, schema boundaries, or pydantic usage in Python. Also use when annotations are missing on public APIs, pydantic models appear everywhere instead of at trust boundaries, contract changes lack migration guidance, or Any/object types are overused across module boundaries.
Evidence-driven scientific figure skill for Nature Portfolio and high-impact journals. Use it to design single and multi-panel figures from raw or summarized data, choose an appropriate graphics grammar, write Python/R plotting code, redraw existing figures, draft mechanism diagrams, write figure captions, and export editable SVG/PDF and high-resolution TIFF/PNG; it also checks data integrity, color accessibility, statistical annotations, and final-size readability. Trigger scenarios include Nature figure, scientific figure, publication plot, multi-panel figure, graphical abstract, mechanism diagram, and figure audit.
HogQL query examples and reference material for PostHog data. Read when writing SQL queries to find patterns for analytics (trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, LLM traces) and system data (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse). Includes HogQL syntax differences, system model schemas, and available functions.
Set up a Quiver bolt's three-layer bootstrap stack (public bootstrap repo, private dotfiles repo, private workspace repo, an age key, and an SSH key) and create the bolt. Use when a user wants to configure a new Quiver persona or dotfiles stack, onboard to Quiver, or spin up a bolt dev environment from scratch. Works on macOS, Linux, and Windows.
Use when planning or reviewing production database migrations, adding columns, indexes, constraints, backfills, renames, table rewrites, or concurrent operations. Covers phased rollouts, lock behavior, rollback strategy, strong_migrations compliance, and deployment ordering for schema changes.
Route requests to the focused Randroid development workflows and explain which capability to use. Use when the user asks what Randroid skills are available, invokes the Randroid namespace without naming a workflow, or needs help choosing among loop execution, PR feedback handling, VibeReview playtesting, visual de-slopping, and gameplay interaction or feedback work.
Expert implementation of @vis.gl/react-google-maps library for Google Maps in React. Use when building maps, markers, pins, infowindows, places autocomplete, geocoding, draggable markers, polygons, circles, polylines, drawing tools, or any Google Maps JavaScript API integration in React/Next.js applications.
Build type-safe validated forms using React Hook Form v7 and Zod v4. Single schema works on client and server with full TypeScript inference via z.infer. Use when building forms, multi-step wizards, or fixing uncontrolled warnings, resolver errors, useFieldArray issues, performance problems with large forms.
React component patterns and architectural best practices. Covers compound components, render props, higher-order components, custom hooks, composition, state machines, and container/presentational patterns. USE WHEN: user mentions "compound components", "render props", "HOC", "higher-order component", "composition pattern", "component architecture", asks about "reusable components", "component patterns", "slots pattern", "polymorphic components" DO NOT USE FOR: Basic React components - use `react` skill instead, hooks implementation - use `react-hooks` skill instead, performance patterns - use `react-performance` skill instead
Advise on and review React code through the lenses of "Advanced React" (Makarevich) — unnecessary re-renders, composition-before-memoization, the memo/useMemo/useCallback traps, Context performance, refs & stale closures, debounce/throttle, useLayoutEffect flicker, portals & stacking context, data-fetching waterfalls & race conditions, and error boundaries. Use when writing or reviewing a React component/hook/context/provider, when chasing "why does this re-render" or "should I memoize this", or when dealing with stale state in a callback, UI flicker, modal clipping, fetch race conditions, or error handling. Detects the target repo's React version and state/UI libraries before applying version-specific rules. Distinct from architecture-lens (architecture) and design-patterns (GoF).
React component testing with Testing Library and Vitest. Covers unit tests, integration tests, async testing, mocking, user events, accessibility testing, and test patterns. USE WHEN: user mentions "React testing", "Testing Library", "Vitest", "component tests", "userEvent", "screen queries", "MSW", asks about "testing React components", "mocking in tests", "accessibility testing", "React test patterns" DO NOT USE FOR: E2E testing - use Playwright skill instead, backend testing - use framework-specific testing skills, general testing concepts - use testing framework skills
Review backend pull requests for correctness, security, performance, maintainability, and test coverage using GitHub CLI plus local repository inspection. Use when asked to review service-layer/API/database changes, audit backend branch diffs, summarize backend risk, or produce actionable must-fix/should-fix feedback.
Researches homes and used cars via the Crawlora API—Zillow and Redfin property search/estimates/market trends, plus CarMax, Autotrader, and Cars.com vehicle search and dealer/listing detail—returning clean JSON. Use when the user wants to search homes or cars, get a property estimate or a region's market trend, or look up a specific listing/vehicle/dealer.
Use when starting an assessment and you need to discover an application's full attack surface — subdomains, hosts, endpoints, technologies, exposed services, leaked credentials and secrets — on assets you own or are authorized to test. Feeds the threat model with real, not assumed, targets.
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.