Skills
97,501 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Senior full-stack engineer mode. The agent owns technical decisions and implementation; the user is the engineering manager who sets the what/why and approves the Stage 3 plan before any code is written. Full-stack feature work in existing codebases: backend APIs, services, data models, migrations, background jobs, external integrations, CLIs, libraries, plus product UI (pages, forms, tables, modals, dashboards). Use when the user wants to implement / add / build / extend a feature: "let's build X", "add feature Y", "implement Z", multi-module refactors, schema changes, new endpoints, new pages or components in an existing product, or any non-trivial engineering task that requires reading existing patterns before writing code. Prefer over a plain coding response whenever the feature has more than one moving part.
Audit a game, feature, encounter structure, roguelite run, puzzle sequence, onboarding path, or progression gate through the lens of its failure loop: what happens after the player fails, what they learn, what they lose, and why they would or would not try again. Use when diagnosing whether failure teaches, motivates, stalls, humiliates, exhausts, or ejects the player, or when tuning punishment, retry structure, and post-failure recovery.
Extract the core player fantasy from a game, feature, loop, or pitch based on what the design actually lets the player do, feel, and become. Use when a team can describe mechanics but cannot clearly articulate the fantasy those mechanics are supposed to deliver, when a concept feels emotionally vague, when a pitch names features instead of a player promise, or when you need to test whether the claimed fantasy is real, weak, conflicted, or absent.
Researches video games via the Crawlora API — Steam (store pages, pricing, reviews, player counts, charts, tags, achievements) and PlayStation Store (products, categories, deals) — returning clean JSON. Use when the user wants a game's price/reviews/player count, what's trending or on sale, or a store listing's details.
GATK Best Practices for germline SNP/indel calling from WGS/WES BAMs. Per-sample HaplotypeCaller GVCFs, GenomicsDBImport, GenotypeGVCFs joint calling, VQSR or hard filters. Requires BWA-MEM2-aligned, markdup, BQSR BAMs. Use DeepVariant for a faster DL alternative; GATK is the NIH/ENCODE standard.
(Experimental) Runs an end-to-end observability rollout for an application on Grafana Cloud via gcx: instrumentation, SLOs, alerts, synthetic checks, k6, IRM, dashboards, cost, GitOps. Use to set up monitoring for a service from scratch. For LLM apps use agento11y-instrument.
Guides the audit of Records of Processing Activities (RoPA) against GDPR Article 30 requirements for both controllers and processors. Activate when verifying RoPA completeness, validating mandatory fields, or preparing for supervisory authority inspections. Keywords: RoPA, Article 30, records audit, processing activities, controller records, processor records.
Plans and audits local genomic-interval machine learning workflows with Geniml (0.8.4) and Gtars: validates BED files against chromosome sizes and assembly contracts, plans Region2Vec, scEmbed, and BEDspace runs, checks model, tokenizer, and universe.bed compatibility, and assesses consensus universes (CC, CCF, ML, HMM, assess-universe). Bundled scripts only validate or plan; they do not train. Use when checking BED coordinates, contigs, or assembly before analysis. Use when planning Region2Vec or scEmbed training on tokenized Parquet data. Use when verifying that a checkpoint, config.yaml, and universe match. Use when building or assessing a consensus peak universe. Use when reviewing BEDbase or Hugging Face download risks. Not for general BED manipulation or peak calling; use bedtools or similar tools.
Predict regulatory features, gene structure, and expression directly from DNA sequence using Genomic Intelligence''s hosted transformer DNA language models — no local GPU or model weights. Six tasks over a REST API and a hosted MCP server (keyless public demo): promoter regions, splice donor/acceptor sites, enhancer activity, chromatin state, sequence-to-expression (log TPM), and de-novo gene annotation, plus a composite find-genes-then-predict-expression workflow. Use when the user has a gene symbol, a genomic region, or a DNA/FASTA sequence and wants any of these predictions, mentions Genomic Intelligence, genomicintelligence.ai, api.genomicintelligence.ai, or mcp.genomicintelligence.ai.
Git + worktree orchestrator: status survey, per-worktree triage, commits, PRs, branches, releases, rebases — reads inline, writes to a background agent. Triggers on: git status, anything to commit, anything to push, commit, push, create PR, rebase, release, tag, changelog, worktree, land worktrees.
Analyze one GitHub user's code contribution activity in a specified UTC time window and generate a Markdown report focused on practical contributions (authored merged PRs, PRs merged by the target user, and authored commits) across accessible public and private repositories. Use when users ask to evaluate real engineering contribution over a period and want evidence links.
Plan and deliver persuasive, confident presentations and produce a Presentation Pack (brief, narrative, slide outline, Q&A bank, pre-brief plan, rehearsal plan, delivery checklist). Use for presentation, deck, keynote, all-hands, exec review, demo talk track. Category: Communication.
Implementation guide for Global Privacy Control (GPC) automated opt-out signal per CPRA Section 1798.135(e). Covers Sec-GPC HTTP header detection, JavaScript navigator.globalPrivacyControl API, and state-specific requirements for CA, CO, CT, MT, TX, and OR. Includes server-side detection code and compliance mapping.
Set and track goals for a solopreneur business using OKRs (Objectives and Key Results) and related frameworks. Use when defining business goals, creating quarterly or annual targets, building KPIs, tracking progress, or aligning daily work with strategic direction. Covers OKR methodology adapted for solo operators, goal hierarchy (vision → annual → quarterly → weekly), and review cadences. Trigger on "set goals", "OKRs", "business goals", "quarterly goals", "KPIs", "goal setting", "how to track progress", "annual goals", "prioritize my work", "what should I focus on".
Route goalflow (wanmol/goal-flow) work — a LangGraph framework that combines workflow graphs with agent loops — into exactly one mode: fit check, transpiling a Dify DSL export into runnable LangGraph Python, authoring workflow nodes and edges, building an `agent_kit` loop with middleware and a harness, wiring the serving layer (data adapters, SSE streaming, HITL, Redis/MySQL, API-key registration), or running the pre-publish security gate. Use when the user wants Dify's visual design without Dify's runtime, a graph node that hosts an agent loop, an OpenAI-compatible wire protocol over their own workflows, or prompt-injected `SKILL.md` capabilities. Triggers on: goalflow, goal-flow, dify to langgraph, dify transpiler, dify DSL export, BaseWorkflow, agent_kit, AgentBaseNode, DataAdapter, chunk processor, HITL interrupt, dify2langgraph. Route plain graph-API questions to `langgraph-fundamentals`.
Godot 4.x game development (verified on 4.7) - scaffold, inspect and edit projects, scenes, UI, resources headlessly; author tilesets, ASCII-painted levels, themes, animation, audio buses, custom Resources, collision/navmesh bakes, shaders, export presets; draw pixel art from ASCII, clean generated art, synthesize sound effects and looping music; look up the installed engine's exact API; lint GDScript, scenes and shaders without Godot (Godot 3 renames, un-inferable :=, dead node paths, input actions, res:// paths); catch editor-only node warnings; move files safely; unit-test, smoke-run every scene with input fuzzing, debug, export; verify it all as text (node trees, UI layout, 2D/3D placement, level, image, audio read-backs), no vision or hearing needed. Use when Codex needs to build or fix a Godot game, write or repair .gd/.tscn/.tres/.gdshader files, add art, sound, levels or UI, migrate Godot 3 code, reorganize a project, or validate, test and export.
Structure Go application logic with pragmatic CQRS. Use when command and query concerns are mixed, handlers are hard to test, one application service is becoming wide, or a Go service needs business-oriented command and query naming, separate handlers, thin ports, narrow consumer-owned interfaces, and guidance on when CQRS is or is not worth the cost.
Support Go services by keeping infrastructure, security boundaries, and automated tests aligned with the application architecture. Use when working on Terraform, Cloud Run, Cloud Build or CI, docker-compose environments, integration or component test setup, repository authorization boundaries, service-to-service authentication, or secure internal operations.
Use when the user wants Google Forums search results through Frevana, including forum-style discussions from Google's Forums tab, Reddit/Quora/community results, localized country/language results, device-specific forum results, pagination offsets, or date-bounded forum searches.
Guide to the Google Gemini API using the current @google/genai SDK v1.27+, not the deprecated @google/generative-ai (sunset November 2025). Covers text generation, streaming, multimodal input (images, video, audio, PDFs), function calling including parallel and compositional calls, system instructions, multi-turn chat, thinking mode, generation parameters, context caching, built-in code execution, grounding with Google Search, error handling and rate limits, plus accurate 2025 model facts (Gemini 2.5 Pro, Flash and Flash-Lite with 1M input tokens, not 2M). Use when integrating Gemini, building multimodal or chat applications, deploying Gemini calls to Cloudflare Workers, migrating off @google/generative-ai, or debugging model not found, context window, function calling, or multimodal format errors. Embeddings live in the google-gemini-embeddings skill.
Fetches Google Trends data including daily trending topics, real-time trends, interest by region, related topics, related queries, and autocomplete suggestions. Use when the user asks about trending searches, search popularity, keyword trends, or Google Trends data.
Use when managing multiple Google Play apps with GPC. Make sure to use this skill whenever the user mentions multiple apps, multi-app, monorepo, white-label, batch operations, bulk upload, several apps, --app flag, app switching, profiles for different apps, fleet management, app portfolio, multiple package names — even if they don't explicitly say 'multi-app.' Also trigger when someone has more than one Android app and wants to manage them efficiently, when they need different configurations per app, when they're running the same command across multiple apps, or when they have a monorepo with multiple Android modules. For single-app setup, see gpc-setup. For CI automation, see gpc-ci-integration.
Use when dealing with GPC credential security, secret management, audit logging, or access control. Make sure to use this skill whenever the user mentions credentials, service account key, secret rotation, key rotation, credential storage, audit log, audit trail, security best practices, .gpcrc.json security, secrets in CI, GPC_SERVICE_ACCOUNT safety, keychain, token cache, credential leak, key compromise, secure deployment — even if they don't explicitly say 'security.' Also trigger when someone asks about where GPC stores credentials, how to rotate service account keys, how to audit who did what with GPC, how to securely pass credentials in CI/CD, or how to handle a compromised service account key. Also trigger on app signing key custody: app-signing enroll, app-signing rotate, Play App Signing, self-hosted Cloud KMS key, cryptoKeyVersion, signing certificate lineage, signing key rotation. For auth setup, see gpc-setup. For CI configuration, see gpc-ci-integration.
Use when monitoring Android app health metrics from Google Play. Make sure to use this skill whenever the user mentions gpc vitals, gpc watch, gpc status, crash rate, ANR rate, startup time, Android vitals, crash monitoring, threshold alerting, vitals gating, rollout monitoring, auto-halt, breach notification, webhook alerting, frame rate, battery usage, memory issues, error tracking, app quality, user reviews, review replies, Play Store reviews, star rating, negative reviews, review export, financial reports, stats reports, gpc reports, reports list, reports download, bulk reports, earnings report, sales report, play balance, installs report, subscriptions report, reports bucket, GPC_REPORTS_BUCKET, pubsite_prod, REPORT_ACCESS_DENIED, download bulk reports permission, or wants to check app health, monitor a staged rollout, respond to reviews, or download Play Console reports. Also trigger when someone asks about gating deployments on crash data, monitoring app performance after a release, watching a rollout for regressions, or tracking review sentiment — even if they don't mention GPC. For releases, see gpc-release-flow. For CI gating, see gpc-ci-integration.
Generate or edit raster images through the user's ChatGPT subscription and save or preview workspace PNGs. Use for text-to-image, local-reference generation, edits, follow-up revisions, transparent PNGs, variants, multi-image batches, or subscription-backed setup in Codex, Claude Code, Google Antigravity, and compatible local agents. Preserve direct prompts verbatim; develop distinct per-output prompts when the user delegates multiple concepts. Attach actual reference files. Use subscription-native OpenAI image_gen when available; otherwise use Codex CLI with ChatGPT sign-in. Never use the Images API, OPENAI_API_KEY, API-key login, or a different provider's image generator.
Migrate an entire Gradle Kotlin/JVM project to Kotlin Toolchain — module.yaml + project.yaml, dependency-catalog reuse, CI rewrite, and local plugins replacing Gradle plugins with no Toolchain equivalent. TRIGGER when converting, migrating, or porting a whole Gradle project (build.gradle/.kts, Gradle wrapper) to Kotlin Toolchain or Amper, not just one plugin; when replacing Gradle plugins (`application`, axion-release, jib, detekt/ktlint, custom `processResources`/codegen); when adapting CI (`./gradlew build`/`check`/`release`) to `./kotlin` commands; when translating `gradle/libs.versions.toml`, including `[bundles]`; when `buildSrc`/`build-logic` or `allprojects`/`subprojects` must become module templates. SKIP for porting one Gradle plugin (`gradle-to-kotlin-toolchain-plugin`), authoring a new plugin (`kotlin-toolchain-plugin-authoring`), and general Toolchain work with Gradle already gone (`kotlin-toolchain`).
Analyze code dependencies, call graphs, and architecture using the graph-it CLI. Use this skill whenever the user wants to understand how their code is connected — even if they don't say "dependency graph" explicitly. Trigger for: "what calls this function", "who uses this class", "is it safe to delete X", "what breaks if I change Y", "show me the architecture", "trace the execution from main", "find circular imports", "give me an overview of this module", "what imports this file", "impact analysis", "refactoring safety", "review this PR", "review this diff", "is this change risky", breaking changes, unused exports, dead code detection, codemap, file logic, module resolution, graph-it, dependency graph, reverse dependencies.
GraphQL schema design and review. Use when designing new GraphQL schema changes (types, mutations, queries, connections, enums, errors), reviewing schema diffs, planning schema evolution, or auditing nullability and naming. Triggers on 'graphql schema design', 'design a mutation', 'design a query', 'design a type', 'new type', 'new mutation', 'review schema', 'review schema diff', 'schema review', 'schema evolution', 'audit the schema', '/graphql-schema-design'.
Clarify product, domain, scope, constraints, business rules, and technology decisions through dependency-aware question sets. Read the repository first, ask all useful questions whose prerequisites are already known in each set, and use the answers to form later sets. Use when a project or feature is ambiguous and not ready for specification. When decisions are stable, recommend exactly one next skill without invoking it.
Build or review SvelteKit animation on Svelte 5: GSAP page transitions, component enter/exit, scroll effects, route reuse, and cleanup. Use for interrupted navigation or choosing GSAP, Svelte transitions, or View Transitions, even when GSAP is unnamed. Also covers hidden-content recovery and first-load performance. Not for plain Svelte or isolated GSAP API questions
Inspects and plans work with Gtars, the Rust/Python/CLI toolkit for genomic intervals: BED RegionSet set algebra (reduce, setdiff, intersect, closest, cluster, gaps), overlap counts, consensus peak sets, coverage, tokenizers, fragment processing, and refget/BEDbase stores. Use when merging or comparing BED interval sets, building a consensus or universe from peaks, tokenizing regions for ML models, working with fragment files, or planning refget sequence-collection and BEDbase cache use. Use when checking BED coordinates, contigs, or strand before running gtars. Not for general BAM/VCF processing; use samtools or bedtools for that.
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.