Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Official Rails documentation. Use when asked about any Rails-specific topic including ActiveRecord, routing, controllers, views, mailers, jobs, Action Cable, Action Text, Active Storage, migrations, validations, callbacks, associations, caching, security, or internals.
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.
Assemble several separate screen recordings, each likely covering a different sub-topic, possibly made at different times and inconsistent in style or quality, into one structured, cohesive training module. This is a stitching skill: many separate pieces going in, one module coming out. The craft is in the assembly (consistent framing, matched audio, connective transitions, a real throughline), not in discovering files or guessing their order. Use when the user says "assemble these recordings into one training module", "stitch these screen recordings into a cohesive course", "combine these separate videos into one structured module", or "turn this batch of recordings into a single training video".
Surgically update a stale video after a UI or feature change - replace only the outdated sections with new material and patch only the narration lines that mention old names or flows, leaving everything else untouched. Use when the user says "this video shows the old UI", "update this video, the feature got renamed", "refresh this outdated tutorial", "the flow changed, fix the video", or "patch this video without redoing it".
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
Plan, conduct, evaluate, and synthesize rigorous research investigations with credible evidence and a traceable method, including source-to-claim closure for media evidence. Do not use this skill for repeated source extraction and durable note orchestration; use `research-and-vault` for that capture workflow, or `ffmpeg` for media operations.
Run a comprehensive multi-perspective code review on current changes. Activates the Review Council (security, quality, documentation, domain review) and runs automated security scanning. Use before creating a pull request or when you want a thorough review of your work.
Use when reviewing/judging a release runbook (the go-to-production procedure for shipping a system to production) — deciding whether an unfamiliar engineer can execute, verify, and roll back from it alone. A gate, not authoring. Judges a single-sourced 11-condition executability + safety bar: every step copy-paste-safe + idempotent with an expected result; a go/no-go gate; a complete rollback (a revert per forward change, measurable triggers, roll-forward if irreversible); post-deploy verification reusing the test-plan criteria; escalation + monitoring; NO secret inlined (an embedded token/key is a finding); stateful-change safety (proportional); a comms window for a user-impacting deploy (proportional); commands spot-checked against the upstreams; nothing fabricated; a delta-scoped amend. Emits `VERDICT: approve|revise` + actionable findings; approves a runbook meeting the bar (no false-revise), revises on a named gap. Not authoring it, not the QA test-plan, not engineering design docs (design-review).
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
Revolut X market data commands. Use when the user asks to “check crypto prices”, “view candles”, “get ticker”, “see order book”, “list currencies”, “list trading pairs”, “fee tiers”, “my fees”, “trading fees”, “maker fee”, “taker fee”, or runs revx market commands
Apply Robi's UI design principles for beautiful, accessible interfaces. Use when building UI components, reviewing designs, choosing colors, setting spacing, or implementing animations. Covers color theory (HSL, WCAG, halation), spacing (4px system), icons, shadows, and micro-interactions.
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.
Deploy GPU workloads to RunPod serverless and pods - vLLM endpoints, A100/H100 setup, scale-to-zero, cost optimization. Use when: deploy to RunPod, GPU serverless, vLLM endpoint, scale to zero, A100 deployment, H100 setup, serverless handler, GPU cost optimization.
Pre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.
Best-practices reference for the ScraperAPI Java SDK (com.scraperapi:sdk Maven artifact). Consult whenever the user is writing, debugging, or reviewing Java code that calls ScraperAPI. Use when user asks: "scrape a website with Java and ScraperAPI", "ScraperAPI Java example", "how do I add ScraperAPI to my Maven project", "Java ScraperAPI render", "ScraperAPI Java fluent API", "ScraperAPI Java premium proxy", "ScraperAPI Java error handling", "ScraperAPI Java retry". Covers Maven/Gradle setup, the fluent builder API, all request parameters, the escalation ladder, async jobs, structured data calls, error handling, and credit costs. Note: Transmits user-supplied queries, URLs, and content to ScraperAPI.
Best-practices reference for the ScraperAPI PHP SDK (scraperapi/sdk Composer package). Consult whenever the user is writing, debugging, or reviewing PHP code that calls ScraperAPI. Use when user asks: "scrape a website with PHP and ScraperAPI", "ScraperAPI PHP example", "how do I use the ScraperAPI PHP SDK", "PHP ScraperAPI render", "ScraperAPI PHP premium proxy", "ScraperAPI PHP Composer install", "ScraperAPI PHP error handling". Covers Composer setup, all request parameters, the escalation ladder, POST requests, error handling, and credit costs. Note: Transmits user-supplied queries, URLs, and content to ScraperAPI.
DevSecOps, secure software development lifecycle (SSDLC), and application security (AppSec) practices covering secret handling, input validation, dependency hygiene, authentication/authorization, and CI/CD security tooling (SAST, SCA, DAST, secret scanning, IaC scanning). Use when writing code that handles credentials, user input, database queries, or authentication, when setting up a CI/CD pipeline, or when reviewing code or infrastructure for security issues.
Systematically identifies vulnerabilities, threats, and mitigations for systems handling sensitive data using STRIDE methodology, trust boundary mapping, and defense-in-depth principles. Use when designing or reviewing systems with PII/PHI/financial/auth data, building security-sensitive features (auth, payments, file uploads, APIs), preparing for audits or compliance (PCI, HIPAA, SOC 2), investigating incidents, or integrating third-party services. Use when user mentions threat model, STRIDE, trust boundaries, attack surface, or security review.
Comprehensive Claude Code self-assessment and learning path advisor. Runs a multi-category quiz covering 10 feature areas, produces a detailed skill profile with per-topic scores, identifies specific gaps, and generates a personalized learning path with prioritized next steps. Use when asked to "assess my level", "take the quiz", "find my level", "where should I start", "what should I learn next", "check my skills", "skill check", or "level up".
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
Analyse the current Google top 10 for one keyword — keyword metrics, search intent, SERP features, the winning content format, and the gap the user can realistically win. Use when the user asks what ranks for a keyword, what the SERP looks like, which format to write, or why competitors outrank them
Sends MMS multimedia messages (images, video, audio, PDFs, vCards) via the MMS channel of the Sinch Conversation API. Available in the United States, Canada, and Australia only. Covers supported media types, file size limits, MMS channel properties, and transcoding behavior. Use when sending an MMS or picture message, sending media to US/CA/AU numbers over MMS, or debugging MMS media rejection and size issues.
Replace hard cuts in an existing video with consistent, subtle transitions at every scene boundary, matched to the video's tone. Use when the user says "smooth out the cuts", "add transitions between sections", "the jumps between scenes feel abrupt", "make the scene changes less jarring", or "do a transitions pass".
Use when you need to turn supplied social performance data into a decision about what to keep, test, change, or stop. Trigger phrases include "report on this campaign", "what worked on social?", "analyse these post results", "make a weekly social report", and "what should we do next from these metrics?". Do not use this to invent data access, claim causation from a dashboard, or replace a campaign brief; use campaign-brief to define success before launch and launch-retrospective for the broader after-action review.
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.
Use when the user is working with — or migrating away from — the legacy Spree Platform/Storefront API v2 (JSON:API-style under `/api/v2/`). Triggers on "API v2", "JSON:API", "Platform API", "Storefront API", "v2 to v3 migration", "JSON:API attributes/relationships", "X-Spree-Order-Token", "Bearer token API v2". The default stance is **don't build new things on v2** — point users to the v3 equivalents (spree-api-v3 skill). Use this skill only to (a) maintain existing v2 integrations or (b) migrate to v3.
Studies exemplar papers from a target venue and produces an original style-and-structure brief — fetches best-paper awardees and top-cited papers on demand (DBLP, Semantic Scholar, Unpaywall, arXiv, open-access ACM DL) and analyzes section architecture, contribution framing, evaluation patterns, and figure/table conventions. Use when the user wants to study best papers or award-winning papers at a venue, find the most-cited papers and how they are structured, learn how successful papers at a conference are written ("what do winning SIGSPATIAL papers look like", "analyze NeurIPS best papers before I draft"), or model a draft on a venue's strongest work. Copyright-safe by design - papers are fetched from legal open-access sources and processed transiently, never bundled, stored, or committed; the output is metadata plus original analysis. Trigger words - exemplar, best paper, award-winning, most cited, top cited, model paper, venue style, paper structure.
Use when writing or debugging Vue code that imports @tanstack/ai-vue. Covers useChat, createChatHook, the generation composables (image, audio, speech, video, transcription, summarize), useAudioRecorder, useByok, useWebMCPTools, and the @tanstack/ai-vue/ui and /byok subpaths. Provides current API shapes, reactive-state rules, and version limits for @tanstack/ai-vue 0.24.x.
TanStack Store for framework-agnostic reactive state management with derived state and batching. Use when managing shared state, creating derived computations, or building framework-agnostic state logic. Use for tanstack-store, store, state, derived, batch, subscribe, reactive-state.
Run or route a coordinated multi-agent team workflow for Codex/OMX. Use when the user explicitly invokes `$team`, asks for team mode, coordinated workers, tmux workers, or multiple agents sharing a task list. Prefer `omx team` when the runtime is installed; use `ultrawork` instead for independent parallel lanes that do not need shared state.
Generate optimized titles, headlines, and subject lines for any content type. Use when asked to create a title, headline, subject line, or when the user says "title ideas", "what should I call this", "subject line options", or needs engagement-optimized naming for videos, newsletters, or social posts.
Amazon public market intelligence via unified host MCP `topview-mcp` (progressive disclosure: use_amazon_data → get_tool_schema → call_tool). Use when: Amazon market/category research, ASIN/product screening, competitor lookup, listing/keyword/traffic analysis, review VOC, trend or trademark risk checks, SellerSprite-style public Amazon data. NOT for: TikTok Shop, Shopee, YouTube creator pool, or video/image/avatar generation (use topview-tiktok-shop-ops, topview-shopee-ops, topview-youtube-kol-ops, or topview-generate).
Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
Remove silences, loading screens, and hesitation gaps from a video so it keeps moving, with a light, standard, or tight aggressiveness setting. Use when the user says "trim the dead air", "cut the silences", "there's too much waiting around", "remove the loading screens", "make it feel faster without changing anything", or shares a recording full of pauses and idle screens.
Design, build, redesign, review, and debug terminal user interfaces (TUIs). Use when the user wants to build, polish, or review a terminal app; mentions "TUI", "terminal UI", "terminal user interface", Bubble Tea, Textual, Ratatui, or Ink; asks to convert a CLI into an interactive TUI; requests TUI layouts, keybindings, or components; needs Unicode, wide-character, emoji, or RTL/Arabic/Hebrew text handling; wants terminal compatibility checks or TUI tests (snapshot, golden, interaction); or needs to troubleshoot terminal rendering.
Design and implement retro/cyberpunk/hacker-style terminal UIs. Covers React (Tuimorphic), SwiftUI (Metal shaders), and CSS approaches. Use when creating terminal aesthetics, CRT effects, neon glow, scanlines, phosphor green displays, or retro-futuristic interfaces.
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.