Skills
101,323 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Use when deploying a database to Zeabur. Use when the user needs MySQL, PostgreSQL, MongoDB, or Redis. Use when the user says “I need a database,” “add database,” “deploy postgres,” “set up MySQL,” “add Redis,” “add MongoDB,” or “connect to database.” Also use when the user mentions data persistence issues such as “data lost after restart,” “data not saved,” “data disappears,” “need persistent storage for data,” or “how to persist data.” Also use when integrating a database with an existing service.
Lint and typecheck debt paydown: clear pre-existing repo-wide lint/type violations and suppressions (@ts-ignore, # type: ignore) one rule per wave, fixing causes not symptoms. Runs on green main. For diff-scoped quality use absolute-simplify. Triggers on “absolute debt”, “fix our lint warnings”, “clear the type errors”, “get to strict mode”, “burn down suppressions”.
Find, evaluate, and assemble the smallest compatible set of AI Agent Skills for an end-to-end natural-language goal. Use when a user wants Skills for a multi-step workflow, asks which Skills fit a project, needs an installed-Skill audit or conflict check, has low Skill recall, wants indirect helpers such as humanizers or compliance checks, or wants a project-specific Skill Stack with controlled installation. Search local Skills, registries, GitHub, and OpenCLI; compare adoption, verified fit, safety, and overlap. Do not use for locating one known or common Skill; use the generic find-skills workflow.
When the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products.
Manage the full lifecycle of ADBPG Supabase projects. Use for listing or querying projects, creating, pausing/resuming, resetting passwords, managing API Keys, and security IPs. Triggers: “Supabase,” “supabase project,” “spb-xxx,” “ADBPG Supabase”
Analyzes events through anthropological lens using cultural analysis, ethnographic methods, kinship and social organization, symbolic systems, ritual and practice, and comparative ethnology. Provides insights on cultural meanings, social practices, symbolic structures, cultural change, and cross-cultural patterns. Use when: Cultural conflicts, identity issues, ritual significance, symbolic meanings, cultural change, cross-cultural comparison. Evaluates: Cultural systems, symbolic meanings, social practices, kinship structures, cultural adaptation, power-culture nexus.
ArkType runtime validation with TypeScript-native syntax. Type-safe schemas using string expressions, morphs, scopes, and generics. Includes ArkEnv for type-safe environment variable validation with auto-coercion and a Vite plugin. Use when defining schemas, validating data, transforming input, building type-safe APIs with ArkType, or validating environment variables with ArkEnv.
Query the Semantic Scholar academic corpus through AI2's Asta MCP server: keyword or title search with venue and date filters, who-cited-a-paper traversal, author profiles and publications, DOI/arXiv/PMID lookup, and ~500-word full-text snippets for evidence, with citation counts and h-index. Use when the user asks for papers on a topic, who cited a paper, an author's work, recent literature since a date, or a venue-scoped paper list. Requires the Asta MCP server.
Use this skill when a Compose tree uses SubcomposeLayout, BoxWithConstraints, or Scaffold and the developer reports extra measure passes, slow first frame, or layout passes running content composition repeatedly. Covers why SubcomposeLayout composes its slots during the measure phase, why BoxWithConstraints forces a subcomposition for every new Constraints value, why nesting Scaffold or BoxWithConstraints multiplies the cost, when a custom Layout or Modifier.layout { } replaces SubcomposeLayout, and how to use SubcomposeLayoutState's slot reuse policy and precompose APIs when SubcomposeLayout is genuinely required. Use when the developer mentions BoxWithConstraints, SubcomposeLayout, Scaffold, "extra measure pass", "double measurement", "first frame slow", "subcompose", or notices that wrapping content in BoxWithConstraints regresses scroll perf inside a LazyColumn.
Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, and Identity Center.
Generate Bruno API collections, request files, environments, and request documentation from backend source code, route definitions, OpenAPI snippets, pasted API docs, curl commands, or endpoint lists. Use when a user asks to create, scaffold, convert, organize, or improve Bruno collections, opencollection YAML files, .bru files, folders, request docs, request metadata, environments, or API-client collections for Bruno.
Query and summarize CawPlan QA Insights A3 TestRail execution progress for a Version or Run: execution rate, pass quality, deduplicated failure/blocker queue, and per-Ticket progress tables. Use when: A3 execution progress, test execution summary, TestRail run progress, execution summary, failure list, pass rate, untested count, status counts, custom status, 查询A3执行进度、查询Version测试进度、查询TestRail Run进度、执行摘要、失败列表、通过率、未执行统计、全status统计。 NOT for: importing test cases, creating TestRail Plans/Runs, filing defects (use `cawplan-defect-ticket`), or release risk assessment.
A layer between the human and agents: turns the human’s word into action, decisions into a graph, and work into units; handles blocked and empty spots, a bottom-up filter, and human choice. Triggers: “take the post”, “separate the work”, “launch agents”, “who is up”, “who else to raise”, “assign a task to agents”, “accept the work”, “plan in waves”, chief of staff, run a crew. Appointed by the human’s word: standing, watch, introduce yourself. Execution outside the graph belongs to units; each person holds their own part of the graph. Composes standing, minding, writing, inquiry. Requires iskron_*
Review a diff or file through the Chisle lens: flag over-engineering, speculative abstractions, reinvented stdlib, and verbose code that a lazier approach would shrink. One finding per line, no praise. Use when the user says "chisle review", "review this for bloat", or invokes /chisle-review.
Design and build agent-first CLIs with HATEOAS JSON responses, context-protecting output, and self-documenting command trees. Use when creating new CLI tools, adding commands to existing CLIs such as joelclaw, or reviewing CLI design for agent-friendliness. Triggers on 'build a CLI', 'add a command', 'CLI design', 'agent-friendly output', or any task involving command-line tool creation.
Use after running CodeceptJS tests with the `aiTrace` plugin enabled and the results need review — verify a fix held, investigate a single failure, cluster errors across a CI fail-storm, diagnose flakiness across reruns. Invoked by other CodeceptJS skills whenever a run has happened. Trigger on "what failed", "analyse the run", "cluster these errors", "is it flaky", "did the fix hold".
Automatically create multiple background tasks in Codex App for complex, parallelizable knowledge work or programming tasks, with configurable models and reasoning effort. The main Agent handles planning, delegation, integration, and acceptance. Use for multi-source research, multi-chapter content, complex Skills/PPTs, cross-module development, independent verification, or 2+ independent workflows. Also use when the user explicitly requests model routing, background Workers, an Agents Team, or persistent project collaboration. Do not trigger automatically for simple Q&A, status checks, small single-file edits, strictly sequential tasks, or publishing/payment/deletion/account operations.
Collect volatile forensic evidence from a compromised host by following the order of volatility, preserving memory, network connections, running processes, and system state with documented chain of custody before they are lost. Use before isolating, shutting down, or remediating a compromised host, especially when fileless or memory-resident malware is suspected, root cause analysis is needed, or the evidence must hold up in legal proceedings
Launch Proteina-Complexa pipelines on a remote SLURM cluster — binder search, LaProteina monomer design, or multi-node distributed training. Reach for this skill whenever the user says "launch on SLURM", "submit to the cluster", "submit binder search to SLURM", "kick off training on the cluster", "multi-node training", "cluster job", "sbatch", "remote GPU run", "complexa slurm", "launch_protein_binder_search.sh", "launch_laproteina_train.sh", "launch_laproteina_design_pipeline.sh", "launch on grizzly / polar", "--on-cluster", "run distributed training", "sweep on SLURM", "run all targets on the cluster", "kick off a multi-target binder search", "rsync to cluster", "submit a singleton requeue chain", or whenever a Hydra config / sweep needs to escape a single workstation. This skill drives the launcher scripts under `slurm_utils/`, **always previews with `--dry-run` first**, then submits, captures SLURM job IDs, and emits a replayable manifest. SLURM submission costs cluster time and is hard to reverse, so the dry-run gate is non-optional.
Use Orca's computer-use CLI to inspect and operate local desktop app windows through accessibility trees, screenshots, and safe UI actions. Use for desktop app interaction: list apps/windows, get app state, read visible UI, click controls, type, press keys, scroll, drag, set values, or perform accessibility actions. Also use for browser windows, webviews, Orca app UI, or other desktop UI. Triggers include "computer use", "orca computer", "read Spotify", "read Slack", "control/click/read in a desktop app", and "get app state".
Debug and support PostHog Experiments (A/B tests) for a customer looking at their own results. Use whenever an experiment support ticket is pasted or a customer asks a results question, most commonly "why aren't my exposures even?", "why is one variant getting no traffic?", "why am I missing / seeing too few exposures?", "why does the bias banner show?", or "why don't PostHog's numbers match my SQL?". Pulls the experiment's real data read-only, matches it to a known-cause catalog, and produces a customer-facing explanation, fix, and review of the pertinent numbers. Loads diagnosing-experiment-health as its deep diagnostic library. DO NOT TRIGGER when: creating an experiment (use creating-experiments), only configuring rollout (configuring-experiment-rollout) or metrics (configuring-experiment-analytics), asking lifecycle questions (managing-experiment-lifecycle), or the underlying feature flag is what's misbehaving rather than the results (use debugging-feature-flags).
Deep research and analysis tool. Generates comprehensive HTML reports on any topic, domain, paper, or technology. Use when user asks to research, analyze, investigate, deep-dive, or generate a report on any subject. Supports academic papers (arXiv), technologies, trends, comparisons, and general topics.
SolidJS adapter for the json-render devtools inspector. Use whenever the user wants to add, configure, or troubleshoot @json-render/devtools-solid in a SolidJS json-render app, including spec inspection, state editing, action and stream timelines, catalog browsing, or DOM picking.
Use whenever writing, editing, restructuring, or reviewing technical documentation — READMEs, API docs, guides, tutorials, reference, onboarding, or developer docs of any kind — to apply the Diátaxis framework, which splits content into four modes (tutorials, how-to guides, reference, explanation) that each serve a distinct user need. Trigger even when the user just says "write docs", "document this", "improve the README", or "our docs are confusing" without naming Diátaxis or documentation types. Use it to decide WHAT KIND of doc to write (via the compass), to diagnose docs that feel bloated, mix instruction with reference, or leave users unable to get started or find facts, and to improve docs in small safe iterations. Especially when you are unsure whether something belongs in a tutorial vs how-to vs reference vs explanation, or when one page is trying to do all four at once.
Use this skill when the user is dealing with the DOCA environment around their workload—verifying an install is healthy; preparing the build environment (pkg-config, headers, LD_LIBRARY_PATH, hugepages, devlink, representors); debugging environment-related failures; deciding between container and bare-metal deployment; or reaching a DOCA installation from a host without one via the NGC DOCA container Stage-1 fallback. Trigger even when the user does not explicitly mention “DOCA setup.” Typical implicit phrasing includes “just got a BlueField, what now,” “code is built, how to run it,” “pkg-config can’t find doca-flow,” “no free 2048 kB hugepages,” “representor X not found,” or “on a Mac and want to learn DOCA.” Refuse and route elsewhere for library API specifics (Flow pipes, RDMA queues), the modify-a-sample first-app workflow or program-side DOCA_ERROR_* debugging, and “where is X documented” knowledge-map questions—those belong to other skills
Routes .NET/C# requests to the correct domain skill and loads coding standards as baseline for all code paths. Determines whether the task needs API, UI, testing, devops, tooling, or debugging guidance based on prompt analysis and project signals, then invokes skills in the right order. Always invoked after `using-dotnet` detects .NET intent. Do not use for deep API, UI, testing, devops, tooling, or debugging implementation guidance.
Scaffolds Drizzle ORM + SQLite boilerplate: a new `drizzle.config.ts`, a singleton client with the right pragmas, per-table schema files with explicit primary keys/indexed foreign keys/relations()/inferred types, per-table repository modules with `.returning()` + `inArray()` + `.onConflictDoUpdate()`, or drizzle-zod validators. Produces convention-enforced templates for three drivers (better-sqlite3, libsql/Turso, bun:sqlite). Trigger even when the user doesn't say "scaffold" — phrases like "add a table for X", "set up Drizzle in this project", "wire up SQLite", "create a CRUD module for X", or "bootstrap the DB layer" should pull this in. Pairs with the `drizzle-sqlite` skill, which covers the 45 rules these templates encode — read it when an exception is required
ALWAYS USE THIS SKILL to create, check the status of, list, or delete scratch org snapshots. A snapshot is a point-in-time copy of a scratch org's metadata AND data, referenced by name in the `snapshot` field of a scratch org definition file. Use when the user asks to create/take a snapshot, check a snapshot's status or creation progress, list/show/view existing snapshots (including filtering for snapshots expiring soon), or delete/remove a snapshot. Requires a Dev Hub with Scratch Org Snapshots enabled. DO NOT TRIGGER for creating org shapes (use dx-org-shape-manage) or for creating scratch orgs, including from an existing snapshot via `--snapshot` (use dx-org-manage).
Use when a factual claim or assertion needs verification — a targeted claim verification pipeline: search multiple independent sources, cross-check for agreement or contradiction, rate confidence (verified / likely true / disputed / unverified / outdated), and produce a cited verification report.
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
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.