Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Write changelog entries for open source documentation sites using Keep a Changelog format. Use when asked to "write a changelog", "update the changelog", "add changelog entry", "document recent changes", or after a release/set of changes that should be recorded. Reviews git commits since the last changelog entry and produces a categorized, human-readable entry.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing—API docs, architecture docs, or operational runbooks.
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component structure, or when user mentions annotations, queued tasks, UI changes, props, state, DOM, or asks about how elements render at runtime.
.NET code quality with Roslyn analyzers, StyleCop, and dotnet format. Covers linting, formatting, and best practices for C#/.NET. USE WHEN: user works with "C#", ".NET", "ASP.NET Core", asks about "Roslyn analyzers", "StyleCop", "dotnet format", ".NET linting", "C# best practices" DO NOT USE FOR: SonarQube - use `sonarqube` skill, testing - use .NET test skills, security - use `dotnet-security` skill
Pattern for wrapping third-party SDK clients (Stripe, Resend, AWS, etc.) with Effect. Use when creating Effect services that wrap external libraries with Promise-based APIs. Provides type-safe error handling, automatic tracing, and clean dependency injection via the "use" pattern.
Effect v4 (4.0.0-beta.x) patterns and architecture judgment for TypeScript. Use when writing or reviewing Effect services, layers, schemas, typed errors, boundaries, config, CLIs, runtimes, or tests; when shaping or reviewing the structure of an Effect project, proposing a service or boundary, or arguing a wrapper is unnecessary — or when a project depends on `effect@4`. Effect v4 differs sharply from v3 and from plain TypeScript; verify APIs against the project's pinned source instead of recalling them.
Electron framework for building cross-platform desktop applications with JavaScript, HTML, and CSS. Covers architecture, IPC, security, packaging, auto-updates, and backend integration patterns. USE WHEN: user mentions "Electron", "desktop app", "cross-platform application", asks about "IPC", "main process", "renderer process", "Electron packaging", "auto-updates", "code signing", "Electron security" DO NOT USE FOR: Tauri applications - use `tauri` skill instead
Comprehensive 2026 engineering best practices for agentic coding. Apply when writing, reviewing, or refactoring code across Node.js, Next.js, NestJS, Java, Spring Boot, Python, Elixir, Phoenix, Erlang, Rust, Go, React, Vue, Nuxt, Astro, and SQL/NoSQL databases. Covers security (OWASP Top 10, zero trust, supply-chain hardening), performance (async I/O, caching, connection pooling, N+1 prevention), idempotency, atomicity, concurrency, observability (OpenTelemetry, structured logging), and accessibility (WCAG 2.2 AA). Includes per-stack version baselines, idiomatic patterns, known CVEs and gotchas (e.g. Next.js CVE-2025-29927, Valkey 9.1 RC), and pre-merge/pre-production checklists. Use for any programming task regardless of language or framework.
Write a weekly engineering status report for a team, service, or initiative. Use when asked to write a team update, weekly engineering report, sprint status email, or standing team communication to stakeholders. Produces a concise, scannable weekly report covering shipping progress, metrics, decisions, blockers, and next-week priorities.
Generate deterministic INSERT SQL seed data from Go Ent schemas and mixed inputs. This skill is REQUIRED whenever you need to create seed SQL for development or testing - it handles entity inference, relationship integrity, stable IDs, and dialect-specific SQL generation including JSON, arrays, and complex types. Use this skill for any task involving seed data, test fixtures, demo initialization, or database population from Ent schema definitions, even if the user doesn't explicitly mention "seed" or "SQL".
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
Guides event-driven systems—pub/sub, point-to-point, event sourcing, CQRS, schema versioning (Avro/JSON Schema), ordering, partitioning, delivery guarantees, idempotency, exactly-once tradeoffs, transactional outbox/inbox, choreography vs orchestration, sagas, dead-letter queues, replay, stream vs discrete events, microservice boundaries. Use when the user asks for event-driven architecture, event sourcing, CQRS, pub/sub, Kafka events, outbox pattern, idempotent consumer, event choreography, saga orchestration, dead letter queue, or event schema versioning—not microservice code only (microservices-developer), enterprise API/iPaaS only (enterprise-integration-api-developer), EDI (edi-engineer), classified promotion (classified-software-devsecops-engineer), solvers (operations-research-algorithm-developer), generic CRUD (senior-software-engineer).
(NS) Execute a GitLab issue end-to-end — first-act status, branch-reuse and source-branch gates, single-worktree isolation, atomic delivery, MR lifecycle, mandatory code review gate with bounded fix loop. Use when the user provides a GitLab ISSUE_URL or asks to implement a GitLab issue directly — not for local-only ad-hoc coding (use code-coder) or non-GitLab autonomous runs (use code-autonomous standalone). Delegates actual coding to the code-autonomous engine. Requires mcp-gitlab-usage for MCP and code-reviewer for the review gate.
Launch a GrowthBook A/B test end-to-end via the REST API — create the experiment, prep the feature flag, wire the experiment-ref rule, and start the experiment. Use when the user says "launch this experiment", "create the experiment", "wire up the A/B test", "kick off the test", "set up X as an experiment in GrowthBook", "start the experiment for flag Y", or "I already have a flag and want to run an experiment on it". Works for both experiment-first (creates the flag) and flag-first (detects the existing flag via the reuse path and wires the experiment to it). For designing the spec first, use experiment-design. For stopping a running experiment, use experiment-stop. For interpreting results, use experiment-analyze.
Use when the user wants to understand a technical concept, compare options, see code examples, assess the impact of adopting something in the current repository, or see candidate high-level designs for a request. Produces an explanation or exploration brief. Do not use when the user has a settled direction and wants requirements, design, or implementation.
Build, review, debug, configure, migrate, or plan Feedsmith v3+ TypeScript/JavaScript feed parsing and generation. Use for feedsmith, parseFeed, parseRssFeed, parseAtomFeed, parseRdfFeed, parseJsonFeed, parseOpml, generateRssFeed, generateAtomFeed, generateJsonFeed, generateOpml, detectRssFeed, RssFeed, AtomFeed, JsonFeed, namespaces (itunes, podcast, media, dc), parseDateFn, maxItems, extraOutlineAttributes, strict mode, DetectError, MalformedError, ParseError, GenerateError, OPML, and v2→v3 migration.
Publish a GrowthBook feature flag draft revision, resolve merge conflicts, revert to a prior revision, or discard a draft. Use when the user says "publish this draft", "push this live", "go live with revision X", "there's a merge conflict on my flag", "rebase my draft", "fix the merge conflict on flag X", "revert flag X to a previous version", "roll back this flag change", "discard this draft", or "abandon these changes". For requesting or submitting an approval review before publish, use flag-review. For listing and inspecting drafts, use flag-revisions.
Create or manage a multi-step ramp schedule for a GrowthBook feature flag rule — progressively increasing traffic exposure over time with defined intervals between steps. Use when the user says "gradually roll this out", "increase traffic from 5% to 100% over a week", "set up a ramp schedule", "advance to the next ramp step", "pause the rollout", "roll back the ramp", or "set a cutoff date on this rollout". For rollouts that also need guardrail metric monitoring and automatic signals, use flag-monitoring — it builds on this skill with monitoring configuration. For simple on/off time windows, use flag-schedule.
List, inspect, and manage draft revisions for a GrowthBook feature flag. Use when the user asks "what drafts are open for flag X", "show me pending approvals", "who owns this draft", "discard this draft", "start a new draft", "what revision is my flag on", "list all my pending changes", "what's waiting for review", or any question about the state of in-progress changes to a flag. Every flag write operation — rules, metadata, default value, toggles — works through a draft revision; use this skill to see what's in flight before making changes. For requesting or submitting an approval review, use flag-review. For publishing a draft live or resolving merge conflicts, use flag-publish. For making flag changes, use the relevant flag-* write skill.
Entry point for working with rules on a GrowthBook feature flag. Use when the user asks "what rules does flag X have", "show me the rules on this flag", "add a rule", "delete a rule", "reorder the rules", or describes a flag operation without specifying the rule type. Routes to specialized skills for creating and editing specific rule types. Also handles listing, reordering, and deleting rules directly. For specific rule types, use flag-targeting for force/rollout rules, flag-experiment for experiment-ref rules, flag-schedule for timed activation, flag-ramp for progressive rollouts, flag-monitoring for monitored rollouts, flag-prerequisites for feature-level prerequisite gates.
Add a timed activation window to a GrowthBook feature flag rule — automatically enable it at a start time and/or disable it at an end time. Use when the user says "turn this on at 9am", "schedule the flag to go live Friday at noon", "disable the rule after the sale ends", "set an end date on this rule", "run this rule during the promotion window", or "time-gate this rule". Applies to force and rollout rules. For multi-step progressive rollouts with intervals between steps, use flag-ramp. For the broader campaign of rules around this schedule, use flag-targeting first.
Governed workflow for AI-assisted coding on a real repo. Triggers: bounded tasks, file scope, task ledgers, claim-before-implement, evidence trails, critique/review/security gates, or multi-agent/multi-repo coordination. Use on any mention of "FORGE", `docs/forge/`, or governed development, or when agents drift outside scope. Not for one-off edits or unstructured review.
Plateforme de conception, planification et spécification de nouveaux produits logiciels. Transforme une idée initiale en un plan d'implémentation exhaustif, sans ambiguïté, suffisamment précis pour être exécuté par une IA même peu performante. Couvre PRD, roadmap, benchmarks, design UI/UX, architecture, découpage en slices, plan d'implémentation par slice, plan de tests, analyse d'impact, et validation automatique des plans (mode Fast Track). Utiliser pour tout nouveau projet (greenfield) — de l'idée vague jusqu'au plan prêt à coder. Ne pas utiliser pour migrer un projet existant vers une autre stack, ni pour un travail sur du code legacy. — Design, planning and specification platform for new software products. Turns a rough idea into an exhaustive, unambiguous implementation plan precise enough for a low-capability model to execute: PRD, roadmap, benchmarks, UI/UX design, architecture, slice breakdown, per-slice implementation plans, test plan, impact analysis, and automated plan validation (Fast Track mode). Use this skill for any greenfield project, from a vague idea to a code-ready plan. Do not use it to migrate an existing project to a different stack, or to work on legacy code.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics
Frontend patterns for Rails applications using Slim templates, Stimulus JavaScript framework, CSS with Optics utilities. Use when building views, adding interactivity, styling components, or when the user mentions Slim, Stimulus, JavaScript, CSS, or frontend development.
Frontend UX rules for Ethereum dApps that prevent the most common AI agent UI bugs. Mandatory patterns for onchain buttons, approval flows, address UX, USD context, RPC reliability, theming, and pre-publish metadata. Use whenever you are building a frontend for an Ethereum dApp.
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
Draft a review-friendly commit message and create the Git commit non-interactively. Use when you need to commit either the already-staged changes or the full current working tree relative to `HEAD`, while preserving a review-friendly message and footer handling. Trigger for requests such as the skill `git:commit` or the skill `git:commit` with `HEAD`, especially when the user wants safe staging behavior and a clean commit created from the drafted message.
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.