Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Cloud & DevOps
Alibaba Cloud ECS extension installation skill. Supports querying available extension lists, checking if a specific extension is available, and one-click installation of extensions (e.g., OpenClaw, BT Panel, Python environments, etc.). Extensions are officially provided by Alibaba Cloud with verified installation packages and scripts. Triggers: "extension", "install", "BT Panel", "OpenClaw", "Python", "Node.js", "package", "one-click install"
Expert knowledge for Azure Artifacts development, including troubleshooting, best practices, decision-making, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use for managing feeds, upstream sources, views, .npmrc auth, .artifactignore, GitHub Actions package publishing, and other Azure Artifacts development tasks. Not for Azure DevOps (use azure-devops), Azure Pipelines (use azure-pipelines), Azure Repos (use azure-repos), or Azure Boards (use azure-boards).
Expert knowledge for Azure Container Instances development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and deployment. Use when configuring ACI standby pools, static IP networking, GPU containers, secure ACR pulls, or GitHub Actions deploys, and other Azure Container Instances related development tasks. Not for Azure Container Apps (use azure-container-apps), Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure App Service (use azure-app-service), Azure Virtual Machines (use azure-virtual-machines).
Expert knowledge for Azure Load Balancer development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring backend pools/rules, SNAT/outbound, dual-stack IPv4/IPv6, health probes, or LB metrics/APIs, and other Azure Load Balancer related development tasks. Not for Azure Application Gateway (use azure-application-gateway), Azure Front Door (use azure-front-door), Azure Traffic Manager (use azure-traffic-manager), Azure Virtual Network (use azure-virtual-network).
Expert knowledge for Azure Resource Graph development, including troubleshooting, best practices, decision-making, limits and quotas, configuration, integrations, and coding patterns. Use when querying via CLI/PowerShell/REST, using GET/LIST vs. Query, handling paging and quotas, or creating Power BI ARG reports, and for other Azure Resource Graph development tasks. Not for Azure Monitor (use azure-monitor), Azure Policy (use azure-policy), Cost Management (use azure-cost-management), or Azure Resource Manager (use azure-resource-manager).
Wire a nao project's context folder to a remote nao instance (Cloud or self-hosted) so every push to `main` automatically runs `nao deploy` via GitHub Actions. Use when the user has a working local nao project versioned in Git and wants their team's deployed instance to always reflect the latest committed context. Covers `nao deploy` usage, the GitHub Actions workflow, organization API keys, GitHub Secrets, `.naoignore`, environment-variable references in `nao_config.yaml`, and create-vs-update behavior. Do not use for first-time project setup (use `setup-context`) or for `nao sync` automation that commits warehouse metadata back to the repo (covered in the docs' synchronization page)
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.
Release and compliance role for Phaser 4 mobile 2D games. Use when preparing builds, store listings, privacy materials, asset licensing, submission checklists, and release candidate packages for mini-games, iOS, Google Play, or new channels.
Twilio CLI reference for managing Twilio resources from the terminal. Covers installation, credential profiles, phone number provisioning, sending SMS and email, webhook configuration, local development with a tunneling service, debugging with watch and logs, serverless deployment, and plugin ecosystem. Use when the developer asks to "just do it", "set this up", "run a command", mentions "CLI", "command line", or "terminal", or when an AI agent can execute a task directly instead of writing application code.
Expert knowledge for Azure Virtual Desktop development, including troubleshooting, best practices, decision-making, architecture and design patterns, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use when managing AVD host pools, FSLogix profiles, autoscale, MSIX App Attach, Teams/OneDrive optimization, or other Azure Virtual Desktop development tasks. Not for Azure Virtual Machines (use azure-virtual-machines), Azure Dev Box (use azure-dev-box), Azure Lab Services (use azure-lab-services), or Azure VMware Solution (use azure-vmware-solution).
Builds AI agents on Cloudflare using the Agents SDK with state management, real-time WebSockets, scheduled tasks, tool integration, and chat capabilities. Generates production-ready agent code deployed to Workers. Use when: user wants to "build an agent", "AI agent", "chat agent", "stateful agent", mentions "Agents SDK", needs "real-time AI", "WebSocket AI", or asks about agent "state management", "scheduled tasks", or "tool calling". Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Comprehensive guide for managing Cloudflare DNS with Azure integration. Use when configuring Cloudflare as authoritative DNS provider for Azure-hosted applications, managing DNS records via API, setting up API tokens, configuring proxy settings, troubleshooting DNS issues, implementing DNS security best practices, or integrating External-DNS with Cloudflare for Kubernetes workloads.
Configure Airflow to run language SDK tasks (Java, Go, and future native SDKs): register a coordinator, map a queue to it, ensure the runtime/artifact is available on workers, and tune coordinator options. Use when the user wants Airflow to route a queue to a native-language coordinator; asks about `[sdk]` `coordinators`/`queue_to_coordinator` settings, `AIRFLOW__SDK__COORDINATORS`, `jars_root`, `executables_root` or other coordinator `kwargs`, `task_startup_timeout`; or asks why native tasks aren't being picked up. Covers the shared routing mechanism and per-coordinator options (e.g. JavaCoordinator, ExecutableCoordinator).
Use for ALL Zeabur environment variable operations — create, list, update, delete, or troubleshoot. Use when user says "set env var", "add variable", "create variable", "update variable", "delete variable", "change env var", or "why is my variable empty". Also use when variables are empty or SERVICE_NOT_FOUND errors.
Expert knowledge for Azure Container Storage development, including troubleshooting, decision-making, limits and quotas, security, and configuration. Use when configuring Elastic SAN-backed pools, CMK encryption, LRS/ZRS redundancy, volume resizing, or Prometheus/Grafana monitoring, and for other Azure Container Storage development tasks. Not for Azure Blob Storage (use azure-blob-storage), Azure Files (use azure-files), Azure Elastic SAN (use azure-elastic-san), or Azure NetApp Files (use azure-netapp-files).
Expert knowledge for Azure Network Watcher development, including troubleshooting, decision-making, limits and quotas, security, configuration, integrations, and coding patterns. Use when configuring VNet/NSG flow logs, Traffic Analytics, packet capture, Connection Monitor migration, or VPN monitoring, and for other Azure Network Watcher development tasks. Not for Azure Monitor (use azure-monitor), Azure Virtual Network (use azure-virtual-network), Azure Networking (use azure-networking), or Azure Firewall (use azure-firewall).
Expert knowledge for Azure Synapse Analytics development, including troubleshooting, best practices, decision-making, architecture and design patterns, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use for Synapse SQL pools, Spark pools, Delta Lake, Synapse Link (Cosmos/SQL), ELT via PolyBase, and other Azure Synapse Analytics development tasks. Not for Azure Data Factory (use azure-data-factory), Azure Data Explorer (use azure-data-explorer), Azure Databricks (use azure-databricks), or Azure Stream Analytics (use azure-stream-analytics).
Deploy NewAPI LLM Gateway on Huawei Cloud via Terraform. Use when deploying a unified LLM API gateway for multi-model management, load balancing, and key rotation. Trigger: deploy NewAPI, NewAPI gateway, LLM gateway, 部署NewAPI, NewAPI网关, LLM网关
Huawei Cloud SWR (Software Repository for Container) image automation and operations skill using hcloud CLI. Use when the user wants to: (1) configure cross-region image sync (auto or manual), (2) manage SWR triggers for auto-deploy to CCE/CCI, (3) query available sync target regions, (4) check sync job status, or (5) create/update/delete trigger configurations. Trigger: user mentions “SWR automation”, “SWR 自动化”, “镜像同步”, “SWR sync”, “跨区域同步”, “cross-region sync”, “触发器”, “SWR trigger”, “自动部署”, “auto deploy”, “镜像复制”, “image replication”, or “SWR 触发器”
Huawei Cloud SWR (Software Repository for Container) image lifecycle management skill using hcloud CLI. Use when the user wants to: (1) manage SWR namespaces (organizations) — create/query/delete, (2) manage image repositories — create/query/update/delete, (3) manage image tags/versions — query/create/delete, (4) obtain docker login credentials for SWR, or (5) check SWR quotas and usage limits. Trigger: user mentions “SWR image management”, “SWR 镜像管理”, “container image”, “镜像仓库”, “SWR 组织”, “SWR namespace”, “镜像版本”, “docker login”, “SWR 配额”, “SWR tag”, “容器镜像”, “镜像生命周期”, “SWR repository”, “SWR 登录”, or “SWR quota”
Expert knowledge for Azure Arc development, including troubleshooting, best practices, decision-making, architecture and design patterns, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use when working with Arc-enabled Kubernetes, Arc SQL MI, resource bridge, Arc Agentic Retrieval, Edge Volumes, or other Azure Arc development tasks. Not for Azure Kubernetes Service (AKS) (use azure-kubernetes-service), Azure Virtual Machines (use azure-virtual-machines), Azure Stack Edge (use azure-stack-edge), or Azure Local (use azure-local).
Expert knowledge for SQL Server on Azure Virtual Machines development, including troubleshooting, best practices, decision-making, architecture and design patterns, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use when planning SQL VM vs Managed Instance, Always On/FCI HADR, Azure storage and backup, Key Vault/MI authentication, KQL telemetry, or other SQL Server on Azure Virtual Machines development tasks. Not for Azure SQL Database (use azure-sql-database), Azure SQL Managed Instance (use azure-sql-managed-instance), Azure Virtual Machines (use azure-virtual-machines), or SAP HANA on Azure Large Instances (use azure-sap).
Expert knowledge for Azure Web Application Firewall development, including best practices, decision-making, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use when configuring Front Door/App Gateway WAF rules, rate limits, bot challenges, Sentinel logging, IaC deployments, or other Azure Web Application Firewall development tasks. Not for Azure Application Gateway (use azure-application-gateway), Azure Front Door (use azure-front-door), Azure Firewall (use azure-firewall), or Azure DDoS Protection (use azure-ddos-protection).
Builds, packs, and deploys compiled Airflow Go SDK bundles so the ExecutableCoordinator can run them. Use when the user wants to compile a Go task bundle, asks about `go build`, `go tool airflow-go-pack`, the AFBNDL01 self-contained executable bundle, packing or inspecting a bundle, placing it under `executables_root`, cross-compiling a bundle for workers, `go-sdk` module versioning/tags/pseudo-versions, or getting the bundle onto an Airflow worker (Docker, Kubernetes, or Astro). For the task code see authoring-go-sdk-tasks; for the shared coordinator settings see configuring-airflow-language-sdks.
Huawei Cloud SWR (Software Repository for Container) image governance skill using hcloud CLI. Use when the user wants to: (1) manage SWR namespace permissions—grant/query/modify/revoke; (2) manage repository permissions—grant/query/modify/revoke; (3) manage image retention rules—create/list/update/delete; (4) manage shared download domains—create/list/update/delete; (5) manage image sharing—list shared repos/query feature gates; (6) check SWR agency status and create agency delegation; (7) list repo accessories and references. Trigger: user mentions “SWR image governance,” “SWR 镜像治理,” “SWR 权限管理,” “SWR retention,” “SWR 保留策略,” “SWR 共享域名,” “SWR 共享镜像,” “SWR 委托,” “SWR agency,” “namespace permissions,” “repository permissions,” “镜像权限,” “保留规则,” “共享下载,” or “镜像分享.”
Expert-level AI system design, MLOps, architecture patterns, and AI infrastructure. Use when the user mentions AI architecture, MLOps, system design, AI infrastructure, or scalability, or when the task involves AI System Architecture, MLOps Infrastructure, Scalability Patterns, or Architecture Design.
Expert knowledge for Azure Automation development, including troubleshooting, best practices, decision-making, limits and quotas, security, configuration, integrations and coding patterns, and deployment. Use when building runbooks, DSC configs, Hybrid Runbook Workers, managed identities, or Automation deployments, and for other Azure Automation-related development tasks. Not for Azure Functions (use azure-functions), Azure Logic Apps (use azure-logic-apps), Azure DevOps (use azure-devops), or Azure DevTest Labs (use azure-devtest-labs).
Expert knowledge for Azure NAT Gateway development, including troubleshooting, best practices, decision-making, architecture and design patterns, limits and quotas, security, configuration, and deployment. Use for managing NAT Gateway V2, flow logs, SNAT ports, outbound IPs, Azure Firewall egress patterns, and other Azure NAT Gateway development tasks. Not for Azure Virtual Network (use azure-virtual-network), Azure Virtual Network Manager (use azure-virtual-network-manager), Azure Load Balancer (use azure-load-balancer), or Azure Virtual WAN (use azure-virtual-wan).
Expert knowledge for Azure Reliability development, including best practices, decision-making, architecture and design patterns, and limits and quotas. Use for choosing regions/AZs, geo-pairs, multiregion designs, Azure Storage Discovery, Queue Storage, Web PubSub, and other Azure Reliability development tasks. Not for Azure Resiliency (use azure-resiliency), Azure Monitor (use azure-monitor), Azure Service Health (use azure-service-health), or Azure Sre Agent (use azure-sre-agent).
Systematic CI/CD failure diagnosis using hypothesis-first investigation, local reproduction, and environment delta analysis. Use when a CI pipeline, GitHub Actions workflow, or build job fails; when tests pass locally but fail in CI; when diagnosing flaky tests, timeouts, or red pipelines; or when the user says "CI is failing", "the build is broken", or "works on my machine"
Speeds up CI and the merge path: finds where changes wait between push and deploy, then fixes the critical path, check placement, merge queue or post-merge checks with auto-revert, flaky tests, and deploy rate. Use when "CI is slow", "speed up CI", "do we need a merge queue", "main keeps going red", "flaky tests block merges", agents open PRs faster than they merge, or building a self-healing merge loop.
Use when building, modifying, deploying, or debugging Keboola Apps (Streamlit or Python/JS). Covers the full lifecycle — choosing app type, the Python/JS prod-app-and-drafts model (never create a second app), configuring keboola-config/, storage access (RO workspace, RW Query Service, input mapping), authentication, DuckDB caching for performance, default Keboola styling, dashboard patterns, optional Kai chat integration, and the three client paths (MCP-only, Claude Code with filesystem, kbagent CLI).
Deploys a built Internet Computer project to a cloud engine (OpenCloud): link the console identity with `icp identity link web` (defaults to https://opencloud.org; a delegation handoff covers sandboxes), run `icp deploy` on the engine's subnet, tag canisters with `__META_*` for a named console app, bake version metadata (service:git:sha) into the wasm, and get the proxy an app needs for Bitcoin/Ethereum signing, VetKeys or exchange rates: deployed by the engine owner in the console and paid from the engine's balance, or self-deployed (`icp new --subfolder proxy`). Use when shipping to a cloud engine; on mention of OpenCloud, an engine subnet id, or linking the icp CLI; when sign-in never completes from a sandbox; when naming, versioning or giving an icon to a console app; when a proxy must be deployed or funded, or which balance to top up (engine, proxy; failing proxied calls: cloud-engine-canisters). Do NOT use for a mainnet deploy with no engine (icp-cli) or canister logic (cloud-engine-canisters).
Scaffolds and adapts Node.js apps for GoDaddy Node.js Hosting (PaaS): package.json start/build scripts, PORT binding, single-app upload, and framework recipes. Use when building a new app, adapting an existing app, fixing deploy or start failures, or preparing AI tool exports (Replit, Lovable, Bolt, Cursor) for Node.js Hosting.
Expert-level toolkit for modular Godot 4.7+ CLI automation and headless build orchestration. Use when you need to: (1) Build complex scene trees or UI layouts programmatically, (2) Automate expert 3D asset pipelines (glTF -> Collision), (3) Optimize procedural geometry headlessly (CSG -> Static Mesh), or (4) Engineer production-grade CI/CD pipelines. Set GODOT_PATH env var for custom engine location. Keywords: Godot CLI, headless, CI, export, builder, 4.7.
Build and deploy a Next.js, Bigfish (@alipay/bigfish), or Vite project to the Morphe service (https://morphe.zenmux.app), targeting a linux-x64-gnu runtime. Use when the user asks to deploy, ship, publish, or release a Next.js, Bigfish, or Vite app to Morphe, run "morphe deploy", or otherwise push a build to the Morphe / zenmux platform. Handles login, framework detection, Next.js standalone validation / config fixing, Bigfish static-server wrapping, Vite SPA static wrapping or custom-server (server.ts/js) esbuild bundling, building, zipping, OSS upload, CRC64 checksum, .morphe.json management, and the deploy API call.
Sizes a Qdrant deployment before it is provisioned. Use when someone asks 'how much RAM do I need', 'how many nodes', 'how big should my cluster be', 'sizing', 'capacity planning', 'will N vectors fit', 'what instance type should I pick', or gives a vector count and dimensions and asks what to provision. Also use when an existing estimate needs checking before hardware or a cluster tier is bought
Deploy a working Intel® SceneScape installation from scratch (outside the repo). Gathers user-provided streams, camera IDs, scene name, and mapping choice, then runs bootstrap through tracking verification via scripts/deploy_scenescape.sh. Also handles re-running or resuming a single phase of an existing deployment on request (e.g. "recalibrate", "redo scene reconstruction", "resume bootstrap only") via the orchestrator's --phase flag.
Use when modifying service config without full redeploy. Use when updating env vars and restarting single service. Use when user says "change env var", "update config", "fix variable without redeploying", "upgrade service version", "update image tag", or "change service tag".
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.