Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use Bitwarden Agent Access CLI (`aac`) with agent-controlled browser login flows. Use when a user wants an AI agent to log into a website through `aac listen`/`aac run`, approve credentials in Bitwarden Agent Access, fill browser login forms without printing passwords, debug Agent Access browser login pairing, or build a credential-conscious bridge between `aac run` env injection and browser automation.
Lean facilitator for creating, updating, and validating a product brief — the Analysis-phase foundation of the BMAD Method. Captures problem statement, target users, core features, goals, constraints, and success metrics. Use when the user says: "create a product brief", "I need a product brief", "let's do discovery", "help me define my product", "what problem are we solving", "capture our product vision", "update the product brief", "validate the brief", "check if the brief is complete", "run discovery", "start a product brief", "brainstorm the product", or "I want to plan a product". Supports three intents: - Create — guided discovery conversation that fills and writes the brief - Update — amends one or more sections in an existing brief - Validate — completeness check against all required sections Output is a planning artifact only — no code is written or run.
Создаёт однозначную спецификацию результата без шагов реализации. Используй, когда пользователь хочет зафиксировать задачу и контекст, целевой результат, рамки и критерии приемки, оставив технический путь исполняющему агенту. Не используй для выбора решения, составления плана реализации, непосредственной реализации или ревью изменений кода.
Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline—author → eval → QA → trigger-audit → release—to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "redo the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin
Use this skill when a designer needs to prepare for a business kickoff workshop with a new customer, or needs to fill a Business Model Canvas after the call. Triggers when someone mentions a kickoff call, BMC workshop, business model canvas, or needs to prepare questions for a new customer discovery session.
Patterns and anti-patterns for using OpenAI Codex Goals — the persistent objectives feature introduced in Codex 0.128.0. Use this skill whenever writing, reviewing, or debugging a `/goal` invocation, deciding whether a task should be a Goal at all, drafting a research Goal that needs an evidence ledger, or diagnosing a Goal that completed against the wrong surface. Triggers on `/goal`, "Codex Goal", "Codex goals", "persistent objective", "evidence-based completion", "iteration policy", "blocked stop condition", or any user message describing a multi-turn Codex task with a defined finish line. Trigger even if the user doesn't explicitly mention Goals — if they're typing "/goal" or asking Codex to "keep going until X", this skill applies.
Build and grow developer and user communities from scratch — covering ambassador programs, community-led growth (CLG), event operations, content strategy, and health metrics. Grounded in real playbooks from Notion, Lovable, AFFiNE, ClickUp, Asana, and Lark. Use when: building a community for an open-source project, SaaS product, or brand; recruiting and managing ambassadors or community leaders; planning community events (online/offline meetups, AMAs, hackathons); designing ambassador tier/points systems; setting community health KPIs; launching a Build-in-Public strategy; setting up Discord, Slack, or Lark communities; running developer relations (DevRel); or when the user asks about community operations, ambassador programs, CLG, user advocacy, KOC/KOL cultivation, UGC flywheels, community monetization, or any variation of "how do I grow my community".
Analyze a software codebase for algorithmic complexity and performance hotspots, then propose or implement safe optimizations without breaking behavior. Use when the user asks to scan many files, find inefficient loops, nested iteration, repeated scans, costly rendering/recomputation, N+1 queries, avoidable O(n^2) or O(n) operations, or reduce complexity such as O(n^2) to O(n log n) / O(n), while preserving tests, APIs, outputs, and maintainability.
Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware infection, including trojan/worm/ransomware outbreaks, malware triage, or infected endpoint remediation.
SVG Style Studio (/create-svg) - art director + vector illustrator that makes polished, editable SVGs (illustrations, logos, icons, posters, infographics, stickers) in 44 styles - pixel art, 8/16-bit, cyberpunk, Y2K, Frutiger Aero, glassmorphism, clay, isometric, low poly, paper cutout, doodle, comic, manga, sumi-e, ukiyo-e, art nouveau, art deco, bauhaus, brutalist, vintage poster, screen print, risograph, blueprint, technical/scientific, medieval, graffiti, sticker, children's, editorial, infographic, cinematic, fantasy, sci-fi, horror, retro futurism, gothic, luxury, monochrome, geometric, botanical. Use for any request for SVG/vector art, style blends ("cyberpunk + minimalist", "ukiyo-e but darker"), one subject in several styles ("in 5 styles"), or converting an SVG/image to a style. Routes the style, applies its design rules, then validates, optimizes, renders and inspects before delivering.
Use this skill when the user wants to create, draft, author, or extract a slide theme in this open-slide repo. Triggers on phrases like "create a theme", "make a theme called X", "extract a theme from <slide>", "build a theme from these images". Produces two paired files under `themes/` — `<id>.md` (palette, typography, layout, fixed Title/Footer components, motion) and `<id>.demo.tsx` (a runnable demo slide that the dev-UI Themes panel previews). Do NOT use for editing real slides — only for authoring the theme bundle.
Creative writing skill for capturing story brainstorming. Use when the user is exploring narrative ideas, discussing characters, planning episodes, or thinking through story possibilities. Creates minimal working notes that preserve creative freedom by recording only what was stated and marking sources.
Salesforce Data Cloud integration patterns and architecture (2025). PROACTIVELY activate for: (1) Data Cloud setup and ingestion, (2) Data Streams (cloud, mobile, web SDK, ingestion API), (3) data model objects (DMO) and source objects (DSO), (4) identity resolution and unified profiles, (5) calculated insights and segmentation, (6) activations to Marketing Cloud, advertising platforms, Salesforce CRM, (7) Bring Your Own Lake (BYOL) with Snowflake, BigQuery, Databricks, (8) zero-copy data sharing, (9) Data Cloud + Agentforce grounding, (10) consent management and compliance. Provides: data-stream selection matrix, identity resolution rules, segmentation patterns, BYOL configuration, and activation playbook.
Use this skill to find which Jetpack Compose composables are recomposing and why, using Android Studio Layout Inspector recomposition counts and skip counts, the per-parameter Argument Change Reasons (Changed / Unchanged / Uncertain / Static / Unknown) introduced in Android Studio Hedgehog and later, and runtime `@TraceRecomposition` from `compose-stability-analyzer` for production-like measurement. Walks through enabling counts, mapping each Argument Change Reason to a fix, and confirming the result in a release build. Use when the developer says "this should be skipping but isn't", "I want to see recomposition counts", asks what "Uncertain" or "Unknown" means in the inspector, or needs to confirm a stability or strong-skipping fix actually worked end-to-end.
Builds scalable design systems with tokens, theming, and component architecture. Use when creating design token hierarchies, theming systems, component variant patterns, or accessibility foundations. Use for design tokens, CVA variants, dark mode, multi-brand theming, Radix headless UI, Storybook documentation, and governance
Remove AI writing patterns from prose. Use this skill when writing, drafting, editing, reviewing, or revising any text to eliminate predictable AI tells, slop, and formulaic patterns. Trigger this skill whenever the user asks you to "deslop", "de-AI", "make it sound human," "remove AI patterns," "remove AI tropes," "clean up AI writing," fix "slop," "deslop" text, or review prose for authenticity. Also use when the user asks you to write or draft anything and wants it to sound natural rather than AI-generated. Common use cases include scientific writing (manuscripts, abstracts, cover letters, grant narratives, discussion sections, peer review responses), blog posts, newsletters, memos, reports, and any other substantial prose.
Use this skill when the user asks about domain modeling, primitive obsession, parse-don't-validate, semantic types, value objects, or making invalid states unrepresentable. Triggers on: “review for domain issues,” “primitive obsession,” “design domain types,” “value object,” “newtype wrapper,” “semantic type,” “make invalid states unrepresentable,” “bool-as-state,” requests to replace raw strings/ints with proper types, requests to fix swappable parameters, or any code review focusing on type safety and domain integrity. Also activates during TDD domain review phases. Not for general code review (style, formatting), debugging, database schema design, or design patterns unrelated to domain type modeling.
Design system engineering aligned with Airbnb-DLS for Expo / React Native apps targeting web and native iOS, built on Unistyles v3, Reanimated, Skia, and FlashList. Use when building, reviewing, or refactoring shared UI, including design tokens, theming, variant-driven component APIs, typography, spacing, cross-platform web/iOS parity, native-feel performance, and complex surfaces such as calendars and drawing canvases (examples use a clinic app). Covers token architecture, theming, component API contracts (variants over style props), web/iOS parity (Unistyles `_web` hover/focus/cursor, Platform splits, one shared theme), the Unistyles styling engine, and governance. Trigger even when the user does not say “design system” but is creating or changing reusable React Native components, tokens, or theme code, or making a component behave natively on both web and iOS. Teaches how to build the design system; pair with expo-react-native-coder for features and expo-ios-hig for iOS native-feel decisions
Subscribe to Feishu events in real time (WebSocket). Use event list to view supported EventKeys; event schema to view event payload/scope; event consume to start a persistent subscription, writing the event stream as NDJSON to stdout (blocking; one EventKey per process); event status to view active local consume processes; and event stop to stop consume by PID / EventKey / --all. Supports 22+ EventKeys (im message received/read/recalled/reaction, group member changes, contact employee changes, calendar changes, cloud drive title/collaborator changes, approval instances and tasks, VC meeting start/end). Supports reconnection and parallel subscriptions to multiple EventKeys. Use when the user requests “listen for Feishu events,” “receive message events in real time,” “subscribe to approval callbacks,” “event stream,” “persistent WebSocket listener,” “event consume,” “event list / schema / status / stop,” or “AI Agent bot real-time response.” Note: This skill only handles subscriptions; for event webhook business logic (pushing to Feishu messages/writing to Bitable), use feishu-cli-msg / feishu-cli-bitable.
Deep accessibility scorecard for a single Figma component or component set — state coverage (default/hover/focus/disabled/error/active/loading), focus-indicator quality and contrast, non-color state differentiation, target size, annotation completeness, and color-blind simulation (protanopia/deuteranopia/tritanopia), all rolled into per-category 0–100 scores and prioritized recommendations. Use when the user wants to vet ONE component before shipping it: triggers 'audit this component', 'accessibility score for this button', 'is this component set accessible', 'check the states on this component', 'does my button have a focus state', 'color blind check', 'rate this component for a11y', 'component accessibility scorecard'. Works on ANY Figma plan. For a broad sweep over a whole page/frame use figma-lint-design; for CODE-side (HTML) checks use figma-scan-code-accessibility.
Map Figma variables to repo tokens and write Figma agent rules. Use when asked to "extract Figma design tokens", "map Figma tokens to our theme", "create Figma design system rules", "set up Figma guidelines", "code connect this component", or "map this Figma component to code"; when Figma-to-code output must follow this repository's components, tokens, and rules files (`AGENTS.md`, `CLAUDE.md`, `.cursor/rules/`) or needs a correction pass against them; or when asked to "implement this Figma design" or "build from a Figma link" and `figma-design-to-code` is not installed. Skip Figma-side writes and code-to-Figma CI export (use `code-to-figma`).
Apply Apple/iOS-style 60% corner smoothing to UI shapes without broken border-radius hacks. Use when implementing squircle-like rounded rectangles, Figma corner smoothing, iOS-style cards/buttons/icons, SVG path rounded rectangles, clip paths, canvas shapes, or when a user asks for radius plus smoothing percent values such as radius 52 and smoothing 60.
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows (git-pr), git commits (git-commit), or deploy/release ops
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
This skill should be used for multi-session autonomous agent work requiring progress checkpointing, failure recovery, and task dependency management. Triggers on '/harness' command, or when a task involves many subtasks needing progress persistence, sleep/resume cycles across context windows, recovery from mid-task failures with partial state, or distributed work across multiple agent sessions. Synthesized from Anthropic and OpenAI engineering practices for long-running agents.
Set up and validate Splunk HTTP Event Collector (HEC), explain indexer acknowledgment and distributed HEC behavior, diagnose HEC no-data and HTTP delivery failures from sanitized evidence, and prepare bounded escalation handoffs. Use for Splunk Cloud Platform or Splunk Enterprise HEC tokens, endpoints, event or raw payloads, TLS, channels, ACK, health, authorization, queues, and delivery verification; do not use for non-HEC ingestion, broad architecture, allowlist changes, or service-side remediation.
Improve a Hinge dating profile through research-backed screenshot audits, photo selection and ordering, conversational discovery, prompt and caption writing, settings review, or post-launch troubleshooting. Use for a full profile rebuild or a focused request about photos, copy, positioning, match quality, or profile performance.
Trace one idea's evolution through the brain: first mention, best articulation, related concepts, reversals, contradictions, abandoned branches, and the current live version. Use for single-idea conceptual lineage, not broad concept-map synthesis or structured entity metrics.
Use the local Kaggle CLI skill for command guidance, workflows, and troubleshooting across competitions, datasets, kernels/notebooks, models, model variations and versions, inbox file uploads, forums/discussions, benchmarks, configuration, OAuth/API-token authentication, and accelerator quota. Activate this skill when the user asks about kaggle CLI commands, examples, flags, metadata files, download/upload flows, submissions, benchmark tasks, or Kaggle CLI behavior.
Based on the real-person AI voiceover script and Jeffrey identity reference image, use the 秋芝03KV visual system by default, select the scene template that best matches the semantics, and generate only three full-size covers for the same concept in 3:4, 4:3, and 16:9. Use when the user says “generate cover prompts,” “make a cover,” “cover,” “cover image,” or “cover wording,” or when the workflow reaches ⑥.
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.