Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Keep gbrain current. When a `gbrain` invocation prints an `UPGRADE_AVAILABLE <old> <new>` marker (or `gbrain self-upgrade --check-only` reports an update), apply it per the configured self_upgrade.mode: notify (prompt the operator with a 4-option question + snooze) or auto (apply silently). The action is always the hardcoded `gbrain self-upgrade` — never a command read from the marker.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Inspect and operate Inngest Cloud through its OAuth MCP connection. Use for deployed apps and functions, failed or slow runs, traces, events, environments, sessions, experiments, and Insights. Prefer this for Cloud operations when MCP tools are available; use CLI or REST skills for explicit terminal or HTTP tasks.
Apply the education-first mindset — make everything you build teachable, create nano-project explanations, write for beginners. Use this skill when the user wants to explain a project to beginners, create a tutorial from code, write documentation that teaches (not just documents), make a concept accessible, or says "make this teachable", "explain like im a beginner", "nano project version", "teaching version", "explain from scratch", "blog post about this". Based on Karpathy 243-line GPT and Eureka Labs posts.
Apply rigorous supply chain security hygiene to software projects — audit dependencies, detect risks, minimize attack surface. Use this skill when the user wants to audit project dependencies, is concerned about supply chain attacks, wants to set up secure dependency management, needs to review a requirements.txt or package.json, or says "dependency audit", "supply chain risk", "check packages", "secure dependencies", "pin versions", "check pypi". Based on Karpathy 28k-like litellm supply chain post.
Deeply analyzes Amazon niches by product ASIN, covering monopoly level, brand concentration, new product success rate, and market opportunity score. Trigger this skill when users mention niche analysis by ASIN, ASIN market research, finding the niche for an ASIN, monopoly assessment, brand concentration analysis, new product success rate, market demand score, competitive landscape, Amazon submarket exploration, ASIN niche analysis, niche by ASIN, monopoly level, brand concentration, new product success rate, market opportunity score, competitive landscape, or Jiimore data. Even if the user does not explicitly mention “niche” or “ASIN,” trigger this skill whenever their request involves assessing the competitive landscape, brand density, or opportunity potential of the niche associated with a product ASIN.
Creates event-driven email listeners that monitor for specific conditions (like urgent emails from boss, newsletters to archive, package tracking) and execute custom actions. Use when user wants to be notified about emails, automatically handle certain emails, or set up email automation workflows.
Generates a self-contained Python experiment client that uses the ddtrace.llmobs SDK. Emits either a runnable .py script or a Jupyter .ipynb notebook matching the canonical DataDog reference notebook style. Use when the user says “generate Python experiment,” “write an SDK experiment,” “create a ddtrace experiment,” “Python notebook experiment,” “use the LLM Obs SDK,” or has `ddtrace` installed and wants idiomatic SDK code.
Write, edit, and review MaaFramework (MaaFW) pipelines — creating tasks and sub-flows from scratch (breaking large tasks into nested reusable sub-flows, translating requirements into states, naming resource files and nodes, writing recognition/action nodes and defining ROIs, designing next chains with branches, loops, interrupts and timeout fallbacks, and self-checking reachability) and refactoring existing ones (surveying reusable nodes, searching the whole codebase for references before renaming, reviewing coordinate hygiene and anti-patterns). Use when authoring, editing, or reviewing any pipeline JSON in a MaaFW project — adding tasks, sub-flows, or nodes, breaking large tasks into nested reusable sub-flows, choosing TemplateMatch/OCR/ColorMatch or action types, sizing ROIs, designing next chains with branches, loops, interrupts, and timeout fallbacks, naming or renaming pipeline files, folders, nodes, or template images, or refactoring existing pipelines for coordinate hygiene and anti-patterns.
Complete guide for MagicBlock Ephemeral Rollups - high-performance Solana execution with sub-10ms latency, gasless transactions, and Solana Plugins. Use when building real-time games, high-frequency trading, or any application requiring ultra-low latency on Solana.
Inspects and configures the security headers a Power Pages site sends to browsers — Content Security Policy, frame and clickjacking protection, cross-origin sharing, cookie behavior, and related site settings. Identifies gaps and walks the user through fixes. Use when the user wants to review headers, fix CSP errors, allow embedding in another site, control cross-origin access, harden cookie settings, or asks "are my browser settings safe?", "fix my CSP", "set up CORS" — even if they only mention a specific header name without saying "security headers".
Merge changes from another branch while reviewing them against the project's principles — a merge is a review gate, not a mechanical operation. Use when the user asks to merge a branch, bring changes in from another branch, or resolve a merge. Flags unclear intent, unnecessary complexity and likely bug sources before merging, asks the user about any product decision a conflict would settle, and recommends merging the main integration branch into the other branch first when that is the easier direction.
Mermaid diagram syntax for flowcharts, sequence diagrams, ERDs, class diagrams, and more. Use when creating diagrams in Markdown, generating architecture visuals, or documenting system flows. Use for mermaid, diagram, flowchart, sequence, ERD, class-diagram, gantt, pie-chart, and mindmap.
Build reusable dimension / lookup tables for a star schema — country/region, timezone, currency, date, plan/product, and other descriptive attributes — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model dimension tables, lookup tables, a star schema, conformed dimensions, or wants to enrich events/revenue/usage with country, region, timezone, plan, or currency attributes without repeating JOINs. Covers sourcing the dimension data (upload, warehouse source, or derive from events), shaping it into an aliased one-row-per-entity view (optionally materialized on a slow schedule since dimensions change rarely), and attaching it to facts via a saved or person join so its columns read as native fields. Key rule: for currency use the built-in convertCurrency() instead of a hand-rolled rate table. Read modeling-warehouse-foundations first; dimensions here are reused by the revenue, conversion, activation, and product-usage modeling skills.
Generate one or more standalone Meta image-ad creatives via Nano Banana 2 / Nano Banana Pro (Gemini Flash Image family) through the Arcads external API. Locks the model family, auto-strips platform chrome, enforces edge-safe layouts. Use when the user asks for a “Nano Banana ad,” “Gemini image ad,” “nano-banana-2 ad creative,” “make a static image ad with Gemini,” or anchors on a need for photoreal / lifestyle / multi-reference / handheld-object / clay-texture ad creatives (sticky-note flatlays, held-whiteboard signs, lifestyle portraits, ingredient collages, OOH photography). Does NOT trigger on ChatGPT Image cues — use chatgpt-image-ad for those.
Perform a multidimensional preliminary assessment based solely on the story text provided by the user (market potential, originality, and content strengths). Use for preliminary screening of novels or stories and quality assessment without external information. Do not use when online research into popularity, author background, or rights data is needed; use ip-evaluator instead.
Read academic papers from a bare arXiv abs/pdf/html URL, a PDF, a paper title, or Zotero. Use for "read this paper", "analyze this paper", "读一下 XXX", "读一下这篇", "帮我读", "看一下这篇论文", "论文笔记", quick summaries, critiques, and Zotero collection reading. A standalone arXiv link or ordinary reading request defaults to full reading and automatic note saving in the configured Obsidian/Markdown library. Honor explicit depth, destination, and no-save requests; a citation used for another task does not trigger reading.
GPU-based particle systems using instanced rendering, buffer attributes, Points geometry, and custom shaders. Use when rendering thousands to millions of particles efficiently, creating particle effects like snow, rain, stars, or abstract visualizations.
Guide for testing Polar payment integrations using the sandbox environment. Use this skill when: (1) Setting up the Polar sandbox for development; (2) Testing checkout flows without real payments; (3) Using Stripe test cards with Polar; (4) Writing integration tests for payment flows; (5) Testing webhooks locally with the Polar CLI (`polar listen`, `polar trigger`) and generating webhook fixtures; (6) Mocking Polar in unit tests; (7) Setting up CI/CD pipelines with Polar sandbox; (8) Debugging payment issues in sandbox.
PostgreSQL 18+ enterprise best practices for database development. USE THIS SKILL WHEN THE USER: - Creates schemas, tables, functions, procedures, or triggers - Writes PL/pgSQL code (naming conventions: l_, in_, io_, co_ prefixes) - Implements Table API (SECURITY DEFINER functions, schema separation) - Manages migrations, indexes, constraints, or query performance - Works with PostgreSQL 18+ features (uuidv7, virtual columns) - Builds Medallion Architecture data warehouses (Bronze/Silver/Gold) - Reviews code for anti-patterns or migrates from Oracle PL/SQL CORE PATTERNS: - Three-schema separation: data (tables) → private (internal) → api (external) - Table API: All access via SECURITY DEFINER with SET search_path - Native PL/pgSQL migration system (no Flyway/Liquibase needed) - Trivadis naming: l_ (local), in_ (input), io_ (inout), co_ (constant)
Use when the user wants to optimize procurement decisions, allocate orders across suppliers, or determine optimal order quantities. Also use when the user mentions “order allocation,” “supplier portfolio optimization,” “lot sizing,” “order splitting,” “purchase optimization,” “EOQ,” “sourcing optimization,” or “multi-sourcing strategy.” For supplier selection, see supplier-selection. For spend analysis, see spend-analysis.
Scaffolds React 19 / React 19.2 code in TypeScript — components, Server Component pages, client islands, form actions with useActionState, context providers, custom hooks, reducers, or document metadata + resource hints. Generates production-grade code that follows React 19 idioms (ref-as-prop, <Context value={...}>, useActionState, inline metadata, useSyncExternalStore) and refuses deprecated React 18 patterns (forwardRef, <Context.Provider>, useFormState, react-dom/test-utils). Trigger even when the user says "create a component", "new page", "add a form", "new hook", or "scaffold X" without explicitly mentioning React 19.
Route RealityKit work on visionOS 27 and handle core entity/component basics, RealityView scene setup, asset loading, input targets, SwiftUI attachments, anchoring, portals, synchronization, and USDStage bridge usage. Use for general RealityKit triage, choosing documented components, loading Reality Composer Pro, USD, USDZ, or .reality content, and deciding whether to hand off to realitykit-rendering-materials, realitykit-animation-physics, realitykit-audio-spatial, realitykit-ecs-systems, spatial-preview-developer, usdkit-runtime-developer, usd-editor, shadergraph-editor, ARKit, SwiftUI, or build-debug skills
Generates render and output configuration for Remotion videos. Focuses ONLY on output settings, codec, format, quality, resolution. Input is target platform/quality requirements. Output is RENDER_CONFIG.md with Remotion render settings.
Pick up unfinished work from docs/<feature>/HANDOFF.md in a fresh session — you are the agent the handoff was written for, and you verify it before you trust it. Use when the user invokes /resume-handoff <feature>, points at a HANDOFF.md, or asks to continue, resume, or pick up where the last session stopped on a plan or roadmap built by execute-plan, execute-roadmap or build-feature, e.g. "pick up the handoff and keep going while I sleep". Reads the project's agent orientation and the handoff, reconciles its claims with git and the code, surveys the pending merge and proposes the scope — then stops and asks the user to confirm the merge and plan of work, or give new instructions, before anything changes the tree. On confirmation it deletes the consumed handoff, merges through the merge-branch gate, continues under execute-plan or execute-roadmap, and writes a fresh handoff at the end if work is still owed. For writing a handoff, use write-handoff; for retiring finished work, use close-plan or close-roadmap.
When the user wants editing guidance for YouTube retention, pattern interrupt techniques, pacing direction, or re-engagement strategies. Also use when the user says 'editing for retention,' 'pattern interrupts,' 'how should I edit this,' 'pacing guide,' 'my videos lose viewers in the middle,' 'editing notes,' 'retention editing,' 'keep viewers watching.' For script-level retention, see script-structure. For analyzing retention data, see video-analysis.
Review an experience, technical, plan, roadmap, or implementation doc from draft-experience, draft-technical, build-feature or draft-roadmap — you are the reviewer, not the author. Use when the user asks to review a plan, roadmap, design or experience document, or invokes /review-doc <feature>. Reads docs/<feature>/<DOC>.revN.md, writes <DOC>.revN.notes.md grounded in the product shape, the project's principles and the actual code, and iterates with the user until the doc is ready to become <DOC>.final.md.
GLSL shader fundamentals—vertex and fragment shaders, uniforms, varyings, attributes, coordinate systems, built-in variables, and data types. Use when writing custom shaders, understanding the graphics pipeline, or debugging shader code. The foundational skill for all shader work.
Add, improve, audit, wedge, or autoimprove a skill. Improve and audit also accept a sub-agent definition. The result runs predictably on Claude Code, Codex, OMP, and other Agent Skills hosts. Use for /skillz <add|improve|audit|wedge|autoimprove>, "improve this skill", "autoimprove this skill", "optimize this skill", "tighten this skill", "audit this agent", "new skill for X", "skill not triggering", "fix trigger rate", "wedge this", "turn this repeated work into a CLI", or "what in this skill should be a CLI". Do NOT use for CLAUDE.md or system-prompt edits, or for code changes that a cheese pipeline skill owns.
Use only after `sn-ppt-entry` and `sn-ppt-story` have prepared the absolute `DECK_DIR` and `outline.md`. Generate a separate HTML file for each slide (1600×900), rendered PNGs, speaker notes for each slide, and `present.html`; generate PPTX converted by Standard’s own exporter as selected by `static_postprocess`. **`present.html` is always a required deliverable; missing it is a technical failure, and it must not be delivered. When `static_postprocess` includes `pptx`, PPTX is also required (omitting either is a technical failure) and must be generated only by Standard’s own exporter. PPTX may be omitted only when the user explicitly requests HTML only (`static_postprocess` is `[]`).**
Resolve Git merge or rebase conflicts based on each side’s intent, preserving behavior and validating integration. Use when an operation with unmerged files already exists; do not abort, rewrite remote history, or choose one entire side without authorization.
Implements the Syncfusion WPF DockingManager control for Visual Studio-like docking interfaces with MDI/TDI support, floating windows, and auto-hide panels. Use when creating docking layouts, window management systems, tabbed document interfaces, or IDE-style layouts in WPF applications. Covers dock panels, floating windows, auto-hide functionality, state persistence, and window management.
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.