Skills
99,719 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Pick the concurrency model from the workload shape — rayon for data parallelism, scoped threads for borrowed stack data, channels for handoff, shared state last — and use the weakest correct atomic ordering. Use when writing or reviewing threaded Rust, when Mutex, RwLock, atomics, or manual Send/Sync appear, when a deadlock or data race is suspected, or when the user asks how to parallelize Rust code.
Move Rust game monsters, items, loot, effects, spawn weights, level gates, and balance numbers into validated data files using Serde-friendly schemas. Use when replacing hard-coded spawn functions, adding RON or JSON content templates, or making game content editable without recompiling.
Finish and package small Rust games with MVP lock, playability checks, resource packaging, release builds, smoke tests, and disciplined post-MVP polish. Use when preparing a Rust game prototype for sharing, packaging bracket-lib assets, or deciding what finishing work belongs before release.
Design and review Rust roguelike procedural maps, map-builder traits, generator harnesses, field-of-view, spatial memory, Dijkstra/pathfinding, and simple monster AI. Use when adding dungeon generation, FOV, map memory, chasing behavior, or visibility-constrained AI to a Rust game.
Design and review Rust tile maps, map indexing, collision checks, map builders, camera-relative rendering, layered drawing, and tile themes. Use when building 2D grid worlds, roguelike maps, tile cameras, or bracket-lib style rendering systems.
Build and review turn-based Rust game flow using turn-state enums, phase-specific schedules, intent messages, movement resolution, combat resolution, wait actions, and win/loss states. Use when implementing roguelike turns, tactical action order, ECS message entities, or decoupled input and action systems.
Set up GitHub's `safe-settings` (a Probot-based GitHub App from the github org) for declarative, org-wide repository policy as code. Use when the user says "settings as code", "safe-settings", "manage repos declaratively", "centralize repo settings", "org-level branch protection", "scaffold an admin repo", "github settings app", or invokes /safe-settings on an org that wants to manage repo settings, branch protection, rulesets, labels, teams, environments, and collaborators from one admin repo. Scaffolds the admin-repo layout (`settings.yml` + `suborgs/` + `repos/`), the GitHub App installation steps, and a scheduled `full-sync` GitHub Actions workflow. Distinct from /gh (per-task ops) and /gh-bootstrap (one-shot `gh api` config of a single repo) — this skill is for **org-scale settings as code** that reconciles continuously.
Design and optimize a sales funnel for a solopreneur business. Use when mapping how customers move from first awareness to paying customer, identifying where leads drop off, building or improving any stage of the funnel (awareness, consideration, decision, retention), or optimizing conversion rates. Covers funnel architecture, stage-by-stage tactics, conversion benchmarks, solopreneur-specific funnel models (self-serve vs. high-touch), and funnel analytics. Trigger on "sales funnel", "design my funnel", "optimize my funnel", "conversion funnel", "why aren't people buying", "lead to customer", "funnel stages", "improve conversions".
Hunter.io platform help — Domain Search, Email Finder, Email Verifier, Campaigns, Discover, Signals, TechLookup, Leads, browser extension, API, integrations, MCP server. Use when email addresses are bouncing, need to find emails for a domain, Hunter verification results seem wrong, campaign sequences aren't sending, Discover or Signals data looks incomplete, integrations aren't syncing, or API calls aren't returning expected data. Do NOT use for building prospect lists (use /sales-prospect-list), designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or enriching contacts across multiple tools (use /sales-enrich).
This skill should be used when users request code review, refactoring, or code quality improvements for Ruby codebases. Apply Sandi Metz's four rules for writing maintainable object-oriented code - classes under 100 lines, methods under 5 lines, no more than 4 parameters, and controllers instantiate only one object. Use when users mention "Sandi Metz", "code quality", "refactoring", or when reviewing Ruby code for maintainability.
Audit a Scala file or codebase for refactoring opportunities — Scala 3 modernization, idiom adoption, anti-pattern removal, performance hygiene, tail-recursion safety, and migration cleanup. Produces educational, documentation-backed findings as suggestions only, never editing the file in place. Use this skill whenever the user asks to refactor Scala code, modernize Scala 2 to Scala 3, find Scala anti-patterns, optimize Scala performance, review Scala idioms, apply opaque types, replace value classes, convert sealed traits to enums, migrate implicits to given/using, audit a `.scala` file, or do anything involving cleaning up or improving Scala code — even if they don't explicitly say "audit" or "refactor". Trigger on phrases like "review my Scala", "modernize this Scala", "make this idiomatic Scala 3", "find issues in this Scala file", "check for Scala anti-patterns", or any pasted Scala code accompanied by a request to improve, clean, optimize, or modernize it.
Scene Feedback surveys for Decentraland SDK7 playtests: plan questions and timing, organize test rounds and find testers, integrate or debug the module, or analyze exported CSV ratings and comments. For audiovisual reactions to gameplay actions, use add-interactivity, audio-video or build-ui.
Autonomous browser control via Chrome DevTools Protocol and Accessibility Tree for full screen control like GPT Operator. Use when user requests "control my screen", "verify Lovable", "test scrapers", "debug DOM", "autonomous testing", or any browser automation task. NO screenshots - uses CDP + semantic queries for 10x faster, 100% reliable element targeting.
Write scripts for vertical short dramas, film/TV, or radio dramas in standard screenplay format. Use when users want a script, short drama, episodic script, a novel adapted into a script, a dialogue script, or ask how to write or format a screenplay. Default to vertical short-drama style; include only what can be filmed (actions, dialogue, sound effects), no psychological descriptions, and end every episode on a strong hook.
SDD fast path. Runs the full pipeline — analyse → plan → implement → review → archive — with a single confirmation gate before implementation begins. Stops automatically if Critical or Major issues are found in review. Use when you want to ship a well-understood feature with minimal interruptions.
Only use when the user explicitly invokes /search-history (or $search-history in Codex). Never auto-invoke. Cross-searches the local chat history (JSONL) of Claude Code / Codex CLI by keyword and presents the matching sessions and conversation fragments. History files are treated as read-only.
Assess and harden LLM applications and agentic systems against prompt injection, tool misuse, excessive agency, memory poisoning, RAG data leakage, and model supply-chain risk, mapped to the OWASP Top 10 for LLM and Agentic Applications. Use when reviewing an AI feature, agent, MCP server, or RAG pipeline for security, or when threat modeling an autonomous system.
Main Figma orchestration skill for the UI/UX skill system. Use this skill whenever the user asks to read Figma design context, turn Figma frames into implementation plans or code, sync live UI back to Figma, edit Figma canvas objects, manage variables/components/assets/effects, audit Figma MCP workflows, or coordinate Figma work under $senior-ui-ux-orchestrator. Routes to figma-context-reader, figma-design-to-code-bridge, figma-code-to-canvas, figma-canvas-editor, figma-design-system-sync, figma-assets-manager, figma-apply-effects, and figma-workflow-auditor while enforcing privacy, tool availability, and evidence boundaries.
Guided entry point for using Sentry through your agent. Orients you to your current setup and, for a new project, sets up Sentry end to end with sane defaults — provision a project, install the SDK (errors, tracing, and whatever it enables by default), and confirm real telemetry reaches Sentry. Routes other intents (adding more signals, fixing issues) to the right skill.
Configure the Serena MCP server — its global defaults and a repo's per-project settings. Use when the user says "configure serena", "set up serena for this repo", "serena project config", "serena global config", "tune serena for this codebase", "edit serena_config.yml", "edit project.yml", "monorepo serena", "serena picked the wrong language", "serena is indexing vendor/node_modules", "make serena read-only here", "serena contexts and modes", "what context for claude-code", "disable serena memory/onboarding", "point serena at my installed language server", "ls_specific_settings", "ls_path", "SERENA_HOME", or "move the .serena folder". Routes per-repo `.serena/project.yml` questions to `references/project-config.md` and machine-wide `~/.serena/serena_config.yml` (settings, contexts, modes, language-server tuning) to `references/global-config.md`. Do NOT use for general "use serena to find / edit X" routing — that is an MCP-routing concern, not configuration.
Configure settings on an existing Enhanced `MessagingChannel` of any type—WhatsApp, Text/SMS, LINE, Apple, Facebook, or EmbeddedMessaging—given its `{CHANNEL_ID}`. Covers five areas: consent (ConsentType and per-language keyword records), automated responses, messaging keywords, session inactivity timeouts, and pre-chat parameters. Consent and a matching language-keyword record are required for the activation readiness check. Trigger when setting or changing settings on an existing channel (opt-out keyword, consent type, double opt-in confirmation, initial/help auto-responses, OptIn/OptOut keywords, session inactivity timeout)—typically between insertion/routing and activation, or on a live channel. Do not trigger for creating a new channel (`service-de-channel-create`), deploying a MIAW/EmbeddedMessaging channel from metadata XML (`service-digital-engagement-channel-configure`), setting routing (`service-de-channel-routing-configure`), or activating a channel (`service-de-channel-activate`)
Apply Whispering service-boundary patterns for UI-free capabilities, explicit inputs, Result fallibility, Live objects, lifecycle factories, and platform variants. Use when creating or refactoring services, contracts, provider dispatch, or the `$lib/services` barrel.
Set up and connect a new Coval agent for evaluation. Guides through agent type selection, endpoint configuration, system prompt, and default resource attachment. Use when user says "set up an agent", "connect my agent", "create an agent", "add an agent", or "configure agent endpoint".
Take a PR from review to merged — run the repo's code-review skill on it in a loop (review, fix, re-review) until nothing is left to fix, applying ALL fixes on the PR branch, wait for CI green, then squash-merge. Use when asked to "ship it", "ship PR #N", or "review, fix and merge" a PR.
Shopify platform development. Stack: Shopify CLI, GraphQL/REST APIs, Polaris UI, Liquid templating. Capabilities: app development (OAuth), checkout UI extensions, admin UI extensions, POS extensions, theme development, webhooks, billing API, product/order/customer management. Actions: build, extend, customize, integrate Shopify apps/themes. Keywords: Shopify, Shopify CLI, GraphQL Admin API, REST API, Polaris, Liquid, checkout extension, admin extension, POS extension, theme, webhook, billing API, OAuth, app bridge, metafields, product, order, customer, storefront, hydrogen, oxygen. Use when: building Shopify apps, customizing checkout, creating admin interfaces, developing themes, integrating payments, managing store data via APIs, extending Shopify functionality.
Use when the user wants to manage a shoplazza store's product catalog through the CLI — creating / publishing / unpublishing products (建品 / 新建商品 / 上新 / 上架 / 下架), searching or counting the catalog (搜商品 / 找商品 / 商品数量 / how many products I sell), changing prices (改价 / 调价 / set price), adjusting stock (库存 / 补货 / 加库存 / 减库存 / inventory), product tags (标签), variants / SKUs (变体 / 规格), collections and collects (商品合集 / 商品分组), product images (商品图片 / 主图), gift cards (礼品卡 / 储值卡 — gift cards live HERE, not in discounts), customer product reviews (买家评价 / 评论 / product reviews), warehouse locations (仓库 / 库位), suppliers and procurement (供应商 / 采购单 / 进货). NOT discount codes / coupons / 优惠码 / 折扣码 / 满减 (→ shoplazza-discounts); NOT the store media library / file uploads / 媒体库文件 and NOT metafields / 元字段 (→ shoplazza-shop); NOT order fulfillment / 发货 (→ orders domain); NOT theme card images / 装修配图 / 商品详情页模板 (→ shoplazza-themes)
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Create or review a reusable skill (SKILL.md) that packages a workflow, and decide whether the request should be a skill instead of a prompt, instruction, agent, or hook. Use when creating a new skill, extracting a workflow from a conversation, updating an existing skill, reviewing SKILL.md quality, or fixing weak skill triggering. Triggers on "create skill", "/create-skill", "new skill", "review skill", "fix skill trigger", "SKILL.md", "スキル作成".
Executing SQL, managing Snowflake objects, deploying applications, and orchestrating data pipelines using the Snowflake CLI (snow) command. Use this skill when you need to run SQL scripts, deploy Streamlit apps, execute Snowpark procedures, manage stages, automate Snowflake operations from CI/CD pipelines, or work with variables and templating.
Spring Boot testing fundamentals including @SpringBootTest, slice tests, MockMvc, mocking with @MockBean, test configuration, and testing utilities. For integration tests with Testcontainers, see spring-boot-integration. USE WHEN: user mentions "spring boot test", "mockmvc", "@WebMvcTest", "@DataJpaTest", asks about "@SpringBootTest", "@MockBean", "spring test", "controller test", "repository test" DO NOT USE FOR: Unit tests - use `junit` with Mockito; Integration tests with real DB - use `spring-boot-integration`; REST API clients - use `rest-assured`; E2E tests - use Selenium
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.