Skills
100,928 packaged capabilities and playbooks for agents. Install any of them with one command.
All
DevOps and Infrastructure expert with comprehensive knowledge of CI/CD pipelines, containerization, orchestration, infrastructure as code, monitoring, security, and performance optimization. Use PROACTIVELY for any DevOps, deployment, infrastructure, or operational issues. If a specialized expert is a better fit, I will recommend switching and stop.
Write Ruby and Rails code in DHH's distinctive 37signals style. Use this skill when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, or when the user mentions DHH, 37signals, Basecamp, HEY, Fizzy, or Campfire style.
Use every time code is written, modified, refactored, fixed, or reviewed, even for a few lines and on any stack (backend, frontend, scripts, configuration, infrastructure), and when asked to analyze or inspect a repo, module, or folder (“analyze the repo,” “check that everything is okay,” “find bugs”).
Expert direct mail marketing strategist for writing compelling copy, designing high-converting mail pieces, and developing measurement strategies. Use when planning direct mail campaigns, writing mailer copy, designing postcards/letters, or measuring campaign effectiveness with incremental lift analysis.
Award-winning director's brain for making films/videos with AI. Runs a gated, interrogation-first process: lock the IDEA and the SCRIPT (the story) in words before generating a single pixel, then plan shots/camera/light/sound, then generate and edit. Use whenever creating a video, film, teaser, trailer, promo, ad, short, reel, documentary, or narrative piece AND the storytelling must actually work — or any time the user says the story/script keeps failing. Hebrew triggers: סרטון, טיזר, פרומו, פרסומת, ריל, סרט, תסריט, סטוריבורד. Handles development, story, and shot-planning; composes with cinematic-ai-video and yuv-fomo-teaser (style/manipulation), hyperframes (render), nano-banana-2/ElevenLabs (assets). Backed by a 28-chapter Director's Bible in references/.
Simplify cluttered UI by removing unnecessary elements, choices, features, and structural complexity. Use when the problem is too many controls, options, features, or competing elements—not when the structure is sound and the real issue is only visual intensity or lack of personality.
Optimize Django ORM query loading by fixing N+1 queries, duplicate related-object queries, over-fetching, serializer/template query loops, and inappropriate select_related, prefetch_related, only, or defer usage. Use when a Django page, API, admin view, template, serializer, or queryset issues too many queries or loads more model data than needed.
Creates Product Requirements Documents (PRDs) from feature requests following a structured workflow of clarification, planning, and drafting. Outputs a standardized PRD to the project prds directory. Use when the user asks to create a PRD, define requirements, or document a new feature. Do not use for technical specifications, task breakdowns, or implementation planning.
Receives the path of a bug file in qa-bugs/ (e.g. qa-bugs/bug-01-alta-formulario.md), analyzes the root cause, implements the fix with regression tests, validates the test suite and updates the file status. Use when the user asks to fix a specific bug found in QA. Do not use for batch fixes — invoke once per bug. Do not use for implementing new features, code review or running QA.
Transform any DOCX document with world-class brand styling. Choose from 10 premium brand aesthetics (The Economist, McKinsey, Deloitte, KPMG, Stripe, Apple, IBM, Notion, Linear, Figma) to polish documents with professional typography, colors, and formatting. Use when users want to: (1) Apply premium brand styling to documents, (2) Make documents look more professional, (3) Match a specific brand's visual identity, (4) Create polished reports, proposals, or presentations.
Build Docyrus React TypeScript web applications end-to-end, combining authentication, API access, @docyrus/app-utils runtime helpers, @docyrus/devtools in-app debugging, generated collections, TanStack Query/Form patterns, and production-grade UI implementation with preferred component libraries. Use when creating or modifying Docyrus-backed apps that use @docyrus/api-client, @docyrus/signin, @docyrus/app-utils, @docyrus/devtools, Docyrus collections, queries, dashboards, forms, tables, layouts, or Docyrus UI components.
Avoid unnecessary useEffect in React components. Most uses of useEffect are anti-patterns — derived state, event-driven logic, data fetching, and external store subscriptions all have better, more idiomatic alternatives. Apply this skill when writing or reviewing React components that use useEffect.
Provides comprehensive guidance for draw.io architecture diagrams including diagram creation, shapes, templates, and collaboration. Use when the user asks about draw.io architecture, needs to create architecture diagrams, design system diagrams, or collaborate on diagrams.
HTMX in Drupal 11.3+ core — the Htmx PHP fluent builder, dynamic forms with swapOob, partial routes with _htmx_route, response headers, and Drupal.behaviors integration. Use when building interactive UI without full-page reloads using Drupal's native HTMX support.
Plan and scaffold an academic introduction section from source papers, context, or rough notes. Use this skill whenever Ilya wants to structure an intro, outline a paper's opening, map the literature into a writing plan, figure out what paragraphs an introduction needs, or asks \"what should my intro cover?\", \"help me plan my introduction\", \"outline an intro from these papers\", \"what topics should I introduce?\", \"scaffold my intro section\", \"turn these papers into an intro plan\", or \"structure my background section\". Also trigger when the user uploads or pastes papers/abstracts and wants to know what to write about — even if they don't say \"introduction\" explicitly. This skill does NOT write the prose; it produces a clear paragraph-by-paragraph blueprint that guides writing. For the actual prose, hand off to ea-academic-writer.
Guides a partner building an EMAP merchant-signup form on their own website, in any tech stack (React/Next.js, Vue/Nuxt, Angular, Svelte, PHP/WordPress, Rails, Django, ASP.NET, static sites, site builders). Every EMAP API call is made from the merchant's browser, never from the partner's server, so EMAP can rate-limit by the merchant's real IP. Covers Integration 1 (full form — all 6 signup steps hosted on the partner site), Integration 2 (redirect handoff — browser redirects to EMAP with step-1 data in URL params, EMAP prefills its form and submits it for the merchant when the data passes its validation), and Integration 3 (email-based signup — step-1 data is POSTed directly to EMAP's REST API from the browser, EMAP creates the record and emails the merchant a secure link to complete their full application). Provides field references, code templates, and a security checklist.
When the user wants to optimize energy supply chains, coordinate oil and gas logistics, or manage energy infrastructure. Also use when the user mentions "energy transportation," "pipeline management," "energy distribution," "oil and gas supply chain," "LNG logistics," "petroleum logistics," "energy asset management," or "energy infrastructure." For renewable energy, see renewable-energy-planning. For power grids, see power-grid-optimization.
Explains code or code changes in plain language, briefly by default or in full for a reviewer. Use when the user says "explain this PR", or when asked to explain, ELIE, summarize, or break down a PR, diff, branch, file, function, or concept for someone new to the code. Not for how a whole subsystem works; use explaining-architecture.
Extract reusable components, product patterns, and design tokens into a clearer design system with shared APIs, documented defaults, and better reuse. Use when the user wants to refactor repeated UI, consolidate buttons/cards/forms/sections, build a component library, or turn one-off values into reusable tokens.
Add, fix, refactor, debug, test, or explain Flutter animations and motion effects. Use for implicit animations such as AnimatedContainer, AnimatedOpacity, AnimatedSwitcher, and TweenAnimationBuilder; explicit animations using AnimationController, Tween, CurvedAnimation, AnimatedWidget, AnimatedBuilder, and built-in transitions; Hero/shared-element route transitions; staggered or sequenced animations; physics-based motion, gestures, springs, flings, scroll physics, curves, performance, accessibility, reduced motion, and animation lifecycle bugs.
Build Flutter forms with Form, TextFormField, DropdownMenuFormField, and custom FormField. Covers validation, AutovalidateMode, forceErrorText, theme-driven InputDecoration, autofillHints, keyboards, and focus traversal on Flutter 3.47+. Use when adding or fixing a login, signup, checkout, or any validate/save form; when fields jump, lose text, skip autofill, or ignore FormState.validate(); or when the user runs /flutter-building-forms
How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel. Only use for flutter/flutter landed pull requests. Only use when the cherry pick request is into "stable", "beta" or a branch that has the format with flutter-<major>.<minor>-candidate.0
When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro.
Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.
Use when the user invokes /gauntlet-loop or asks to turn an objective, plan, spec, PRD, or requirements document (inline text, a .md file, or an .html file) into an orchestrated execution system prompt — e.g. "gauntlet this plan", "make an orchestrator prompt for this spec", "generate the execution prompt for @plan.md".
A GEO (generative engine optimization) brand analysis tool. Automatically queries six AI search engines—Doubao, Kimi, DeepSeek, Yuanbao, Qianwen, and Baidu—to analyze brand mentions in AI responses, sentiment, source citations, and competitor comparisons, then generates an interactive HTML report. Use when analyzing a brand’s performance in AI search engines, GEO optimization, AI search brand monitoring, or brand visibility in AI. Trigger phrases: GEO analysis, brand AI search analysis, AI search engine optimization, brand visibility, GEO, geo analyzer
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.