shadow-observe
Skill1 starsChanged yesterdayMITView on GitHub
Production Observability & SRE. Use when defining SLIs/SLOs, error budget burn-rate alerts, OpenTelemetry distributed tracing, structured log correlation, or Prometheus/Loki/Grafana monitoring.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Cody-Sims/agent-skillstheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Cody-Sims/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Every production service must define explicit Service Level Indicators (SLIs) and Service Level Objectives (SLOs):
- Very specific: line 27
Never create an alert that has no clear mitigation step.
- Very specific: line 38
Ensure a single X-Request-Id / W3C traceparent flows unbroken across:
- Very specific: line 47
Cardinality Cost Guardrail: Never attach unbounded values (userId, requestId, email, raw URL path with UUIDs) as Prometheus metric labels — …
- Very specific: line 49
Diagnostic Handoff: When alerts or trace anomalies pinpoint a failing subsystem, hand off trace timeline + redacted logs to /shadow-debug …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shadow Observe (/shadow-observe) — SLI/SLO, Error Budgets, Tracing & Actionable Alerting
While /shadow-ops provisions the monitoring stack (Prometheus, Loki, Grafana), /shadow-observe governs what to measure, when to page a human, and how to turn telemetry into fast root-cause diagnosis.
1. Defining Measurable SLIs, SLOs & Error Budgets
Every production service must define explicit Service Level Indicators (SLIs) and Service Level Objectives (SLOs):
| SLI Category | Metric Formula | Standard SLO Target (28-Day Window) | Allowed Error Budget (28 Days) |
| Availability | $\frac{\text{Total Valid Requests} - \text{5xx Responses}}{\text{Total Valid Requests}}$ | 99.9% | 40.3 minutes downtime / 0.1% failed requests |
| Latency (Interactive API) | Proportion of requests with duration $\le 400\text{ms}$ (p95) and $\le 900\text{ms}$ (p99) | 95% < 400ms, 99% < 900ms | 5% slow requests |
| Async / Queue Freshness | Proportion of background jobs / ETL watermarks processed within < 5 minutes | 99.5% < 5m | 0.5% delayed jobs |
2. Actionable Alerting & Escalation Rules (Zero Alert Fatigue)
- Every Paging Alert Must Link to a Runbook Action:
- Never create an alert that has no clear mitigation step. Every alert annotation must include
runbook_urlor exact triage commands (docker compose logs,SELECT * FROM pg_stat_activity, rollback command).
- Never create an alert that has no clear mitigation step. Every alert annotation must include
- Multi-Window Burn Rate Alerting:
- Critical Page (P1 — Immediate Action): Fast burn where
> 2%of the 28-day error budget is consumed in1 hour(and still burning over the last5 minutes). - Warning Ticket (P2 — Next Business Hours): Slow burn where
> 5%of the error budget is consumed in6 hours.
- Critical Page (P1 — Immediate Action): Fast burn where
- Symptom-First, Cause-Second:
- Page on user-visible symptoms (5xx spike, latency breach, queue stall, disk
< 15%free, TLS cert expiring< 14 days), not noisy transient CPU spikes.
- Page on user-visible symptoms (5xx spike, latency breach, queue stall, disk
3. End-to-End Trace & Log Correlation (requestId / traceId)
Ensure a single X-Request-Id / W3C traceparent flows unbroken across:
- Frontend UI Error Boundary / Toast -> displays
Ref ID: req_01H...so a client reporting a bug on WhatsApp/Email gives the exact lookup key. - Nginx / Reverse Proxy Access Log -> logs
$http_x_request_id. - Backend Structured JSON Log -> every log line includes
"requestId": "req_01H...","userId","tenantId","route","durationMs". - Database / Queue Worker -> passes
requestId&traceparentacross async queue headers (shadow-concurrency) and SQL comments (/* req_id=req_01H... */) for slow-query tracing.
4. Cardinality Controls, Redaction & Debugging Handoff
- Cardinality Cost Guardrail: Never attach unbounded values (
userId,requestId,email, raw URL path with UUIDs) as Prometheus metric labels — put high-cardinality IDs in OpenTelemetry spans and structured logs only. - Telemetry Redaction: Strip
Authorization, cookies, NIK, and credentials before exporting spans or logs. - Diagnostic Handoff: When alerts or trace anomalies pinpoint a failing subsystem, hand off trace timeline + redacted logs to
/shadow-debugfor causal hypothesis falsification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

