Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Use when you need to understand the positioning, capabilities, architecture or integration flow of the Ziniao browser WebDriver automation interface, for design discussions, integration planning or tool evaluation. Do not use it to write concrete automation scripts — when executing, refer directly to the interfaces and examples in reference/.
Use when the user wants to build a CLI tool to automate browser interactions on a specific website using kimi-webbridge. Invoke when user says "create a CLI for X site", "build a tool to automate X", or wants to control a website programmatically via an AI agent.
EXPERIMENTAL. Use when looking for meaningfully duplicated logic in a codebase, especially duplicate behavior hidden behind different names, different syntax, different control flow, or independently evolved implementations. Not for style issues, not for syntactic clone detection, and not for fixing what it finds.
Create, audit, or trim AGENTS.md and its harness mirrors (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, .cursor/rules) so build/test commands stay accurate and the file stays under each harness's size cap. Use when the user says "create AGENTS.md", "audit AGENTS.md", "trim AGENTS.md", "AGENTS.md is stale", "CLAUDE.md drift", "agent instructions hygiene", or invokes /agents-md. Covers nested AGENTS.md for monorepo packages, nearest-file precedence, and the bundled scripts/agents_md_check.py measurement script. Do NOT use for `.github/copilot-instructions.md` authoring or Copilot code-review configuration — that is /github-copilot-repo-instructions. Do NOT use for personal, per-user, or machine-global instruction files (`~/.claude/CLAUDE.md`, personal Copilot instructions) — those are out of scope for this repository-scoped skill.
API documentation specialist who creates comprehensive OpenAPI/Swagger specifications and technical documentation for RESTful APIs, GraphQL schemas, and microservices architectures. Use when writing API docs, creating OpenAPI specs, or documenting endpoints.
Use to develop a feature or bug fix end-to-end through a TDD git-worktree workflow — interactively (developer-led) or unattended (autonomous-mode, driven by the dispatcher). Triggers on phrases like "implement issue #N", "fix this bug", "add a feature", "create a worktree", "write test cases", "push and open a PR", "check CI", "address review comments", "resolve review threads", "/q review", "/codex review", "implement this autonomously", or any partial step in the design → worktree → tests → implement → verify → review → PR → CI → E2E lifecycle. Interactive mode asks for decisions; autonomous mode makes decisions per autonomous-mode.md and posts progress comments to the GitHub issue.
Draft local Azure DevOps work item packets from loose context using the known project process, with Scrum PBI as the fallback when type and process are unknown. Inspect repo context when present. Do NOT use for live REST/CLI creation, migration, wiki, or status reporting.
Retrieve and search logs from B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to view server logs, search for errors, filter log entries by level or time, or monitor logs in real-time. Also use when the user reports a 500 error, broken checkout, failing job, or any server-side issue that needs log investigation — even if they just say "something's broken on the sandbox" or "check the logs".
Amazon-style Working-Backwards PRFAQ: a future press release plus internal and external FAQs that stress-test a product concept before any building begins. Produces prfaq.md in the configured output folder. Use when the user says: "write a PRFAQ", "working backwards", "press release", "future press release", "stress-test the concept", "validate the idea before building", "internal FAQ", "external FAQ", "Amazon-style product brief", or "PRFAQ for [product/feature]". Also use when someone wants to clarify or update an existing PRFAQ, or validate a draft against the Working-Backwards criteria. Supports three intents: Create / Update / Validate.
Report stale git branches with a keep, archive, or delete recommendation, and propose enabling delete-branch-on-merge. Use for "clean up stale branches", "delete merged branches", "delete branch on merge", "which branches are dead", or /branch-cleanup. Checks age, author, ahead/behind counts, merged status, open pull requests, and ruleset protection, then prints exact deletion commands that require explicit per-batch authorization before any push. Do NOT use for local git worktree management (worktree add, list, or prune) — that stays out of scope. One-time repository merge defaults and branch-protection rulesets belong to /gh-bootstrap; this skill reads and reports on that state but does not set it up.
Go performance analysis expert. Analyzes CPU/memory performance bottlenecks, gives high-performance coding advice, and optimizes GC/allocator/compiler/cache performance. Covers benchmark, pprof, escape analysis, compiler optimizations (BCE/inlining), concurrency performance, memory layout, CPU cache friendliness, data-driven optimization methodology, and performance differences across Go versions. Trigger words: Go performance, benchmark, pprof, memory allocation, escape analysis, compiler optimization, inlining, BCE, bounds check, CPU cache, cache line, false sharing, sync.Pool, GC optimization, GOGC, compiler optimization, performance analysis, pprof profiling, benchstat, allocation optimization, stack vs heap, string concatenation performance, slice preallocation, struct layout optimization, concurrency performance, Go performance, profile, escape analysis, optimization advice.
Expert in building Command Line Interfaces (CLIs), Terminal User Interfaces (TUIs), and shell automation tools. Use when creating CLI applications, building interactive terminal UIs, parsing command-line arguments, or developing shell scripts and automation tools.
Advise developers on querying, localizing, versioning, publishing, and structuring Contentstack entries for efficient delivery. Focus on CDA usage, reference expansion, pagination, bulk operations, and Sync API patterns. Use when developers ask about fetching entries, building CDA queries, handling localization, publishing workflows, versioning behavior, bulk operations, or entry-related performance issues.
Performs semantic code intelligence and token optimization through context engineering and automated context packing. Use when reducing token overhead for large codebases, creating repository digests with Gitingest, packaging code context with Repomix, or tracing cross-file dependencies with llm-tldr.
Author, validate, and enforce a CODEOWNERS file: detect an existing file, gather ownership evidence from directory structure and git history, write or update rules with correct CODEOWNERS syntax, validate the file against the GitHub API, and wire the ruleset rule that requires code owner review on pull requests. Use when the user says "add CODEOWNERS", "who owns this path", "require owner review", "validate CODEOWNERS", or invokes /codeowners. Idempotent — safe to re-run; diffs before overwriting and never auto-assigns an owner without confirmation. Do NOT use for branch rulesets in general (use /gh-bootstrap) or community health files such as README, LICENSE, CODE_OF_CONDUCT, and SECURITY (use /oss-hygiene) — this skill only covers the CODEOWNERS file and the review rule it feeds.
Creates and registers Tambo components - generative (AI creates on-demand) and interactable (pre-placed, AI updates). Use when defining components, working with TamboComponent, withTamboInteractable, propsSchema, or registering components for AI to render or update.
This skill should be used when the user asks to "create a plugin", "make a GitHub plugin", "turn my repo into a plugin", "create a Claude Code plugin", "create a Codex plugin", "publish my skills as a plugin", or "set up a plugin marketplace". Scaffolds the complete file structure for a repo that works as both a Claude Code and Codex plugin with marketplace support.
Shared reference content used by other Datex Studio skills (report-creator, report-editor, function-creator, datasource-creator, endpoint-creator, hub-editor, branch-code-reviewer, commit-message-generator, release-notes-generator). Not invoked directly — other skills link into the files below. Install this alongside any Datex Studio skill so cross-skill references resolve. Covers: the canonical `dxs configuration` round-trip (get → extract `.json` → edit → upsert) and its silent-wipe guard, branch & connection selection, Studio lifecycle, designer context navigation, flow code patterns (`$utils.isDefined()`, OData pagination), RDLX-JSON report authoring (design standards, CLI commands, dataset rules, sample data, deploy patterns, troubleshooting), component-type references for cards (cti 11), lists (cti 14), and frontend flows (cti 27), and the Fluent 2 app design system (theme tokens, component class names, traps) for hand-authored UI.
TanStack DB core concepts: createCollection with queryCollectionOptions, electricCollectionOptions, powerSyncCollectionOptions, rxdbCollectionOptions, trailBaseCollectionOptions, localOnlyCollectionOptions. Live queries via query builder (from, where, join, select, groupBy, orderBy, limit). Optimistic mutations with draft proxy (collection.insert, collection.update, collection.delete). createOptimisticAction, createTransaction, createPacedMutations. Entry point for all TanStack DB skills.
Diagnose Fireworks training and deployment issues, including stuck or failed jobs, error messages, poor quality, checkpoint and resume problems, LoRA adapter load mismatches, and deployments that are ready but not serving. Use for systematic read-only triage before retrying. Use configure for a new or approved retry run; use research when the starting method, data, or cookbook example is unclear.
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates. Covers bun, npm, pnpm and yarn. Use when packages were just upgraded and need validating, when deciding whether a held-back package can move, when asking why a dependency is present at all, or when checking release notes for breaking changes and migration steps. Not for picking and applying upgrades autonomously, bun CLI usage (bun-cli), or non-JavaScript package ecosystems
Reconcile Drupal configuration drift between a working tree and a deployed environment one item at a time, deciding import (disk wins) vs export (DB wins) vs skip for each difference. Use when `drush config:status` shows drift, after pulling a fresh DB, before a deploy, or when local config and a remote/prod environment disagree. Pantheon/Terminus-aware but works with any remote alias; never writes to production.
Native UI integration for Electrobun desktop applications including ApplicationMenu, ContextMenu, system Tray, native dialogs, keyboard shortcuts, and platform-specific UI patterns. This skill covers creating application menus with submenus and accelerators, context menus triggered by right-click, system tray icons with menus, file/folder dialogs, message boxes, notification systems, global keyboard shortcuts, menu item roles, dynamic menu updates, platform-specific menu conventions (macOS menu bar, Windows system menu), drag-and-drop integration, and native theming. Use when implementing application menus, adding system tray functionality, creating context menus, showing file pickers, implementing keyboard shortcuts, displaying notifications or dialogs, or building platform-native UI experiences. Triggers include "menu", "tray icon", "context menu", "file dialog", "shortcuts", "accelerator", "native dialog", "system tray", "notification", "menu bar", or "right-click menu".
Migrate to the next major version of @elevenlabs/client, @elevenlabs/react, and @elevenlabs/react-native. Use when updating code that uses Conversation, Input, Output, useConversation, ElevenLabsProvider, ConversationProvider, or related APIs from these packages. Also trigger when users mention upgrading ElevenLabs packages, fixing breaking changes after an npm update, moving to the latest ElevenLabs SDK, or encountering type errors or runtime errors after updating @elevenlabs/* dependencies.
ESPHome device configuration, firmware, and IoT product development. Covers ESP32, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2, ESP32-P4, ESP8266, RP2040, RP2350, nRF52, LibreTiny, Shelly, Sonoff, Tuya, BLE proxy, Matter firmware, Thread, Zigbee, GPIO, sensor YAML, LVGL displays, LED strips, voice assistant hardware, device flashing, Arduino conversion, alarm_control_panel, lock, valve, media_player, microphone, speaker, audio DAC, event entities, datetime entities, Z-Wave proxy, MIPI DSI displays, and DLMS smart meters. Also covers designing new ESPHome-based products: hardware selection, component sourcing, PCB design (KiCad), enclosures, 3D printing, CE/FCC certification, BOM optimization, and manufacturing from prototype to production scale.
Assess whether a specific Lightning web component can serve its user's purpose as an HXL declarative widget. Use for LWC-to-widget feasibility, portability audits, and candidate screening; use experience-lwc-widget-migrate when the user wants the widget built
Use this skill to read device logs for test failures, debug, smoke testing, and CI repros. Covers `adb logcat` (stream), `adb logcat -d` (dump and exit), `adb logcat -c` (clear), buffer selection (`-b main|system|crash|events|radio|kernel|all`), priority ladder (V/D/I/W/E/F/S), filter expressions like `MyApp:D *:S`, format flags (`-v threadtime`, `-v json` on Android 11+), `--pid $(adb shell pidof -s pkg)`, time/count filters (`-T '01-01 12:00:00.000'`, `-t 100`), buffer rotation (`-r <kbytes>`, `-n <count>`, `-f <file>`), buffer sizing (`-G`, `-g`), and stripping `Log.d` calls in release builds via R8 `-assumenosideeffects`. If the user mentions "logcat filter only my app", "events buffer am_proc_start", "logcat json format", "grep logcat expensive", "missing logs after restart", "stripping Log.d release", or "logcat -f writes to host or device", use this skill.
FastAPI Python framework. Covers REST APIs, validation, dependencies, security. Use when building Python web APIs with FastAPI, configuring Pydantic models, implementing dependency injection, or setting up OAuth2/JWT authentication. Keywords: FastAPI, Pydantic, async, OAuth2, JWT, REST API.
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
Run repeated build -> QA -> retro -> re0-work cycles while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.
Plans and runs game localization: i18n architecture, string extraction per engine, a machine translation + LLM + human review pipeline, pseudo-localization in CI, fonts, RTL and CJK, LQA, and Steam AI disclosure for translated text. Use for "localization", "translation", "i18n", "RTL", "CJK", "pseudo-localization". Not for writing dialogue (use game-narrative-director).
A GTK (GTK4/GTK3) UI/UX specialist that crafts beautiful, native-feeling desktop applications following GNOME Human Interface Guidelines. Use this skill when working with GTK widget composition, Libadwaita theming, CSS styling, accessible layouts, and modern GTK4 features like GtkListView, property bindings, and event controllers. Handles visual design decisions, layout composition, responsive designs, and theme-aware styling for Linux desktop applications.
Integrate InFlow stablecoin payments into any project. Use this skill when the user wants to: accept payments, add a checkout, request a payment, build a payment flow, integrate InFlow, accept USDC/USDT/EURC/PYUSD, set up consumer login via InFlow, register users with InFlow, handle payment webhooks, create spending policies for autonomous agents, build a 0-click headless payment flow, or add InFlow checkout to a marketplace app (note: native multi-recipient splits are not supported by the InFlow API). Also trigger on: 'add inflow', 'inflow payment', 'inflow checkout', 'stablecoin payment', 'crypto payment', 'accept stablecoins', 'pay with usdc', 'inflow webhook', 'inflow login', 'inflow policy'.
Use this skill when writing code that reads, writes, syncs, or reacts to data in an external app. Applies to SaaS products, internal tools, scripts, batch jobs, and CLIs. The skill uses Membrane as the integration engine — it handles OAuth and credential lifecycle (authentication, token refresh, reconnect), exposes vendor operations through a uniform interface, delivers events via webhooks, generates connectors on demand for apps not yet in the workspace, and captures every action run and raw API exchange in structured logs. Works against any external app.
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.