Observability Triage
every-app/open-seo
Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically.
Debug deployed Cloudflare Workers using the cfobservability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction.
Install Debug Cloudflare Workers Observability
$ npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Consensys/c0 debug-cloudflare-workers-observability --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debug-cloudflare-workers-observability .claude/skills/debug-cloudflare-workers-observability && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debug-cloudflare-workers-observability" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/debug-cloudflare-workers-observability into .claude/skills/debug-cloudflare-workers-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-cloudflare-workers-observability", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Consensys/c0/tree/master/.agents/skills/debug-cloudflare-workers-observabilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Consensys/c0 debug-cloudflare-workers-observability --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/debug-cloudflare-workers-observability .agents/skills/debug-cloudflare-workers-observability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debug-cloudflare-workers-observability" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/debug-cloudflare-workers-observability into .agents/skills/debug-cloudflare-workers-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-cloudflare-workers-observability", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Consensys/c0 debug-cloudflare-workers-observability --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/debug-cloudflare-workers-observability .cursor/skills/debug-cloudflare-workers-observability && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debug-cloudflare-workers-observability" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/debug-cloudflare-workers-observability into .cursor/skills/debug-cloudflare-workers-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-cloudflare-workers-observability", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Consensys/c0.git --path .agents/skills/debug-cloudflare-workers-observability--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Consensys/c0 debug-cloudflare-workers-observability --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/debug-cloudflare-workers-observability .gemini/skills/debug-cloudflare-workers-observability && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debug-cloudflare-workers-observability" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/debug-cloudflare-workers-observability into .gemini/skills/debug-cloudflare-workers-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-cloudflare-workers-observability", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Consensys/c0 debug-cloudflare-workers-observabilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/debug-cloudflare-workers-observability .github/skills/debug-cloudflare-workers-observability && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debug-cloudflare-workers-observability" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/debug-cloudflare-workers-observability into .github/skills/debug-cloudflare-workers-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-cloudflare-workers-observability", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Consensys/c0 debug-cloudflare-workers-observability --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Consensys/c0.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/debug-cloudflare-workers-observability .opencode/skills/debug-cloudflare-workers-observability && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debug-cloudflare-workers-observability" agent skill from https://github.com/Consensys/c0/tree/master/.agents/skills/debug-cloudflare-workers-observability into .opencode/skills/debug-cloudflare-workers-observability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-cloudflare-workers-observability", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debug-cloudflare-workers-observability- GitHub stars
- 105
- Token cost
- ~1.2k tokens
- SKILL.md length
- 560 words
- Files
- 6 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- LGPL-3.0
At a glance
Debug deployed Cloudflare Workers using the cfobservability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction.
- Works in 7 steps: Bound the incident: stage, Worker script… → Read the repo surface that defines the… → Query deployed observability before… → …
- Preview/prod runtime incidents involving missing
- SKILL.md covers Core Loop, cf_observability First Pass, Wrangler And State and Domain Sections, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Debug Cloudflare Workers Observability is an agent skill from Consensys/c0. Debug deployed Cloudflare Workers using the cfobservability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction. Use for preview/prod runtime incidents involving missing or incomplete logs/traces, webhook delivery, Worker request routing, Workflow runs/events/artifacts, Slack app integrations, Slack API errors such as invalidarguments, duplicate responses, or cases where the user asks to use Cloudflare Worker Observability or cfobservability to debug c0 behavior.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `references/cf-observability.md` and `references/slack-integration.md`).
It sits in DevOps & Cloud, covering Observability and Webhooks. It works with Cloudflare Workers, Slack and Model Context Protocol. The repository describes itself as: c0 is an open-source AI platform built for organizational work, tools, and context. A single deployment to Cloudflare to get started. The licence is LGPL-3.0.
When your agent uses it
- Preview/prod runtime incidents involving missing
- Incomplete logs/traces
- Webhook delivery
- Worker request routing
Example prompts
- “/debug-cloudflare-workers-observability”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Bound the incident: stage, Worker script name, user-facing URL/path, approximate UTC window, IDs already known, and what safe live action…
- Read the repo surface that defines the runtime: Worker name, route, bindings, D1/R2 names, feature flags, and existing observability…
- Query deployed observability before guessing from code. Use the cf_observability MCP when available; otherwise pivot to Wrangler, D1/R2…
- Cross-check durable state. Logs often prove ingress and routing; D1/R2 usually prove workflow/run/session/artifact state.
- Reproduce with the smallest safe action only after the path and target environment are clear.
- Patch the owning boundary. Prefer structured Effect logs/spans/request observers already used by the repo. Do not add noisy catch-all logs…
- Validate locally, deploy only when allowed, then close the loop with a new deployed query and durable-state readback.
What it can do on your machine
Read from SKILL.md and the folder at commit e7a1810. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debug Cloudflare Workers Observability loads about 1.2k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 560 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:43
source config/.env
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Consensys/c0 at commit e7a1810, republished under its LGPL-3.0 licence (© Consensys). 560 words, ~1,245 tokens.
Download SKILL.mdSave it as
.claude/skills/debug-cloudflare-workers-observability/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- debug-cloudflare-workers-observability
- description
- Debug deployed Cloudflare Workers using the cf_observability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction. Use for preview/prod runtime incidents involving missing or incomplete logs/traces, webhook delivery, Worker request routing, Workflow runs/events/artifacts, Slack app integrations, Slack API errors such as invalid_arguments, duplicate responses, or cases where the user asks to use Cloudflare Worker Observability or cf_observability to debug c0 behavior.
Debug Cloudflare Workers Observability
Use this as an evidence-first debugging loop for deployed Workers. Start broad enough to prove the request reached the Worker, then narrow through structured logs, durable state, and the owning code boundary.
Core Loop
- Bound the incident: stage, Worker script name, user-facing URL/path, approximate UTC window, IDs already known, and what safe live action is allowed.
- Read the repo surface that defines the runtime: Worker name, route, bindings, D1/R2 names, feature flags, and existing observability helpers.
- Query deployed observability before guessing from code. Use the
cf_observabilityMCP when available; otherwise pivot to Wrangler, D1/R2, app UI, and local reproduction. - Cross-check durable state. Logs often prove ingress and routing; D1/R2 usually prove workflow/run/session/artifact state.
- Reproduce with the smallest safe action only after the path and target environment are clear.
- Patch the owning boundary. Prefer structured Effect logs/spans/request observers already used by the repo. Do not add noisy catch-all logs or log raw payloads/secrets.
- Validate locally, deploy only when allowed, then close the loop with a new deployed query and durable-state readback.
cf_observability First Pass
Use tool_search to expose cf_observability if its tools are not already loaded.
Start with observability_keys scoped to the Worker and an absolute ISO timeframe. Avoid relative windows unless you have verified the MCP accepts that exact format.
Common useful fields:
$metadata.service: Worker script name, such asc0-api-pre.$workers.event.request.path: request path for ingress routing.$metadata.requestId: Cloudflare request correlation within one invocation.$metadata.traceIdandannotations.trace.id: useful when populated, but do not assume they are searchable.message: structured log text and embedded JSON.annotations.*: app-specific metadata from Effect logs/spans.
Load references/cf-observability.md for query JSON, known failure modes, and examples.
Wrangler And State
Before any remote Wrangler work, verify auth without printing secrets:
set -a
source config/.env
set +a
nub exec wrangler whoamiFor c0, derive resource names from infra code instead of guessing. In the current pattern, pre resources include c0-db-pre and c0-workflow-artifacts-pre.
Use D1 for durable truth about runs, registrations, sessions, and configuration. Use R2 for workflow artifacts and generated code. Avoid destructive commands unless the user explicitly approved them.
Load references/wrangler-d1-r2.md for command shapes.
Show full SKILL.md (213 more words)Show less
Domain Sections
Workflows
Use this section when debugging c0 Workflow triggers, workflow overview rows, run failures, node outputs, generated workflow artifacts, or mismatches between the UI and runtime behavior.
Primary evidence order:
- Observability ingress/routing logs.
workflows,workflow_runs, andworkflow_run_eventsD1 rows.- Workflow manifest/code artifacts in R2.
- Compiled workflow and node implementation code.
Load references/workflows.md for D1 queries, artifact inspection, safe manifest version updates, and how to reason about workflow error logging.
Slack Integration
Use this section when debugging Slack webhook delivery, app mentions, keyword triggers, slash commands, Slack API errors, duplicate Slack replies, or Slack app setup.
Primary evidence order:
- Query Worker logs for
/workflows/slack-apps/ingress. - Confirm channel hydration, registration listing/filtering, matched trigger nodes, and run count.
- Use D1 run events to decide whether Slack posted once or the workflow/model produced duplicated text.
- Use browser/Slack only in an explicitly authorized channel, and only after backend targeting is clear.
Load references/slack-integration.md for Slack-specific log names, safe test flow, and invalid_arguments debugging notes.
Reporting
Report the investigation as evidence, not vibes:
- What reached the Worker and how you know.
- Which query or command proved each hop.
- Which query failed or produced incomplete evidence.
- What durable state said.
- The exact owning boundary patched.
- Validation, deploy, and post-deploy readback.
© Consensys, LGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in .agents/skills/debug-cloudflare-workers-observability of Consensys/c0.
- SKILL.md
- agents/openai.yaml
- references/cf-observability.md
- references/slack-integration.md
- references/workflows.md
- references/wrangler-d1-r2.md
Open the folder on GitHubat commit e7a1810
Compare with similar skills
Debug Cloudflare Workers Observability next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debug Cloudflare Workers Observability this skillConsensys/c0 | 105 | — | ~1.2k | Automated safety check: Notes | LGPL-3.0 | |
| Observability Triageevery-app/open-seo | 23k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template | 786 | — | ~5.9k | Automated safety check: Notes | MIT | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 412 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Agentmeasureroy-tong/AgentMeasure | 218 | — | ~753 | Automated safety check: Pass | MIT | |
| Logging Observabilitygetsentry/toolkit | 917 | — | ~2.6k | Automated safety check: Pass | Custom licence |
Similar skills
Prepare Cloudflare Production Deployment
LubomirGeorgiev/cloudflare-workers-nextjs-saas-template
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.
UModel Root Cause Analysis
alibaba/UnifiedModel
Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.
Agentmeasure
roy-tong/AgentMeasure
Check whether agent telemetry preserves measurement semantics.
- Official
Logging Observability
getsentry/toolkit
Review code for correct logging and error handling patterns.
AWS Cost Operations
zxkane/aws-skills
AWS cost optimization, monitoring, and operational excellence expert.
More from Consensys/c0
All 11 skills in this repoDeslop Typescript
Consensys/c0
Run a final de-slopping pass on nearly finished JavaScript or TypeScript work before commit or PR.
Implement Workflow Node
Consensys/c0
A skill your agent uses when adding, changing, or reviewing Workflow Nodes in the c0 agent repo, including shared node catalog metadata, Workflow Node options and ports, runtime node Adapters…
Workflow Runtime Abi
Consensys/c0
Guidance for safely changing the c0 Workflow runtime ABI, manifest ABI, runtime kernels, manifest migrations, workflow artifact compatibility, and audit/backfill tooling.
Agent Eval Loop
Consensys/c0
Run and improve the c0 agent evaluation loop using the local and remote Cloudflare MCP harness, versioned history notes, and current Cloudflare product updates.
Alchemy Env Types
Consensys/c0
Derive Cloudflare worker env types from Alchemy resource Env types instead of hand-writing env shapes.
C0 Config
Consensys/c0
A skill your agent uses when changing c0 deployment configuration, runtime-editable global settings, auth providers, AI providers, MCP Context Forge, discovered registries, secret references, or…
Related
Categories
Questions about Debug Cloudflare Workers Observability
What does Debug Cloudflare Workers Observability do?
Debug deployed Cloudflare Workers using the cfobservability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction. Debug Cloudflare Workers Observability is an agent skill from Consensys/c0. Debug deployed Cloudflare Workers using the cfobservability MCP, Wrangler, D1/R2 state, repo evidence, and safe live reproduction.
When should I use Debug Cloudflare Workers Observability?
Debug Cloudflare Workers Observability fits situations like: preview/prod runtime incidents involving missing; incomplete logs/traces; webhook delivery; worker request routing.
How do I install Debug Cloudflare Workers Observability in Claude Code?
Run `npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a claude-code`. Or copy the skill folder (.agents/skills/debug-cloudflare-workers-observability in Consensys/c0) into .claude/skills/debug-cloudflare-workers-observability in your project. Claude Code loads it when a task matches its description.
How do I install Debug Cloudflare Workers Observability in Codex?
Run `npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a codex`. Or copy the skill folder (.agents/skills/debug-cloudflare-workers-observability in Consensys/c0) into .agents/skills/debug-cloudflare-workers-observability in your project. Codex loads it when a task matches its description.
Can I use Debug Cloudflare Workers Observability in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Consensys/c0 --skill debug-cloudflare-workers-observability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-cloudflare-workers-observability, .gemini/skills/debug-cloudflare-workers-observability, .github/skills/debug-cloudflare-workers-observability and .opencode/skills/debug-cloudflare-workers-observability in your project.
What does Debug Cloudflare Workers Observability need to run?
SKILL.md names no scripts, command-line tools or credentials: Debug Cloudflare Workers Observability is instructions for the agent only.
Does Debug Cloudflare Workers Observability access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debug Cloudflare Workers Observability safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Debug Cloudflare Workers Observability use?
Debug Cloudflare Workers Observability is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debug Cloudflare Workers Observability use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.6k tokens, read only when the agent opens those files.
What are the alternatives to Debug Cloudflare Workers Observability?
Skills that share tags, products or a category with Debug Cloudflare Workers Observability: Observability Triage (every-app/open-seo, 23k stars), Prepare Cloudflare Production Deployment (LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, 786 stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 412 stars) and Agentmeasure (roy-tong/AgentMeasure, 218 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debug Cloudflare Workers Observability?
Consensys (a GitHub organization) maintains it in Consensys/c0, which has 105 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 18, 2026.
Source: Consensys/c0 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.