architect-monitoring

Detect OS and Cloudflare Worker health issues and map evidence to task actions.

198|19|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/iterate/iterate --skill architect-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-monitoring
Source: https://github.com/iterate/iterate/tree/main/.opencode/skills/architect-monitoring
Command: npx skills add https://github.com/iterate/iterate --skill architect-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you monitor the OS / Cloudflare Worker health signal, identify blocked or repeated incidents, and ensure the right evidence is attached for fast triage and escalation.

Core Features & Use Cases

  • Cloudflare Worker observability triage: Pulls events and traces to determine what changed, what broke, and whether the impact is clear.
  • Task-focused evidence updates: Records findings on the active task only when the situation is blocked, deferred, ambiguous, or repeated, keeping updates evidence-only.
  • Slack escalation with deep links: Posts to #error-pulse when impact is broad or unclear, including direct links to PostHog, Cloudflare logs queries, and the relevant GitHub code/work item.

Quick Start

Use the architect-monitoring workflow to check OS/Worker health signals for your current environment and record evidence on the active task, escalating to #error-pulse when impact is unclear or widespread.

Frequently Asked Questions about architect-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor Cloudflare Worker health and detect error regressions?

Monitor Cloudflare Worker health by collecting observability evidence from PostHog and Cloudflare logs, then mapping those signals to task-level actions to detect worker failures and error regressions during deploy or test workflows.

How does Slack escalation for incident response work with deep links?

Slack escalation works by posting to the #error-pulse channel when incident impact is broad or unclear, attaching deep links to PostHog, Cloudflare log queries, and GitHub permalinks to provide evidence-based triage context for fast resolution.

When do I need to update the active task with monitoring evidence?

Update the active task with monitoring evidence only when the incident situation is blocked, deferred, ambiguous, or repeated, ensuring that task records remain focused on evidence-only findings rather than routine status checks.

What is evidence-based triage for OS and worker health incidents?

Evidence-based triage for OS and worker health incidents is the process of collecting observability signals, determining what changed or broke, and attaching direct links to PostHog and Cloudflare logs to operationalize fast incident response.

How do I handle missing credentials when checking worker health signals?

Handle missing credentials by prioritizing environment variables first, and use the `doppler run` command to inject required secrets when credentials are missing during the worker health monitoring and triage workflow.

What's the best way to triage repeated or ambiguous incident signals across environments?

The best way to triage repeated or ambiguous incident signals across environments is to pull events and traces to determine what changed, record evidence-only updates on the active task, and escalate to Slack when impact remains unclear.