Skills
97,501 packaged capabilities and playbooks for agents. Install any of them with one command.
All
All-in-one Redis expertise covering data modeling and key naming, client connections (pooling, pipelining, client-side caching, timeouts), clustering and replication, Redis Search (FT.CREATE, vector and hybrid search, RAG pipelines), observability and incident triage, production security hardening, semantic caching for LLM responses via LangCache, and agent memory via Redis Iris (session events, long-term memory, background promotion). Use whenever designing, writing, reviewing, or debugging anything that touches Redis: choosing a data structure, naming keys, configuring a client, sharding across a cluster, building or tuning a search index, monitoring or diagnosing performance, hardening a deployment, caching LLM completions, or wiring persistent memory for an AI agent, merged into one skill so the right domain loads automatically without picking between separate ones.
Client-facing red-team deliverable format — codifies the Subject / Observations / Description / Impact / Recommendation / PoC structure used for external red-team engagements (not bug-bounty platform reports). Different audience, different tone, different cadence. Built from an authorized engagement deliverable where 14 findings were packaged into a 52KB MD + 2.2MB DOCX with 16 embedded screenshots. Use when the engagement is "external red team for an enterprise client" (not H1/Bugcrowd/Intigriti), when generating the final report, when the client has specified a custom report format, or when packaging findings into DOCX/PDF.
Use when changing existing structure without changing behavior, adding characterization tests, isolating hard dependencies, consolidating APIs, migrating callers, introducing value objects or domain events, replacing null/string/generic exceptions with typed failure contracts, or removing legacy paths safely. Applies to protected incremental change, not an unverified rewrite or unrelated cleanup.
Builds compliance checklists for business scenarios involving GDPR, PIPL, or advertising/data laws. Outputs a structured checklist with check items, legal basis, risk levels, and actionable recommendations. Triggered by requests like "run a compliance check," "GDPR/PIPL compliance," "pre-launch review," "privacy impact assessment (PIA/DPIA)," or asking if a feature is compliant.
Remix v2 data loading and mutations. Use when writing loaders, actions, deferred data, revalidation logic, or pending state. Triggers on loader, action, useLoaderData, useActionData, json(), defer(), <Await>, shouldRevalidate, useRevalidator, useNavigation, useTransition (v1 holdover).
Reviews Remix v2 error-handling code for the unified ErrorBoundary, isRouteErrorResponse narrowing, throw-vs-return, root boundary scaffolding, and v1 holdovers (CatchBoundary, useCatch). Use when reviewing routes that throw or define ErrorBoundary in a Remix v2 codebase.
Remix v2 form submissions and mutations. Use when implementing forms, optimistic UI, file uploads, or multi-action routes. Triggers on <Form>, useFetcher, useSubmit, useNavigation for pending state, unstable_parseMultipartFormData, fetcher.formData, intent-based actions, encType multipart.
Reviews Remix v2 form code for manual fetch() mutations, native <form> misuse, wrong useNavigation/useFetcher choice, missing pending state, unbounded uploads, and intent-pattern violations. Use when reviewing form/mutation code in a Remix v2 codebase.
Reviews Remix v2 code for v1-shape meta exports (BREAKING in v2), cookie security gaps (httpOnly, secure, secrets rotation), auth gates in wrong layer, and missing CSRF. Use when reviewing meta/SEO, session, auth, or form-mutation code in a Remix v2 codebase.
Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets. Triggered when users ask about Git analysis, code hotspots, who owns what code, secret scanning, security audits of commit history, or optimizing code review assignments.
Audit two or more interdependent repositories for drift, duplication, and practices one repository uses well and another lacks. Verify every finding mechanically, decide with the user, then apply surgical alignment fixes and adapted transfers per repository.
Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi — report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula, impact statement formula, severity decision guide, downgrade counters, pre-submit checklist. Use after validating a finding and before submitting. Never use 'could potentially' — prove it or don't report.
Use when working with, adding to, or updating the shared cross-project research library at $RESEARCH_HOME (vendor repo clones, reference PDFs/epubs, mirrored docs pages) — before fetching the same material from the web, when cloning a reference repo for a project, or when asked to update/refresh the library. Also owns judging a named package or tool before depending on or installing it — from PyPI, npm, crates.io or apt, or shipped only as GitHub release binaries: whether it is still maintained, who actually commits to it, how often it releases on its stable line, what a release really ships and costs (wheel or sdist, npm platform packages and install scripts, prebuilt binaries), whether its Python, node or glibc floor fits this machine, how far an apt package lags upstream, whether it ships types, how much test suite backs it, whether a version cap will hold you back — read from the registry, the GitHub API and the project's own source rather than from a search summary.
Use when a val's HTTP endpoints should not be open to the whole internet — limiting an app to a team, understanding why an endpoint redirects to a login page, letting a webhook through, or identifying which Val Town user is viewing an app. Covers app access (`httpPrivacy`), org grants, bypass tokens for automation, and the `X-Val-Town-User` identity header. For building your own login flow inside a val, see the `oauth` skill instead.
Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON output for https://rxresu.me.
Design and audit revenue forecasts, capacity planning, funnel assumptions, pipeline, conversion, expansion, churn, retention cohorts, gross margin, infrastructure capacity, support capacity, sales capacity, inventory/supply, scenario planning, leading indicators, and forecast governance. Use when growth plans, pricing, launches, or operations need financially credible capacity-aware planning.
Review module boundaries, coupling, public APIs, and refactors for concrete complexity and unnecessary abstraction. Use for structural reviews or requests such as "this file does too much", "hard to test", "split this file", or "the same change touches many places". Exclude ordinary bug fixes, formatting, and naming-only edits that do not affect structure.
Use when judging a finished visual prior-art artifact before it is accepted — a UI-pattern vocabulary map, a per-angle search output, an extract record, or the convention register and report. An acceptance gate, not authoring. Judges a single-sourced bar: a recorded zero is distinguishable from an unreachable source and from one refused on its terms; queries are reproducible as run; every cited corpus actually contains the convention claimed; authority and prescriptivity are recorded and not confused; a register row says what its record says; a vacated angle is not reported as a negative result; tokens are carried verbatim; an observed capture is never ranked as convention and was made within robots and terms. Approves a thin-but-honest result for a narrow UI and revises only on a named, unrecorded gap. Emits exactly VERDICT: approve|revise plus actionable findings. Keywords: design system review, UI convention review, accessibility criteria review.
Rewrite raw meeting audio transcriptions into clean, accurate meeting minutes in Traditional Chinese. Use when the user has an unprocessed audio transcription file with recognition errors and needs it cleaned up into proper meeting minutes.
Performs structured analysis of RFP (Request for Proposal) or requirement documents, identifying stakeholders, functional modules, system constraints, and generating key clarification questions. This Skill focuses on 'analysis and decomposition' to prepare for subsequent User Story writing.
Implements the GDPR Article 17 right to erasure (right to be forgotten) workflow, covering all six grounds for erasure, five exceptions, technical deletion versus anonymization decisions, and third-party notification under Article 19. Activate for erasure request, deletion request, right to be forgotten, Art. 17 queries.
Enforcing Ring's orchestrator protocol every conversation: dispatch specialist/Explore agents instead of operating tools directly, honor the >3-file hard gate, and run skill discovery before any task. Use at conversation start, before any task, when a request matches auto-trigger phrases (fix issues, refactor, find where, visualize), or when tempted to read/edit files directly. Never skip — mandatory.
Extract full text from WeChat public account articles (mp.weixin.qq.com). Use when the user provides a WeChat article URL and asks for 提取文章, 抓取公众号, 读一下这篇, or when another skill needs to read a WeChat article before processing. Bypasses WeChat's access control via MicroMessenger UA spoofing. Stdlib only, no API key required.
Use when someone asks to roast an idea, pressure-test or stress-test an idea, validate a business idea, "convene the panel", get a brutal second opinion before building something, or says "/roast". Spins up a 5-angle panel (Critic, Champion, Analyst, Investigator, Customer) that attacks the idea from every angle, then a Judge returns one GO / RESHAPE / KILL verdict with the cheapest test to de-risk it.
Use when building, fixing, testing, or reviewing any Roblox game or Roblox Studio work - Roblox, Roblox Studio, Luau, obby, tycoon, simulator, Roblox UI, Roblox combat, DataStore, RemoteEvent, Roblox multiplayer, Studio MCP. Router skill; load the matching reference for the task.
Write an operational runbook for a service, incident type, or deployment procedure. Use when asked to write a runbook, create an ops guide, document an operational procedure, or prepare an incident response playbook. Produces a runbook with overview, prerequisites, step-by-step procedures, rollback steps, troubleshooting table, and escalation paths.
Brevo platform help — email/SMS/WhatsApp campaigns, marketing automation (journeys), transactional messaging, Sales CRM (deals, pipelines), Conversations (live chat, chatbot), Loyalty programs, push notifications, e-commerce, landing pages, contact management, Aura AI, API & integrations. Use when Brevo emails landing in spam, automations not firing, contacts not syncing or importing correctly, Brevo API calls failing, or confused migrating from Sendinblue. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), designing outbound cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), transactional email strategy (use /sales-transactional-email), live chat strategy (use /sales-live-chat), or loyalty program strategy (use /sales-loyalty).
Customer.io platform help — customer engagement and marketing automation for behavior-based multi-channel messaging (email, SMS, push, in-app, WhatsApp). Use when automations aren't triggering on the right behavior, transactional messages are failing or delayed, segments aren't updating as expected, journeys need debugging or restructuring, Data Pipelines or reverse ETL aren't syncing, custom object relationships aren't working, or API calls to Track/App/Transactional endpoints are erroring. Do NOT use for general email marketing strategy (use /sales-email-marketing), cross-platform email deliverability (use /sales-deliverability), or email open/click tracking strategy (use /sales-email-tracking).
Seamless.AI platform help — Prospector, Buyer Intent, Job Changes, CRM Enrich, Pitch Intelligence, Engagement Hub (email, calling, social), AI Agents, Autopilot, Chrome extension, API. Use when Seamless.AI searches return bad data, contact credits are burning too fast, Buyer Intent isn't surfacing relevant accounts, Pitch Intelligence suggestions feel generic, AI Agents aren't performing as expected, or the Seamless.AI API isn't returning results. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts across tools (use /sales-enrich), interpreting buying signals across tools (use /sales-intent), cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or sales content strategy (use /sales-content).
SendGrid platform help — transactional email via Email API (REST + SMTP), Marketing Campaigns (drag-and-drop editor, automations, A/B testing, signup forms, segmentation), Email Validation API, Dynamic Templates (Handlebars), Event Webhooks, Inbound Parse, domain authentication (SPF/DKIM/DMARC), dedicated IPs, suppressions, Design Library, email testing, statistics. Use when SendGrid emails are landing in spam, transactional emails aren't sending, domain authentication is failing, Event Webhooks aren't firing, Dynamic Templates aren't rendering correctly, Marketing Campaigns have low open rates, or SendGrid bounce rates are spiking. Do NOT use for general email marketing strategy (use /sales-email-marketing), cross-platform email deliverability (use /sales-deliverability), or email open/click tracking strategy (use /sales-email-tracking).
SMS marketing strategy — opt-in collection, compliance (TCPA/GDPR), campaign types, automation triggers, segmentation, timing, two-way messaging, MMS, and analytics. Covers strategy and implementation across Omnisend, Klaviyo, Attentive, Postscript, Brevo, ActiveCampaign, Mailchimp, and more. Use when SMS campaigns have low click-through rates, opt-in list growth has stalled, subscribers are opting out too fast, you're unsure if your SMS program is TCPA/GDPR compliant, automations aren't converting, or you don't know which SMS platform to pick. Do NOT use for email marketing (use /sales-email-marketing), push notifications (use /sales-push-notification), cold outbound sequences (use /sales-cadence), or platform-specific config (use /sales-omnisend, /sales-klaviyo, /sales-brevo, etc.). For Omnisend-specific help, use /sales-omnisend. For Klaviyo-specific help, use /sales-klaviyo.
Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs.
Standard single-cell RNA-seq analysis pipeline. Use for QC, normalization, dimensionality reduction (PCA/UMAP/t-SNE), clustering, differential expression, visualization, and converting R-friendly single-cell formats such as Seurat or SingleCellExperiment RDS files into h5ad for Scanpy. Best for exploratory scRNA-seq analysis with established workflows. For deep learning models use scvi-tools; for data format questions use anndata.
Create and manage scheduled tasks, with support for viewing, modifying, enabling/disabling, deleting and creating scheduled tasks. Use when the user wants to set up, modify or manage tasks that run automatically on a schedule. Create and manage scheduled tasks for recurring or one-time automated execution.
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.