Cloudflare DNS Analytics
This skill should be used when the user asks about "DNS performance", "zone settings", "DNS analytics", "domain configuration", "DNS report", "zone list", "DNS troubleshooting", "DNSSEC", "DNS latency", or needs to monitor and optimize Cloudflare DNS.
What this skill does
# Cloudflare DNS Analytics Monitor DNS performance and configuration using the DNS Analytics MCP server. ## Available Tools | Tool | Purpose | |------|---------| | `zones_list` | List all zones under the active account | | `dns_report` | Get DNS performance report for a zone over a time period | | `show_account_dns_settings` | View DNS settings at the account level | | `show_zone_dns_settings` | View DNS settings for a specific zone | ## Common Workflows ### DNS Health Check 1. Use `zones_list` to identify zones 2. Use `dns_report` for each zone to check performance 3. Review metrics for latency, query volume, errors ### Configuration Audit 1. Use `show_account_dns_settings` for account-level settings 2. Use `show_zone_dns_settings` for zone-specific settings 3. Compare settings across zones for consistency ### Performance Investigation 1. Identify the zone with `zones_list` 2. Pull `dns_report` for the relevant time frame 3. Analyze query patterns and response times ## DNS Report Metrics The DNS report typically includes: - Query volume over time - Response time distribution - Query types (A, AAAA, CNAME, etc.) - Response codes (NOERROR, NXDOMAIN, etc.) - Geographic distribution ## Integration with Workers For Workers using custom domains: 1. Verify zone configuration with `show_zone_dns_settings` 2. Check DNS report for the zone 3. Correlate with Workers observability data ## Troubleshooting | Issue | Investigation Steps | |-------|---------------------| | Slow DNS resolution | Check `dns_report` for latency metrics | | Missing records | Verify `show_zone_dns_settings` | | High error rates | Review response codes in `dns_report` | | Zone not found | List zones with `zones_list` | ## Tips - Zone IDs from `zones_list` are needed for other operations - DNS reports can span custom time ranges - Account settings may override zone settings - Use with observability tools for full-stack debugging
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.