agentleFS
kryptophonikkryptophonik/SRE-Skills/.claude/skills/sre-toil-review/SKILL.md

sre-toil-review

Skill4 starsChanged 25 days agoMITView on GitHub

Use for quarterly ops reviews or when on-call load is high: inventory repetitive manual work, score frequency x time x risk, and pick automation candidates.

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

Toil Review

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.

Toil = manual, repetitive, automatable, reactive work that scales with service size and has no lasting value. Target: toil under 50% of SRE time.

Workflow

  1. Collect 4–12 weeks: pages, tickets, runbook executions, manual deploys/requests (sre-pagerduty-opsgenie with paginated fetches, ticket system, handoff notes).
  2. Group into tasks (e.g., "restart stuck consumer", "grant DB access").
  3. Score each task.
  4. Pick top items; choose fix type: eliminate (fix root cause), automate, self-service, or tune alert.
  5. Plan with owner and expected hours saved; re-measure next quarter.

Scoring table

TaskTimes / monthMinutes eachHours / monthRisk if done wrong (1–3)Automation effort (S/M/L)Priority

Priority = hours/month × risk ÷ effort (S=1, M=2, L=4).

Output

  • Toil table, top 3–5 candidates with fix type, owner, expected hours saved

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.