Cloudflare Workers Observability
This skill should be used when the user asks about "worker logs", "debug worker", "worker errors", "request analytics", "worker metrics", "performance monitoring", "error rate", "invocation logs", "troubleshoot worker", "worker analytics", or needs to debug and monitor Cloudflare Workers.
What this skill does
# Cloudflare Workers Observability Debug and monitor Cloudflare Workers using logs and analytics from the Observability MCP server. ## Available Tools | Tool | Purpose | |------|---------| | `query_worker_observability` | Query logs and metrics from Workers | | `observability_keys` | Discover available data fields in logs | | `observability_values` | Find available values for specific fields | ## Query Workflow ### 1. Discover Available Fields Use `observability_keys` to find what data is available: - Metadata fields (timestamps, status codes) - Worker-specific fields (script name, route) - Custom logged fields from console.log ### 2. Explore Field Values Use `observability_values` to find valid values for filtering: - Status codes present in logs - Script names deployed - Custom field values ### 3. Query Logs and Metrics Use `query_worker_observability` to: - List recent events/invocations - Calculate metrics (error rates, latency) - Find specific invocations by criteria ## Common Queries | Goal | Approach | |------|----------| | Recent errors | Query for events with error status | | Latency analysis | Query for execution time metrics | | Traffic patterns | Query for invocation counts over time | | Specific request | Query by request ID or timestamp | | Script comparison | Query metrics grouped by script name | ## Debugging Workflow 1. **Identify the problem** - Query recent errors with `query_worker_observability` 2. **Find patterns** - Use `observability_keys` to discover relevant fields - Use `observability_values` to see error types 3. **Narrow down** - Add filters for specific routes, times, or status codes 4. **Analyze specific invocations** - Query for detailed logs of problematic requests ## Post-Deployment Monitoring After deploying, check for issues: 1. Query for errors in the last 5-10 minutes 2. Compare error rates before/after deployment 3. Check latency metrics for performance regression ## Tips - Start broad, then add filters to narrow results - Use `observability_keys` when unsure what fields exist - Custom console.log output appears in queryable fields - Combine with builds tools to correlate issues with deployments
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.