Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Draft and fill NDA contract templates — mutual NDA, one-way NDA, confidentiality agreement. Produces signable DOCX files from Common Paper and Bonterms standard forms. Use when user says "NDA," "non-disclosure agreement," "confidentiality contract," "confidentiality agreement," "mutual NDA," or "one-way NDA." Includes lawyer-reviewed practice guides; see openagreements.org/editors.
NetBox server administration: configuration, authentication backends (local/LDAP/SAML/OIDC), object permissions, API tokens, performance tuning, backups, upgrades, and housekeeping. Use when managing a NetBox instance rather than consuming its API.
Methodology for migrating data into NetBox from spreadsheets, legacy IPAM/DCIM systems, CMDBs, and unstructured sources. Use when planning or executing a data migration — covers assessment, cleaning, dependency ordering, import strategy selection, validation, and post-migration verification with Discovery and Assurance.
When the user wants to forecast using deep learning, LSTMs, transformers, or neural networks. Also use when the user mentions "neural network forecasting," "LSTM," "GRU," "transformer forecasting," "attention mechanisms," "seq2seq," "temporal convolution," "deep learning time series," or complex non-linear patterns. For traditional forecasting, see demand-forecasting. For general ML, see ml-supply-chain.
Require `neverthrow`-based return types in TypeScript and JavaScript code whenever the surrounding technology allows it. Use when creating, refactoring, reviewing, or extending standalone functions, exported module functions, class methods, object methods, service methods, repository methods, and similar APIs that should expose explicit success and failure result types in their signatures. Prefer `Result<T, E>` for synchronous code and `ResultAsync<T, E>` for asynchronous code. Only skip a `neverthrow` return type when a framework, library, runtime interface, or externally imposed contract is incompatible and requires a different return shape.
Use for Next.js 16 Cache Components and runtime rendering work involving `use cache`, `cacheLife`, `cacheTag`, `updateTag`, Suspense, runtime APIs, Partial Prerendering, remote cache, metadata/viewport runtime access, or migration from older route segment caching configs.
React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.
Install and compose Nexus UI components for AI chat UIs — prompt input, model selector, suggestions, attachments, message, thread, citation, reasoning, text shimmer, image, feedback bar, toaster, chain of thought, tool, questions, and AI SDK patterns. Activates for @nexus-ui registry usage or Nexus UI source under components/nexus-ui.
A skill for writing server-side APIs with the Nitro v3 framework and H3. Use for initialising backend-only Nitro projects, adding full-stack capabilities to Vite projects, writing spec-compliant CRUD endpoints, and database interaction with Drizzle ORM. Use this skill when developing new Nitro endpoints, initialising Nitro configuration, or consulting Nitro development conventions.
Remove code comments that explain or defend Remotion's own code, keeping only comments about external systems we cannot change (browser quirks, codec/FFmpeg behavior, third-party APIs, OS or platform bugs). Use when the user invokes /no-comments or asks to strip unnecessary comments from a diff or files.
Single-directory install package for web fiction writing. Users only need to install and invoke /novel-assistant to be automatically routed to internal capabilities such as long-form writing, short-form writing, ranking scans, story breakdown, AI-style removal, covers, import, review, and project deployment. Suited to Codex, Claude Code, OpenClaw/qclaw and similar setups where only one skill directory should be installed; long-form writing enables a stability control loop by default; only novel-assistant is kept under the repository's top-level skills.
Documents the `npx skills` CLI for installing and updating agent skills, plus the project-level `skills-lock.json` lockfile. On start, detects a `skills-lock.json` without installed skills under `.claude/skills/` and proposes restoring them via `npx skills add … --copy -y` per the source recorded in the lockfile.
(NS) Create and maintain PHPUnit unit and integration tests in the backend package (bootstrap tests/ when missing). Mandatory Docker-only execution with phpunit --testdox --stop-on-failure --stop-on-error and 120s timeout. Use when writing or refactoring PHPUnit tests, implementing unit-test tasks, or scaffolding backend tests on greenfield Laravel/PHP projects — not when planning test task markdown (use ns-pm-unit-test-task-generator). Read harness backend-tests rules when present.
(NS) Security/compat/a11y hygiene + Vercel Web Interface Guidelines review (headers, CSP, deps, accessibility). Use when hardening security, fixing CSP/CORS/headers, reviewing UI / checking a11y / auditing UX, or applying Web Interface Guidelines — even without saying "best practices"; also at ns-proto-creator close-out. Do NOT use for MR/SOLID review (ns-code-reviewer), visual redesign (ns-code-frontend-design), or feature implementation (ns-code-coder / ns-spec-driven).
(NS) Write and edit human-facing project documentation — README, docs/ guides, runbooks, and contributor-facing markdown. Use whenever the user asks for documentation, README updates, how-to guides, or docs/ content — even if they say "explain how to use" instead of "write docs". Stack-agnostic; follow project layout from AGENTS.md. Do NOT use for code comments, API docblocks in source, requirements.md, or SDD version artifacts (use PM skills).
(NS) Create and maintain Cypress E2E tests in an independent tests-e2e/ Node package at product root (bootstrap when missing). DRY device-aware command architecture (shared/pages/device). Use when writing or refactoring Cypress specs, custom commands, scaffolding E2E on greenfield projects, or implementing E2E tasks — not when planning E2E task markdown (use ns-pm-e2e-test-task-generator). Read harness e2e rules when present. Mandatory discovery before writing specs.
(NS) Distinctive production UI — layout, typography, motion, and component polish that avoids generic AI-slop aesthetics. Use whenever the user builds or refines pages, components, dashboards, forms, or design-brief work, or asks for better UI/UX — even if they do not say "design". Load docs/context/design-brief.md when present. Do NOT use for backend-only work, requirements writing, or full SDD orchestration (use ns-spec-driven).
(NS) Root-cause diagnosis from errors, logs, stack traces, failing tests, or CI — entry priority 4 when the user wants diagnosis WITHOUT implement ("why does X break?"). Use proactively on unclear test/CI failures if they have not asked to fix yet. Do NOT use for implement/fix (ns-code-coder), version scope (ns-spec-driven), GitLab ISSUE_URL execution, or pre-merge review (ns-code-reviewer).
Integrate with Octav API for cryptocurrency portfolio tracking, transaction history, and DeFi analytics across 50+ blockchain networks. Use when building applications that need to: (1) Track wallet balances and net worth across multiple chains, (2) Query transaction history with filtering and search, (3) Monitor DeFi protocol positions (Aave, Uniswap, etc.), (4) Access historical portfolio snapshots, (5) Analyze token distribution and holdings, (6) Pay per request as an autonomous agent via x402. Triggers on: "Octav API", "crypto portfolio API", "blockchain portfolio tracking", "DeFi analytics API", "wallet balance API", "transaction history API", "multi-chain portfolio", "Octav x402".
Use when the user asks to "plan & implement", "plan this work", "research & build", "plan auth/API/work", or needs a multi-step pipeline from understanding through implementation. Flow is Understand → Research → Plan → Implement → Verify. For design documents or technical proposals without implementation, use octocode-rfc-generator instead.
Open Graph and social sharing image design with platform specs, text placement, and branding. Covers OG meta tags, Twitter cards, LinkedIn previews, and dynamic generation. Use for: social sharing images, blog thumbnails, link previews, social cards. Triggers: og image, open graph, social sharing image, twitter card, social card, link preview image, og meta, sharing preview, social thumbnail, meta image, og:image, twitter:image, linkedin preview
Run and interpret the OnionCry Rust CLI for architecture-boundary checks in JavaScript and TypeScript repositories. Use when the user asks to check architecture boundaries, generate or review .onioncryrc.jsonc, run onioncry check or explain, adopt a violation baseline, inspect llm-mode reports, render boundary graphs, add repo/package scripts, or automate OnionCry in agent workflows. Do NOT use for generic Rust implementation work.
A chemical toolbox designed to speak the many languages of chemical data. Supports over 110 formats and provides tools for conversion, 3D structure generation, molecular searching (SMARTS), and force field calculations. Use for chemical file format conversion (SDF, PDB, SMILES, CIF, Gaussian), 3D coordinate generation from 2D structures, substructure searching with SMARTS patterns, molecular docking preparation, force field minimizations (UFF, GAFF, MMFF94), molecular fingerprints and Tanimoto coefficients, and batch processing of chemical databases.
Inter-instance communication for OpenClaw. Use this skill when you need to pass messages, sync data, or execute commands remotely between multiple OpenClaw instances. Covers agent-to-agent messages, nodes.run remote execution, file-level communication and more.
This skill should be used when the user mentions "openclaw", "OpenClaw CLI", asks to "send a message via openclaw", "manage openclaw agents", "configure openclaw gateway", "check openclaw status", "run openclaw agent", or asks about OpenClaw setup, channels, devices, or messaging automation.
Powerful web scraping, crawling, and data extraction with stealth anti-bot bypass (Cloudflare Turnstile, CAPTCHAs). Use when: (1) scraping websites that block normal requests, (2) extracting structured data from web pages, (3) crawling multiple pages with concurrency, (4) taking screenshots of web pages, (5) extracting links, (6) any web scraping task that needs stealth/anti-detection, (7) user asks to scrape/crawl/extract from URLs, (8) need to bypass Cloudflare or other bot protection. Supports CSS/XPath selectors, adaptive element tracking (survives site redesigns), multi-session spiders, pause/resume crawls, proxy rotation, and async operations. Powered by MyClaw.ai.
Create parametric OpenSCAD 3D models of workshop tools (drill presses, vacuums, saws, etc.) for workshop layout planning. Use when asked to "model a tool", "create OpenSCAD for [tool]", "add [tool] to workshop", or when planning workshop layouts that need tool representations. Supports brand-accurate colors (Bosch, Festool, Makita, DeWalt, Milwaukee) and standardized code structure with customizer parameters.
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.
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.
Content Packaging Workshop — the final step in the writing series. Handles the presentation layer after content is finalized: title polishing, opening hooks, layout optimization, punctuation cleanup (integrates with zan-punct-fix), image suggestions, platform adaptation. Does not change the body content. Six modules can each be triggered independently. Triggers: help me polish the title, this title isn't good enough, how to write the opening, check the layout for me, paragraphs are too dense, punctuation check, review the images, which platform does this article suit, going to publish — run through the packaging, check if there are presentation problems, the content is fine but tiring to read, do a pre-publish check for me. EN: "polish the title", "fix the opening hook", "check layout", "fix punctuation", "review images", "platform formatting", "pre-publish checklist". Not for: body content rewriting (→ humanize-ai / editor-revisor), content quality diagnosis (→ chinese-write-checker), voice calibration (→ voice-dissolver).
When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
Brainstorm a research idea and decide what a new paper should cover — generate candidate framings, pick the central contribution, and draw the in-scope vs. deferred boundary. Use whenever the user has a rough interest, preliminary results, or a problem and asks "what should this paper be about", "help me brainstorm an idea", "what should I include / cover", "is this one paper or two", "help me scope this", "what's the contribution here", or "I have an idea but don't know how to frame it". Default to running this upstream of research-idea-stress-test (which vets one chosen idea) and paper-argument-planner (which structures a paper once the contribution is fixed). Always check first whether the input is sufficient (a seed, the field, the motivation); if not, request the missing context before brainstorming rather than inventing a direction. Hands off per-claim evidence to benchmark-and-baseline-selector, novelty grounding to literature-triangulation, and section logic to paper-argument-planner.
When the user is choosing partners, investing in a management team, or assessing whether to build a long-term relationship with a person or organization. Language signals: "how is this management team" / "should I work with this person" / "which of two opportunities should I pick" / "how do I verify trust." Not applicable to: purely transactional decisions that do not require evaluating a long-term relationship.
End-to-end hotel booking with USDC wallet payment. Use when the user wants the agent to search, book, and pay for a hotel in one autonomous flow — phrases like "book me a hotel in Tokyo and pay with USDC", "find a place in Paris and pay from my wallet", "handle the whole booking for next week". Orchestrates: search → select → authenticate wallet → fund if needed → pay via x402 → confirm. Do NOT use for search-only, payment-only, or non-hotel bookings.
Load PROACTIVELY when task involves payments, billing, or subscriptions. Use when user says "add payments", "integrate Stripe", "set up subscriptions", "add a checkout flow", or "handle billing webhooks". Covers Stripe, LemonSqueezy, and Paddle integration, checkout sessions, subscription lifecycle management, webhook verification and handling, customer portal, metered billing, refunds, and PCI compliance considerations.
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 page-cro) — 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.