hypercare-anomaly-watcher
Skill1 starsChanged yesterdayMITView on GitHub
Watch production for the hypercare window after a release - Datadog metrics and Sentry issues, read-only, on a schedule (one tick per run) - and flag what changed against a statistical baseline (the same hour on the days before the release; robust z-scores for rates and latencies, Poisson tails for counts, a minimum change, persistence across ticks), correlate each anomaly with the release, and draft incidents for a named person to raise. Never pages, never creates incidents, monitors, issues or comments anywhere. Seasonal spikes in the baseline are normal; too little baseline is not_assessed, never normal; a quiet tick is never "all clear".
- Reads credentials
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- api-contract-testerSkill
- bug-reproducerSkill
- ci-failure-triagerSkill
- ci-suite-runnerSkill
- code-security-auditorSkill
- cross-browser-checkerSkill
- db-migration-reviewerSkill
- dead-test-finderSkill
- exploratory-charter-writerSkill
- flaky-test-hunterSkill
- i18n-checkerSkill
- journey-mapperSkill
- journey-to-testsSkill
- mobile-app-auditorSkill
- mutation-testerSkill
- performance-budget-auditorSkill
- post-deploy-validatorSkill
- privacy-flow-auditorSkill
- qa-orchestratorSkill
- release-readiness-gateSkill
- requirements-traceability-auditorSkill
- resilience-proberSkill
- risk-based-test-plannerSkill
- test-case-designerSkill
- test-data-auditorSkill
- test-impact-selectorSkill
- test-suite-evaluatorSkill
- ticket-readiness-reviewerSkill
- ticket-to-tddSkill
- ui-crash-hunterSkill
- visual-regression-reviewerSkill
- wcag-auditorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
Init: check the config; record the window.
- Distinctive: line 65
End: after the window, a last summary.
- Distinctive: line 81
Another deploy in the window: start a new watch for it; correlate each anomaly with the latest deploy.
≈ “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
Hypercare anomaly watcher
Mission
For the 24 to 72 hours after a release, check production on a schedule and say what changed, whether it started with the release, and what a person should raise:
- Datadog: any metric a query returns (error rates, latency percentiles, throughput, job errors).
- Sentry: new issues first seen in the release, and old issues whose rate jumped.
- Ongoing: each scheduled run is a tick; anomalies must persist; drafts are updated, not duplicated; recoveries are noted.
post-deploy-validator checks actively minutes after the deploy; this skill watches passively for days. A draft can become a bug-reproducer's input.
Non-negotiable rules
- Read-only: GET requests to the monitoring APIs only, with
DD_API_KEY/DD_APP_KEYandSENTRY_AUTH_TOKENfrom the environment. Keys and tokens are never printed or written, and never sent to another origin on a redirect (safe_http.py;python scripts/sources.py --self-test). - Every anomaly carries its statistics: value, baseline samples, median and MAD (or expected count), score, threshold and the query.
- Not enough baseline is
not_assessed(fewer than 7 samples, no points, a failed fetch), never normal. - Persistence: one anomalous tick is
suspected; two in a rowconfirmed. A new Sentry issue is confirmed as soon as it reaches the user or event threshold. - Correlation is earned: "correlated with the release" only if the anomaly began after the deploy and the hour before the deploy was normal (or the issue was first seen in the release).
- Seasonality: the baseline is the same hour of the day on previous days, so a nightly spike that happens every night is normal.
- Drafts only,
status: draft, with an owner who raises them. Never page, never create or comment on incidents, monitors or issues. Recoveries are noted; drafts are never closed by the skill. - No "all clear": say "no anomalies above the thresholds in the metrics watched", and list what wasn't assessed.
- No event payloads: Sentry titles, culprits, counts and links only.
- The schedule is the user's:
initprints a cron line; the skill never installs it.
Inputs
hypercare.json (schemas/hypercare_config.schema.json): the release (service, version, deploy time),
window_hours (72), tick_minutes (60), baseline_days (14), incident_owner, critical_services, the
Datadog queries (id, query, kind rate/latency/gauge/count, service, direction, thresholds) and the
Sentry project (org, project, service, thresholds).
Workflow
python scripts/watch.py init --config hypercare.json --state state/
python scripts/watch.py tick --state state/ # on the schedule; --now and --from-dir for replays
python scripts/render_report.py state/ [--brief]
python scripts/validate_watch.py state/- Init: check the config; record the window; give the user the schedule line to install.
- Each tick (or when asked "how is the release doing?"): run
tick; read the changed states; for a new or updated draft, addsuggested_actionsand notes (what to look at, who decides on a rollback), thenrender_report.py --write-drafts. - Report: the headline (what's confirmed, what recovered, what isn't assessed), the drafts, and the limitations. Hand drafts to the owner; never raise them.
- End: after the window, a last summary.
Rating
See RUBRIC.md. Draft severity: SEV2 for a confirmed error-rate anomaly on a critical service or a new
release issue affecting at least sev2_users users; SEV3 for other confirmed, correlated anomalies.
Output
state/watch.json (schemas/watch_state.schema.json): config and hash, window, schedule, tick summaries,
item states (with history and correlation), drafts, summary, limitations. state/ticks/<n>.json: each
tick's inputs, evaluations and requests. state/incidents/<id>.json and .md: the drafts.
Edge cases
- Low traffic: rates over few requests are noisy; watch the count instead, or raise
min_abs_change(amin_volumeoption is not built in v1). - Another deploy in the window: start a new watch for it; correlate each anomaly with the latest deploy.
- Monitoring outage:
not_assessedfor that tick. - Weekly patterns: the default baseline ignores weekdays; say so when it matters.
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.

