Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Cloud & DevOps
Bumps Konflux Tekton task bundle digests in `.tekton` and `.tekton-templates`, applies each task's MIGRATION.md, regenerates PipelineRuns, and checks pins against data-acceptable-bundles so ECP does not reject expired or untrusted tag@sha256 refs (tasks.unsupported, required_untrusted_task_found). Then invokes /rhdh-base-images for the matching GitHub main or release-* branch so FROM tags, rpms.lock.yaml, and Node headers stay current. Use for "bump konflux task digests", "apply the tekton migration", "ECP violation", "expired task", "trusted task", "missing node headers", node-v*-headers.tar.gz, .nvm/releases, catalog builder.Containerfile, UBI nodejs, quay.io/konflux-ci/tekton-catalog/task-* upgrades such as buildah-oci-ta or prefetch-dependencies-oci-ta, and build-definitions MIGRATION.md URLs that 404. Runs on rhdh-plugin-catalog and RHDH midstream (updateDigests.sh, generatePipelineRuns.sh, updatePLRs.sh; generatePipelineRunsForPlugins.sh is the deprecated 1.9/1.10 name).
Create or load an operational runbook for a given topic. Searches `runbooks/` for an existing match; if none, scaffolds a new one from the standard template (Purpose / Prerequisites / Steps / Verification / Troubleshooting / Last Tested). Use when asked to "create a runbook", "load runbook for X", document a procedure, or look up an SOP.
Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Build or update a GitHub Pages documentation site with the same design as fandhe-frontend. Covers Rust SSG, Markdown management, automated deployment with Actions, and branding configuration (the site table in nav.toml). Use for requests such as “I want to publish on GitHub Pages,” “create a docs site,” “use the same design as fandhe-frontend,” “update the Pages site,” or “bring the design up to date.” For publishing with Firebase, use setup-firebase-hosting; for a standalone HTML page, use create-html-report.
Signals scout for PostHog distributed tracing (APM / OpenTelemetry spans). Watches per-service RED metrics for error-rate and latency regressions, new error signatures, and traffic cliffs, and audits for standing performance issues: N+1 calls, expensive query shapes, and caching candidates
Sinch Functions, the beta serverless platform for voice, SMS and conversation apps. Use for platform questions: what it is, how deployment works, choosing Node.js or C#, install and auth, FunctionContext, handlers, the Voice v2 call lifecycle and `call.*` events, voice services and `VOICE_SERVICE_ID`, and SVAML. Runtime code lives in sinch-functions-node and sinch-functions-dotnet.
Write C#/.NET Sinch Functions with the `Sinch.Functions.Runtime` NuGet package. Use when writing or editing a function controller: answering and controlling calls with Voice API v2, IVR menus, placing, bridging or transferring calls, realtime AI voice agents, SMS/WhatsApp/RCS webhooks, custom HTTP endpoints, dependency injection, cache/storage/database and authorization. Run and deploy with the sinch-cli skill.
Use this skill when the user asks to “analyze network traffic with Wireshark,” “capture packets for troubleshooting,” “filter PCAP files,” “follow TCP/UDP streams,” “detect network anomalies,” “investigate suspicious traffic,” or “perform protocol analysis.” It provides comprehensive techniques for network packet capture, filtering, and analysis using Wireshark.
Generate an interactive bash wizard that walks a person step by step through operations only a human can do. Use it to provision infrastructure, configure credentials or CI secrets, navigate unfamiliar third-party backends, or run a one-off migration/cutover. Don't use it for steps the agent can do itself.
Use when managing Alibaba Cloud Contact Center AI (ContactCenterAI) via OpenAPI/SDK, including the task involves Contact Center AI resource lifecycle operations, configuration changes, status queries, or troubleshooting failed ContactCenterAI API calls.
Use when managing Alibaba Cloud Cloud Call Center (CCC) via OpenAPI/SDK, including the user is working on CCC operations such as instance/resource management, configuration updates, status checks, and troubleshooting call-center API workflows.
Sets up GitHub Actions CI/CD workflows for Astro sites — `astro check` (TypeScript + content schema), ESLint, Prettier, build verification, Vitest testing, Lighthouse CI, link checking, npm audit, and automated deployment to GitHub Pages, Cloudflare Pages, Netlify, or Vercel. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an Astro site — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated type-checking or linting to an Astro repo; set up `astro check` in CI; add Lighthouse or accessibility checks to PRs; configure Vitest in CI for an Astro project; auto-deploy an Astro site to GitHub Pages, Cloudflare Pages, Netlify, or Vercel from GitHub; add link checking or broken-link detection; add security scanning to an Astro pipeline; or generally "add CI", "add automated checks", "set up workflows", or "automate" anything related to an Astro site's GitHub repository. Also trigger when someone wants quality gates on PRs, wants to verify the build still passes, or is setting up a new Astro repo and wants best practices for automation. If the user is inside an Astro project repository and mentions anything about automated testing, code quality, deployment, or GitHub workflows, use this skill.
Use when the user asks about chaos engineering, fault injection, resilience testing, or HA verification for a SPECIFIC AWS service (e.g., RDS, EKS, MSK, ElastiCache, DynamoDB, S3, Lambda, OpenSearch, etc.). Triggers on "chaos testing on [service]", "fault injection for [service]", "how to test HA of [service]", "FIS scenarios/actions for [service]", "[service] failover testing", "[service] resilience testing", "[service] 混沌测试", "[service] 故障注入", "[service] 高可用验证", "对 [service] 做混沌实验", "test my [service]", "verify my [service] is resilient". Use this skill even when the user phrases it casually like "test my RDS" or "how resilient is my MSK cluster".
Use when exporting existing Azure resources to Terraform using aztfexport. Triggers on aztfexport, Azure import to Terraform, export Azure resource, bring Azure under Terraform management, reverse-engineer Azure infrastructure, bootstrap IaC from live Azure resources. Covers resource, resource-group, and query modes.
Connects an app to the Azure SQL Database container securely, with a least-privilege database user instead of the sa login, the right auth method per environment, and safe handling of the connection secret. Use when a user asks "don't use sa in my app", "create a least-privilege database user", "app login for SQL", "which authentication should my app use", "secure the connection string", "Encrypt / TrustServerCertificate", "store the connection string in Key Vault", "dotnet user-secrets", "managed identity for Azure SQL", or "grant only the roles my app needs". SQL auth locally, Microsoft Entra or managed identity in the cloud, changing only the connection string. Reach for this before wiring an app to connect as sa, or before committing a connection string to source.
Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask "when was X deployed", "is my change live in the US/EU yet", "has my PR shipped", "did the fix roll out to prod-us", or otherwise want to know whether/when a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event/data volume alone — that only shows when data changed, not when code shipped.
Use when an agent needs to operate HeadlessX through the published `headlessx` CLI instead of calling files or APIs directly. Covers installing the CLI package, bootstrapping local HeadlessX with `headlessx init`, updating an existing workspace with `headlessx init update`, using the guided modern setup/login prompts, logging in with API URL and API key, reading runtime logs with `headlessx logs`, using markdown-first terminal output, and running commands for website scraping, map, crawl, Google AI Search, Tavily, Exa, YouTube, jobs, and operators. Trigger for requests like "use the CLI", "test the CLI", "show the command", "log in with the CLI", "run HeadlessX from terminal", "bootstrap HeadlessX", "update HeadlessX", "show logs", or "smoke test the CLI".
Guide to Cloudflare Email Routing, covering both Email Workers for receiving mail and the send_email binding for sending mail from Workers. Covers dashboard setup with MX, SPF and DKIM records, the email() handler and ForwardableEmailMessage, parsing with postal-mime, composing with mimetext and cloudflare:email EmailMessage, allowlists and blocklists, conditional forwarding, and automatic replies. Documents 8 known issues including Email Trigger not available, unverified destination addresses, Gmail rate limiting, SPF permerror, failed to call worker, and limited free-plan debugging. Use when enabling email routing, writing or configuring an Email Worker, sending notifications or alerts from a Worker, parsing incoming email, configuring MX records, or troubleshooting mail that is not forwarding or delivering.
Cloudflare Zero Trust Access authentication for Cloudflare Workers applications. Covers hono-cloudflare-access middleware setup, manual Access JWT validation with public key caching, service tokens for machine-to-machine auth, CORS handling in front of Access, identity providers (Azure AD, Google Workspace, Okta, GitHub), role-based access control, geographic restrictions, multi-tenant configurations, and Access policy setup. Prevents eight common errors including blocked CORS preflight requests, key cache race conditions, missing JWT headers, and dev/prod team mismatches. Use when protecting Worker routes or admin dashboards with Access, validating Access JWT claims, authenticating backend services or CI/CD jobs to a Worker API, or debugging blocked preflight requests, a missing Access JWT header, or team mismatch errors.
Check and configure cache-busting strategies for Next.js and Vite projects. Use when configuring content hashing for Next.js or Vite builds, setting up CDN cache headers for Vercel or Cloudflare, adding build verification scripts for hashed assets, or auditing static asset caching strategy. Natural triggers: "configure cache busting", "set up CDN cache headers", "add content hashing".
Metadata management, data analysis, development changes, operations diagnostics, and inspections for Volcengine databases (MySQL, veDB-MySQL, PostgreSQL, SQL Server, MongoDB, Redis) and self-managed public-network databases (MySQL and PostgreSQL families). Covers instance lists, databases within instances, table lists and schemas, data queries, data analysis and visualization reports (including joint analysis across data sources/files), data governance (asset inventories/data profiling/data quality/sensitive data identification), slow query diagnostics, deadlock and lock-wait analysis, transaction and active session troubleshooting, error log queries, tablespace analysis, health inspections, monitoring metric queries, and change request applications. Does not support ByteCloud databases such as ByteRDS / ByteDoc / ByteRedis
Domain name multi-query tool — one-shot lookup of ICP filing (备案) and WHOIS registration info for any domain. Triggered whenever the user mentions "domain lookup", "ICP", "备案", "WHOIS", "registration info", "check this domain", "domain details", "域名查询", "查一下这个域名", or simply pastes a domain and asks "check it" or "查一下". Trigger even for one-line requests.
Guides zero trust implementation across AWS, Azure, and GCP per NIST SP 800-207 and BeyondCorp principles, covering identity-centric access, micro-segmentation, continuous verification, device trust assessment, and Identity-Aware Proxy deployment. Use when migrating from perimeter security to identity-centric access, removing VPN dependency, or designing micro-segmentation for multi-cloud workloads.
Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed. Use for "who broke master", "why did this test fail in CI", "is this failure my PR's fault or everyone's", "is this test flaky or actually broken", "when did this failure start". Works from the engineering_analytics warehouse views (engineering_analytics_ci_failures, engineering_analytics_ci_job_history) plus the CI failure logs. Not for aggregate CI health, cost, or merge bottlenecks (use diagnosing-ci-and-merge-bottlenecks) and not for building saved insights (use turning-engineering-analytics-into-insights).
Kaggle `kernel-metadata.json` setup and repair. PROACTIVELY activate for: (1) creating kernel-metadata.json, (2) fixing metadata validation errors, (3) setting `id`, `title`, `code_file`, language, or kernel type, (4) configuring private/public, internet, GPU, or accelerator behavior, (5) attaching dataset_sources, competition_sources, kernel_sources, or model_sources, (6) preparing metadata before `kaggle kernels push`, (7) converting script/notebook metadata. Provides: schema checklist, valid fields, source arrays, defaults, and push-readiness review.
Comprehensive logging and observability patterns for production systems including structured logging, distributed tracing, metrics collection, log aggregation, and alerting. Triggers for this skill - log, logging, logs, trace, tracing, traces, metrics, observability, OpenTelemetry, OTEL, Jaeger, Zipkin, structured logging, log level, debug, info, warn, error, fatal, correlation ID, span, spans, ELK, Elasticsearch, Loki, Datadog, Prometheus, Grafana, distributed tracing, log aggregation, alerting, monitoring, JSON logs, telemetry.
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.