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

sre-oncall-audit

Skill4 starsChanged 25 days agoMITView on GitHub

Use before rotation changes, after a migration, or quarterly: read-only audit of PagerDuty/Opsgenie schedules and escalation policies for coverage gaps, single-person layers, DST, loops, unreachable users.

  • Reads credentials

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
  1. Distinctive:

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

    line 12
  2. Distinctive:

    Set the window: default now to +14 d. Extend it to cover the next DST change.

    line 21
  3. Distinctive:

    Stop: when every check has a finding or a pass, or if a key lacks read access (report the 403 and stop).

    line 30

≈ “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 Schedule and Escalation Audit

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. This skill is read-only. Editing schedules, adding overrides, changing policies and fixing contact methods are writes: propose them, then wait for approval.

Related: sre-pagerduty-opsgenie (adapter, scripts), sre-oncall-handoff; Opsgenie migration: opsgenie-migration.md. Requires sre-pagerduty-opsgenie installed for its scripts.

Workflow

  1. Set the window: default now to +14 d. Extend it to cover the next DST change.
  2. Run the automated checks (read-only):
    • PagerDuty: bash ../sre-pagerduty-opsgenie/scripts/pd_audit_schedules.sh --since <ISO8601> --until <ISO8601> (gaps, single-person layers, policies with no service, empty levels, users with no contact methods or notification rules)
    • Opsgenie: bash ../sre-pagerduty-opsgenie/scripts/og_oncall.sh (schedules with nobody on call now)
    • Env: PD_API_KEY / OG_API_KEY (read-only keys), PD_REGION / OG_REGION = us|eu
    • Exit 2 (missing key, wrong region, unreachable API, HTTP error) means the audit didn't run: report it as not audited, never as "no findings".
  3. Run the manual checks in schedule-escalation-audit.md: time zones/DST, loops and repeat counts, overlapping overrides, timeouts, and the Opsgenie equivalents.
  4. Rate each finding: high means a service can page nobody; medium is single-person coverage or an unreachable user; low is cleanup.
  5. Draft fixes as proposals with risk and rollback. Don't apply them.
  6. Stop when every check has a finding or a pass, or if a key lacks read access (report the 403 and stop).

Thresholds (minimum layer size, timeouts) are team policy: state the ones you used.

Output

# On-call audit — [team/account placeholder] — [window UTC]
| # | Severity | Object (type/name/ID) | Finding | Proposed fix (WRITE, needs approval) |
|---|---|---|---|---|

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.