Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Build and maintain Dexie.js data layers for IndexedDB-backed offline-first web applications. Use when tasks involve Dexie setup, schema/index design, CRUD/query implementation, transactions, live queries, migrations, or debugging in Vanilla JS, React, Next.js, TanStack Start, Svelte, or SvelteKit.
Automatically discover software engineering practice skills when working with code review, documentation, pair programming, production debugging, performance profiling, deployment strategies, or software engineering practices. Activates for engineering development tasks.
Extracts design data from Figma via the REST API and converts designs to React code. Use when syncing Figma tokens to CSS variables, exporting icons as SVG components, generating code from Figma designs, or automating design-to-code workflows. Use for design token extraction, icon export, component generation, and CI-based Figma sync.
Use when building, editing, or reviewing Vue 3 UI with Flux (by Bas Milius): @flux-ui/components (docs at flux-ui.dev) and its siblings @flux-ui/application (app shell / dashboards) and @flux-ui/statistics (KPIs/charts). Trigger on Flux-prefixed components (FluxPrimaryButton, FluxFormField, FluxPane), on FluxRoot / showConfirm / showSnackbar / showPrompt / showAlert, on its composables (useBreakpoints, useFluxStore, use*Injection), or any import from @flux-ui/*. This is the Vue 3 Flux (basmilius), NOT the Livewire/Blade Flux from fluxui.dev and NOT the Flux web-components library; never mix their syntaxes.
Use when debugging or preventing errors in Frappe Server Scripts. Prevents ImportError (the #1 error), NameError for restricted builtins, sandbox violations, doc_events not firing, wrong script type selection, SQL injection, permission denied in scheduled scripts, infinite loops, and API scripts not returning JSON. Covers error message mapping table. Keywords: server script error, ImportError, NameError, sandbox, restricted, ImportError in server script, script not running, sandbox error, restricted function, frappe.throw, doc_events, scheduler, API script, SQL injection.
Use when implementing server-side features via Setup > Server Script: document validation, auto-fill, API endpoints, scheduled tasks, permission queries. Covers sandbox-safe coding, script type selection, testing, migration to controllers. Keywords: how to implement server script, which script type, sandbox limitation, Document Event, API script, Scheduler Event, Permission Query, migrate to controller, no-code automation, run code on save, auto-fill field, server-side validation, scheduled script.
Use when creating or customizing Workspace pages in Frappe v14-v16. Covers Workspace DocType structure, shortcuts, number cards, dashboard charts, custom HTML blocks, JSON content format, shipping workspaces with custom apps, and role-based access control. Prevents common mistakes with content/child-table desync and missing fixtures. Keywords: workspace, desk, dashboard, number card, chart, shortcut, customize desk, dashboard setup, add shortcut, module page, sidebar customize, workspace builder, module, fixtures, sidebar.
Use when configuring scheduler events and background jobs in Frappe/ERPNext v14/v15/v16. Covers scheduler_events in hooks.py, frappe.enqueue() for async jobs, queue configuration, job deduplication, error handling, and monitoring. Keywords: scheduler, background job, cron, RQ worker, job queue, async task, frappe.enqueue, scheduled task, cron syntax, how often does it run, background job example, enqueue example.
Integrate Freemius monetization into a JavaScript/TypeScript backend — entitlement table, server-side checkout creation, purchase processing, and webhook license-lifecycle sync. Use when adding subscriptions, licensing, paywalls, or "unlock premium feature" gating to a SaaS/App/Web app whose backend is JS/TS (Hono, Express, Next.js, Fastify, serverless Fetch handlers). Covers the Freemius JS SDK (`@freemius/sdk`), not the frontend Checkout SDK.
Use when Codex is building, revising, or reviewing a frontend UI, web app screen, responsive layout, component surface, dashboard view, form flow, visual system, or no-template product interface that needs visual polish, accessibility, screenshots, or browser QA.
Git worktree management with tmux and iTerm2 integration. Use when creating isolated dev environments, managing parallel feature branches, switching contexts without stashing, or running multiple Claude instances. Covers worktree creation, tmux window management, iTerm2 tabs, and cleanup workflows.
Manage project milestones including create, list, update, view, and close operations. Use when planning releases, tracking milestone progress, or organizing issues/MRs by milestone. Triggers on milestone, release planning, milestone progress, version milestone.
Comprehensive code review checklist for Go projects. Evaluates code quality, idiomatic patterns, error handling, naming, package structure, and test coverage. Use when reviewing Go code, PRs, or before merging changes. Trigger examples: "review this code", "check this PR", "code review", "review Go file". Do NOT use for security-specific audits (use go-security-audit) or performance-specific analysis (use go-performance-review).
GoldRush Streaming API — real-time blockchain data via GraphQL subscriptions over WebSocket. Use this skill whenever the user needs live price feeds (OHLCV candles), real-time DEX pair monitoring (new pairs, liquidity updates), wallet activity streaming, decoded swap/transfer events, token search, trader PnL analysis, or any sub-second latency blockchain event push. This is the right skill for trading bots, live dashboards, alerting systems, copy-trading, DEX sniping, and real-time analytics. Also covers one-time GraphQL queries for token discovery and profitability analysis. If the user needs historical data, batch queries, or paginated REST results, use goldrush-foundational-api instead. If the user needs pay-per-request access without an API key, use goldrush-x402 instead.
Entry skill for the Headless Ghidra YAML-first reverse-engineering pipeline. Use when the user asks to analyze, decompile, triage, resume, or iterate on a binary target with Ghidra/headless-ghidra. Reads artifacts/<target>/pipeline-state.yaml, routes P0–P4 phase skills, runs gate checks, and manages review pauses. Performs zero analysis work itself.
Use when the project follows hexagonal (ports & adapters) architecture. Prevents domain code from depending on Spring or JPA. Use when you see packages like domain/, application/, infrastructure/, or adapters/ in the project structure.
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Unified GPU kernel operator generation and optimization skill. Automatically detects the target repository type (FlagGems, vLLM, or general Python/Triton) and dispatches to the appropriate specialized sub-skill. Includes operator generation, MCP-based iterative optimization, and feedback submission sub-skills. Use this skill when the user wants to generate or optimize a GPU kernel operator, create a Triton kernel, or says things like "generate an operator", "create a kernel for X", "optimize triton kernel", or "/kernelgen-flagos".
Use when the project follows API-first / OpenAPI-first approach: generating controller interfaces, DTOs, and clients from an OpenAPI spec. Use when you see openapi.yaml, openapi-generator-maven-plugin, or ApiDelegate pattern in the project.
Build OpenTelemetry collector configs, instrument services, transform telemetry with OTTL, and debug missing traces, metrics, or logs. Use for OTel/otelcol collector config, OTLP export, SDK instrumentation, sampling, cardinality, TLS/PII controls, Kubernetes/Helm values.yaml deployments, collector health and alerts, and AI coding-agent telemetry (Claude Code, Codex, Gemini CLI, Antigravity, GitHub Copilot, Cursor).
Add Opik tracing to an existing app and verify a real trace lands. Installs the Opik package, detects the language and LLM framework, adds the minimum tracing, runs a safe representative path, confirms a trace in Opik, and returns the trace link. Use for “instrument my code”, “add opik tracing”, “add observability”, “trace my agent”. Not for building a new app from scratch, or a review-only pass with no code changes.
Run a structured quality audit on a product spec, PRD, or requirements document. Produces a severity-rated issue list with concrete fixes—catches untestable requirements, happy-path-only flows, missing scope exclusions, absent dependencies/constraints/assumptions, implementation details leaking into functional specs, and unvalidated assumptions presented as facts. Use when reviewing a spec, PRD, or requirements doc, or as the validation step after writing one.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
General guidelines for building a robust webhook receiver/handler: verifying signatures, raw-body access, replay protection, async processing, retries and endpoint auto-disabling. Use whenever you write, review, or debug a handler that consumes incoming webhooks from any provider.
Use when reviewing/judging a published, consumer-facing API reference an integrating developer calls an API from — deciding if they can integrate from it. A gate, not authoring. Judges against a single-sourced 11-condition usability + contract-consistency bar: getting-started + auth reach a first call; every api-spec operation (incl. events/webhooks) is documented with purpose + typed params + a worked example + errors; errors first-class; rate-limits + pagination documented where applicable; versioning + deprecation/sunset stated; the reference is CONSISTENT WITH THE HANDED-IN api-spec (no drift, no fabricated endpoint — the load-bearing check); samples runnable; an amendment re-syncs to the changed contract. Emits exactly `VERDICT: approve|revise` plus actionable findings; approves a proportionally-sized reference, revises on a named gap. Not authoring it, not the end-user user-guide, not the developer-adoption guide, not the engineering api-spec (reviewing-api-spec).
Use when reviewing or judging a finished or amended developer guide — the adoption + integration narrative for a developer-tool product (SDK/library/CLI/framework/API platform). Decides whether a developer can install, integrate, and operate the tool from the guide alone. A gate, not authoring. Judges it against a single-sourced 14-condition adoptability + accuracy bar: a signposted start-here + a verifiable first success; concepts before recipes; how-tos cover the handed-in scenarios; samples runnable + accurate to the CURRENT tool (no fabricated/stale endpoints); LINKS INTO the api-reference, never duplicates it; Diataxis modes typed; a troubleshooting path; an amend reviewed delta-scoped. Emits exactly `VERDICT: approve|revise` + actionable findings; approves a guide meeting the bar (no false-revise on a thin one), revises only on a named gap. Not for authoring it, the end-user user-guide, the endpoint catalog (api-reference review), or engineering design docs (design-review).
Build integrations with Rocket.net's WordPress hosting API. Manage sites, domains, backups, plugins, themes, CDN cache, FTP accounts, and more programmatically. Use when: building WordPress hosting management tools, automating site deployment, creating reseller portals, managing multiple WordPress sites, integrating with Rocket.net hosting services, automating backup workflows, or building custom control panels.
Use when connecting an application to a published Runway app Workflow through the Dev API, or when maintaining an existing Workflow invocation. Use live setup guidance when project-specific connection details are needed; do not infer unpublished workflow behavior.
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows
Edit shipyard's config.toml, the macOS menu bar app listing pull requests, issues and workflow runs. Use when asked to change my shipyard or the shipyard app (its layout, theme, projects, notifications, what it shows): watch or group repositories, show or hide issues, runs, drafts or someone's items, switch the menu between a list and tabs, pick or write a theme, change when it notifies, show pings from my other machines, or fix its configuration file. Also use to ping me through shipyard with the `shipyard ping` command, from my Mac or another machine running Herdr: when a PR is ready, when you need my input, or to bring me back to this pane. Use `shipyard notice send` from any of my machines to post a status notice (tests running, done) that needs nothing from me. And use to open, quit, steer or screenshot the shipyard app on my Mac with `shipyard app` and `panel`, on my data or a demo's. And use for my notes, kept in Notion per shipyard project: to take a note I dictate, find one by its number, or list, tidy or archive them.
Use when you need to initialize a new Spec Pack in this repository's AI SDLC process (creating a three-digit numbered branch and the `.aisdlc/specs/{num}-{short-name}` directory), or when running `spec-init` and unsure about input parsing, short-name rules, passing UTF-8 BOM file paths, script invocation, or outputs.
Use when you need to complete R1 (raw→solution) requirements clarification on the sdlc-dev spec branch but see pressure signals such as pushing to skip clarification or skip gates, demanding to "ask everything at once", or asking you to jump straight to a next-step routing conclusion.
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.