Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
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.
Main entry point for the Show Me The Money business automation suite. Dual mode: pre-task routing (which skill fits your problem) + post-task navigation (a skill just finished — what's next). Use when the user wants to start a business, automate operations, generate revenue, find product ideas, set up marketing, or run any business function autonomously. Also use when the user says 'show me the money', '来财' (the suite's Chinese name), 'make money', 'start a business', 'automate my business', 'build a company', 'what's next', or '下一步怎么走'. Includes a beginner tutorial mode triggered by '/money onboarding', '/money tutorial', '/money 新手', '/money 教程', 'how do I use this', or '这个怎么用' — a zero-input guided walkthrough that produces a demo business brief.
Discover profitable business ideas from scratch. Analyzes market gaps, trending niches, user skills, and competitive landscapes with a competitive intelligence protocol including 4-filter benchmark stress test and Blue Ocean differentiation grid. Use when the user has no idea what to build, wants to explore opportunities, needs market research, competitive benchmarking, or says 'find me a business idea', 'what should I build', 'market research', 'find opportunities', or 'competitive analysis'.
Design and build motion-first creative websites — page design (structure, type scale, palette, spacing) plus interaction choreography: scroll animation, Framer Motion, GSAP, and light 3D via Three.js/R3F. Use for animated landing pages, creative portfolios, product showcases, WebGL-lite scenes, and motion audits. Also use when tuning interaction handfeel (手感差/太生硬/不跟手), replicating motion from a video or URL reference (复刻), building 3D depth from flat image assets (伪3D/抠图), diagnosing dead scroll-timeline stretches, mixing scene audio, auditing discoverability (点不开/没人会发现), building headless verification probes, or fixing a page that moves well but looks generated (不好看/像AI做的/没设计感). Equally for building a whole site from nothing (从0到1做个网页/落地页/官网/作品集): stack choice, sections and copy, components (导航/hero/表单/卡片/定价表), and production polish (favicon/OG/404/空状态/暗色模式). Not for dashboards, admin UI, or full 3D scene generation.
Rebuilds an AI-generated (or any) flat motion design video as clean, editable code: inline SVG shapes animated by one GSAP timeline, seekable frame by frame, looping seamlessly, checked side by side against the source; and optionally turns an interface recording into a real interactive website (GSAP ScrollTrigger, real clicks). Ships scripts to study the video (frames, cuts, contact sheet, exact palette), render the code to mp4/GIF through anim.seek, compare it with the source frame by frame and check the loop seam and page contract. Use when the user wants a video, GIF, Lottie-like clip, motion design shot, animated logo, UI screen recording or AI video "recreated in code", "converted to SVG/GSAP", "made into an HTML animation" or "made into a real site". Not for photographic footage, 3D rendering or video editing
Designs, builds, debugs, and documents n8n workflows and AI agent automations. Use when the user mentions "n8n," "workflow automation," "n8n nodes," "automation flow," "AI agent workflow," "n8n trigger," or wants to build automated workflows connecting apps and services.
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, selecting the HTTP Request node for network access, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
Per-feature NaN-safe Spearman/Pearson correlation across many features (genes, proteins, variants) with missing values. Covers why bulk matrix shortcuts fail, correct pairwise deletion, degenerate input filtering, and large-dataset performance. Use statistical-analysis for test choice; shap-model-explainability for interpretability.
Use when creating game worlds, lore, factions, geography, timelines, or establishing world consistency rules. Genre-agnostic — works for fantasy, sci-fi, modern, or abstract settings. Triggers: lore, factions, geography, world bible, world creation.
Write like a human, not a language model. Avoid AI-tell vocabulary, formulaic structures, and hollow emphasis. Apply to ALL written output including prose, documentation, comments, and communication. Use when drafting prose, documentation, comments, or any written output that should sound human.
Use when searching, extracting, ingesting, or querying a document collection with the NeMo Retriever 26.8.1 CLI, including local LanceDB indexes and deployed Retriever services. Use for PDFs, images, Office files, HTML, text, audio, and video; not for editing documents or web search.
Pipeline for Neuropixels extracellular electrophysiology: probe geometry (ProbeInterface), Kilosort sorting via SpikeInterface, quality metrics, unit curation (ISI, firing rate, SNR), post-sort analysis (PSTH, tuning curves, population decoding). Supports Neuropixels 1.0/2.0/Ultra in rodent/primate experiments.
NocoBase 2 only; never use in a NocoBase 3 project. Use when users need to configure, inspect, test, or troubleshoot NocoBase notification management, including in-app message channels, email SMTP channels, workflow notification nodes, and notification send logs.
NocoBase 2 only; never use in a NocoBase 3 project. Use when a task provides a prototype to reproduce — an HTML file, an image, or a link, INCLUDING the published form "Build a NocoBase app — X … Match the layout and signature visuals of this reference prototype: <url>" — or when someone says a built page "doesn't match the prototype / looks monotone / is ugly". A prototype/URL being present is what triggers this skill, EVEN WHEN the same prompt also says "build an app" — the verb "build" does not cancel the prototype. Skip it only when there is NO prototype at all: a bare "build me a CRM/app" → nocobase-app-discipline; a one-field edit / rename → nocobase-ui-builder. It turns "here is the prototype, build it" into a faithful app — analyze prototype, native CRUD, the right native block per region, then a screenshot-vs-prototype visual loop. Native-first; JS only inside a native container; never a full-page JS block. Mechanics live in nocobase-ui-builder, nocobase-data-modeling, nocobase-app-discipline.
Novig exchange — public events, market catalog (outcomes, fees, void rules), and order books. No API key, read-only. Covers NFL, NBA, MLB, NHL, NCAAF, NCAAB, WNBA, soccer, tennis, MMA, golf, esports. IMPORTANT: catalog markets carry no prices; prices come only from `get_order_book` (bids per outcome as probabilities, each contract pays $0.01). Use when: user asks what Novig lists for a game or league, Novig order-book prices for a market, or wants Novig alongside other venues. Don't use when: user wants to place or cancel orders (not supported). For Kalshi/Polymarket/ProphetX prices use those skills; for cross-venue comparison use markets. For scores/stats use the sport-specific skill
(NS) Senior Tech Lead code review on SOLID, clean code, performance, security, and testability. Use proactively after writing or modifying code, before opening PRs, after implementation closure, or when the user asks for a code review, PR review, or issue review gate — even if they do not name this skill. For GitLab issue execution with ISSUE_URL, use Issue review mode. Do NOT write code-review-report.md. Do NOT use for root-cause debugging (use ns-code-investigator).
(NS) Generate or refresh project AGENTS.md plus CLAUDE.md (Rules boot + AGENTS.md + .claude/agents) after harness install. Use for "write AGENTS.md", bootstrap agent entry point, replace harness stub, or configure Cursor/Claude project rules. Do NOT copy the harness template verbatim. Do NOT use for architecture-rules, reverse business specs, or brownfield maps.
(NS) Resolve ambiguities and gaps in a vague scope before requirements. On brownfield, runs bootstrap when brownfield-map.md is missing; if map exists, human gate to refresh or keep. Use for incomplete scopes ("dashboard", "notifications", "integration with X") or before requirements when terms are unclear. Do NOT generate requirements.md — enriched context only.
Comprehensive guide for integrating Obsidian vaults as AI-powered second brains with Claude Code. Covers MCP integration, vault manifests, self-evolving patterns, auto-linking, and knowledge graph automation. Use when setting up Claude Code + Obsidian workflows, implementing bidirectional sync, creating CLAUDE.md manifests, or building self-healing knowledge systems.
Use when a consequential change needs a decision before coding: write or improve an RFC, design doc, architecture proposal, migration plan, option comparison, rollout plan, or measurable implementation contract. If the idea is still open-ended, use octocode-brainstorming first.
Use proactively when a task requires implementing, modifying, refactoring, or reviewing a product's frontend visible interface, interaction behavior, frontend state and data flow, component or style organization — no need for the user to name it. Also for testing and validation strategies for these frontend behaviors. Applies to pages, forms, lists, modals, responsiveness, styling and motion implementation, and frontend code ownership adjustments. Not for design judgments such as visual style, color scheme, typography, and design direction, nor for purely backend work, build and deployment, dependency upgrades, mechanical changes that only fix import paths, merely operating an existing website, only generating design images, or discussing this skill; not triggered when the user explicitly asks not to use it.
OpenClaw operations assistant. Use when the user mentions OpenClaw, 小龙虾, gateway, channel connections, failed message sending, unreachable services, log troubleshooting, or channel or Agent management. Prioritize status checks and fault triage; for high-impact operations such as restarting, repair, updates or configuration changes, explain them to the user before executing.
Cross-chain bridging, swapping, and bridge+call via Relay through the OpenFinance backend. Use whenever the user wants to move tokens across chains, swap EVM same-chain with a token change, or run a destination-chain tx funded from another chain. `recipient` may be the caller's own wallet OR any external address — Relay treats them the same. Routing rule — SAME-chain transfer with NO token change → `openfin-onchain` POST /agent/onchain/send (faster, cheaper than a bridge). Solana SAME-chain swap (SPL ↔ SPL / wSOL) → `openfin-onchain` onchain_jupiter_order + onchain_jupiter_execute (native SPL routing, better pricing than Relay). Everything else (EVM same-chain swap with token change, any cross-chain) → Relay. Triggers — "bridge X from Y to Z", "move USDC to Base / Arbitrum / Optimism / Polygon / Solana", "swap ETH for USDC on Base", "cross-chain swap", "bridge and call", "how do I get to / back from Solana", "my USDC is stuck on Solana", "send USDC to 0x… on another chain", EVM↔EVM, EVM↔Solana, Bitcoin bridge, gas topup, native-token sentinel `0x0`, intent status. Covers POST /agent/relay/quote, POST /agent/relay/execute, GET /agent/relay/status. Includes the chainId cheatsheet (1/137/8453/10/42161/… and Solana 792703809), tradeType (EXACT_INPUT / EXACT_OUTPUT / EXPECTED_OUTPUT), why topupGas auto-disables on Solana routes, bridge+call (`txs` array). When the user names a token by symbol (not address), run the pre-swap checklist in `openfin-onchain` (resolve via /token/search on the destination chain, DexScreener link, mcap, warn-on-thin, confirm). Pair with openfin-setup (API key) and openfin-troubleshooting (Blockhash not found, Custom:101, 412 setup-incomplete on Solana origin).
Use to streamline and optimize the AGENTS.md in the current code repository; not for ordinary coding, initialization, or global rule changes. Apply Prompt DSL compression principles, fill in missing coding guidelines, and preserve project facts and scope.
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
ORO GRAIL gold infrastructure for AI agents. Use when building agent integrations that involve: - Checking gold prices (via Pyth oracle) - Buying or selling gold (GRAIL tokens) - Managing user gold balances - Agent treasury/wealth features - Building fintech agents with gold savings, DCA, or rewards Based on Oro GRAIL API: https://docs.grail.oro.finance/
Plan and review Amazon Ads with margin-aware ACoS, product, and search-term guardrails. Use for Amazon advertising, Sponsored Products, Sponsored Brands, Sponsored Display, ASIN targeting, Amazon ACoS, or Amazon Ads performance exports.
Explain NotFair's paid-ads skills, installation, platform boundaries, account connections, and current product capabilities. Use for questions about how NotFair works, what it supports, how to install or connect it, plans or limits, or paid-media troubleshooting that is not an account-performance request.
Discover, connect, and verify NotFair paid-ad integrations and their actual capabilities. Use when asked to connect an ad account, configure an ads MCP, check available tools, troubleshoot access, or determine whether NotFair can read or change a platform.
Audit, diagnose, plan, and safely operate connected LinkedIn Ads accounts through the NotFair MCP, with an export-based fallback. Use for LinkedIn advertising, sponsored content, lead-generation forms, job-title or company targeting, campaign groups, creatives, conversions, lead quality, budgets, bids, or approved LinkedIn campaign changes.
Connect NotFair paid-ad accounts and establish reusable campaign context. Use when setting up paid media in a new workspace, connecting Google, Meta, X, LinkedIn, Reddit, or TikTok Ads, refreshing brand context, or preparing an agent to work on ads safely.
Payment gateway integration. Providers: SePay (Vietnamese: VietQR, bank transfer, cards), Polar (global SaaS: subscriptions, usage-based billing). SDKs: Node.js, PHP, Python, Go, Laravel, Next.js. Capabilities: checkout flows, subscription management, webhooks, QR code generation, benefit automation, tax compliance. Actions: integrate, implement, configure, handle payments/subscriptions/webhooks. Keywords: payment gateway, SePay, Polar, VietQR, bank transfer, subscription, usage-based billing, checkout, webhook, QR code, API key, OAuth2, product management, customer portal, tax compliance, MoR, recurring payment, invoice. Use when: integrating payment processing, implementing checkout, managing subscriptions, handling payment webhooks, generating payment QR codes, building billing systems.
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see lp-optimizer) — this skill focuses on in-product upgrade moments where the user has already experienced value.
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.