Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.
Design and optimize pricing strategies for SaaS products, including tiering, packaging, value metrics, and experimentation. Use when setting initial pricing, optimizing conversion, expanding revenue, or when users ask about pricing strategy, monetization, or revenue optimization.
Profile Dart command-line applications using the VM Service protocol to capture CPU samples and identify performance bottlenecks. Helps agents automate CPU profiling, generate function call breakdown summaries, and export JSON profiles without a browser or DevTools.
Generates comprehensive planning documentation for web application projects, structuring work into context-safe phases with built-in verification criteria. Creates IMPLEMENTATION_PHASES.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, and other planning docs based on project needs. Optimized for Cloudflare Workers + Vite + React stack. Use when starting new projects, adding major features, or restructuring existing work into manageable phases. Keywords: project planning, planning documentation, IMPLEMENTATION_PHASES.md, DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, UI_COMPONENTS.md, TESTING.md, AGENTS_CONFIG.md, phased development, context-safe phases, verification criteria, exit criteria, planning docs generator, web app planning, Cloudflare Workers planning, Vite React planning, project structure, project phases, major features planning, new project setup
Write a structured project status report for any project. Use when asked to write a project update, status report, RAG report, project dashboard narrative, or weekly project communication. Produces a clear status report with RAG ratings, milestone progress, risks, and decisions needed.
Read-only proofreading pass over lecture `.tex` or `.qmd` files. Checks grammar, typos, overflow, terminology consistency, and academic writing quality; produces a report without editing. Use when user says "proofread", "check for typos", "look for grammar issues", "copy-edit this", "any writing errors?", or before a lecture release.
Make a design question tangible before committing to it: compare production-representative UI directions for a screen, component, or short flow, or drive a logic, state, data-shape, API, or CLI model through a shareable HTML demo. Use before committing to a visual, interaction, or behavioral design; not for production implementation.
Manage terminal sessions with screen snapshots, cursor-based output recovery, terminal resizing, and independent session ownership. Use when existing terminal tools lack the needed PTY or session features, or when a workflow specifically requires pty-bridge. Ordinary commands and simple interactive sessions can use existing terminal tools when sufficient.
Read the diff for a change and produce a short, manual QA checklist to run against the deployed app — only the behaviour this change actually touched, written as plain-English steps a person can click through. Use when the user asks for a "QA checklist", "manual test plan", "what should I test", "smoke test steps", or how to verify a change by hand after deploy.
When the user wants to improve product quality, implement quality control systems, reduce defects, or analyze quality data. Also use when the user mentions "SPC," "statistical process control," "Six Sigma," "DMAIC," "control charts," "process capability," "Cp," "Cpk," "quality control," "defect reduction," "inspection," "acceptance sampling," or "quality assurance." For lean improvements, see lean-manufacturing. For process optimization, see process-optimization.
Crash and vulnerability sample analysis: deterministic reproduction, ASAN/UBSAN report interpretation, input minimization (afl-tmin/cmin), gdb backtrace localization, rr recording and replay, and PoC generation. Trigger terms: crash, ASAN, UBSAN, undefined behavior, UAF, heap overflow, out-of-bounds, segmentation fault, segfault, core dump, PoC, vulnerability analysis, crash analysis.
Electron desktop app reverse engineering: asar unpacking, main/renderer process JS, V8 bytecode (.jsc) boundaries, CDP dynamic debugging, and anti-debugging countermeasures. Triggers: Electron, asar, desktop app reverse engineering, .jsc, V8 snapshot, CDP, ELECTRON_RUN_AS_NODE, devtools detection.
Coverage-guided fuzzing: AFL++/libFuzzer/honggfuzz, instrumentation and corpus initialization, afl-fuzz runtime parameters, coverage (afl-cov), dictionaries/structured inputs. Trigger terms: fuzz, fuzzing, AFL, afl-fuzz, libFuzzer, honggfuzz, coverage, corpus, dictionary, vulnerability hunting.
Managed code reverse-engineering gateway. Orchestration: identify runtime → decompile → deobfuscate → route malware scenarios to [[re-malware]]. Subskills: [[re-dotnet]] [[re-java]] [[re-script-deob]] [[re-wasm]] [[re-ai-triage]] → [[re-ai-model]] [[re-blockchain]] [[re-python]]、[[re-browser-ext]]、[[re-electron]]、[[re-javacard]]. Trigger terms: .NET, dnSpy, ILSpy, Java, jar, bytecode, PowerShell obfuscation, VBA macro, JS deobfuscation, managed code.
Vulnerability hunting gateway. Orchestration: identify targets and input surfaces → coverage-guided fuzzing → crash analysis → reverse-engineering and localization → report. Sub-skills: [[re-fuzzing]] [[re-crash-triage]] [[re-exploit]]. Trigger terms: vulnerability hunting, find vulnerabilities, fuzz, fuzz testing, AFL, libFuzzer, crash analysis, crash, vulnerability hunting, fuzzing
React 19 + TypeScript for FMC TanStack Start apps: typed components, events, generics, ref-as-prop, Compiler-first memoization, and useEffect discipline (naming, when not to use Effect, alternatives). Use when typing React components/hooks/events, or writing/reviewing useEffect, useEffectEvent, derived state, data-fetch effects, or oxlint React Compiler / Rules of React effect rules. Not for routing/server boundaries (see tanstack-start-* skills).
Provides comprehensive guidance for React Native development including components, navigation, native modules, platform-specific code, and mobile app development. Use when the user asks about React Native, needs to create mobile applications, implement React Native components, or work with React Native features.
Provides one-command project creation for React Native including project initialization, configuration, and template generation. Use when the user asks about creating React Native projects, needs to initialize a new React Native project, or generate React Native project structure.
Expert in the React Bits UI component framework. When developing front-end pages, always prefer components from the react-bits framework to produce standardized code. Supports describing requirements in natural language and automatically matches the best component combinations. Trigger words: react-bits, reactbits, animated component, landing page, hero section, front-end page development, make a page.
Use this skill to record a terminal or TUI demo with VHS whenever the user wants to "record a demo", "create a GIF of my CLI", "write a VHS tape", "make a terminal recording", or "add a demo GIF to the README" — even if they never say "VHS" and only ask for an animated demo of a command-line tool. Covers tape syntax, dimensions, pacing, GIF size reduction, and CI golden-file recording. Do NOT use this skill to build the TUI itself (see build-tui), to screenshot a web app on localhost (see screenshot-local), or to capture video of anything outside a terminal.
Design and audit refund, cancellation, chargeback, dispute, entitlement revocation, repurchase, appeal, and customer support flows for SaaS, mobile apps, games, utilities, marketplaces, and subscriptions. Use when handling refund policy, abuse ladders, support macros, account restrictions, trust recovery, or post-refund product access.
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.