agentleFS
kryptophonikkryptophonik/SRE-Skills/.claude/skills/sre-oncall-handoff/SKILL.md

sre-oncall-handoff

Skill4 starsChanged 25 days agoMITView on GitHub

Use at shift change or when asked for an on-call summary: open incidents, alerts that fired, noisy alerts, ongoing risks, pending changes and follow-ups. Read-only.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

On-call Handoff

Safety gates (REQUIRED)

  1. Read-only diagnosis first.
  2. Propose each change with risk (low/med/high) and reversibility.
  3. Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
  4. Act only as approved, verify, and stop and escalate if anything gets worse.

Full rules: sre-safety-gates. Read-only MCP setup: sre-safety-gates/references/mcp.md.

Workflow

  1. Set the window (default: last shift, e.g. 12 h or 7 d for weekly rotations).
  2. Collect, read-only:
    • Incidents and alerts: sre-pagerduty-opsgenie. Count pages with its capped paginated scripts (bash ../sre-pagerduty-opsgenie/scripts/pd_incidents.sh --since … --until … --json > "$W/pages.jsonl" && grep -c . "$W/pages.jsonl", with W="$(mktemp -d)"; Opsgenie bash ../sre-pagerduty-opsgenie/scripts/og_alerts.sh). The default API page of 25 undercounts; a MAX_PAGES warning means the count is a lower bound. A non-zero exit means the data is unavailable, not zero. The scripts exit 2 on a missing key, wrong region, unreachable API or HTTP error and print nothing on stdout. Write "pages: unavailable (<error>)" in the handoff, never 0, and never pipe the script straight into wc -l (that prints 0 on failure).
    • Open problems: sre-dynatrace; firing alerts: sre-prometheus-grafana, sre-datadog.
    • Deploys and changes: CI/CD history, sre-change-safety log, Terraform runs.
  3. Group alerts by service; flag noisy (fired 3+ times, no action) and missing-runbook alerts.
  4. List open risks: degraded SLOs, error budget burn, expiring certs (sre-expiry-audit, and sre-emudhra-ca-check/sre-php2shell-check if either incident is still open), pending maintenance.
  5. Draft the handoff note; mark unknowns [TBD].
  6. Present for review; post only after approval.

Template

# On-call handoff — [team] — [from] → [to] — [date]

## Open incidents
- [ID] [sev] [service] — [status] — [owner] — [next step]

## Pages this shift
| Time (UTC) | Alert | Service | Action taken | Noisy? |
|---|---|---|---|---|

## Watch list / risks
- [e.g., checkout error budget at 30%]

## Changes in flight / scheduled
- [deploy, migration, maintenance + time]

## Follow-ups
- [ ] [ticket / runbook fix / alert tuning] — [owner]

## Stats
- Pages: [n] (off-hours: [n]) — Incidents: [n] — Toil hours: [n]

Output

  • Completed handoff note (template above) plus list of noisy alerts for sre-slo-alerting

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.