disk-pressure-triage

Find what is filling a volume before deciding whether to delete anything, so the deletion is informed rather than hopeful.

Procedure

start start. Goes next to s1
check Confirm the volume is actually full. Goes on_fail to s9; next to s2
check Find the largest directories. Goes on_fail to s9; next to __end_success
escalate Escalate to the platform team. Terminal
end success. Terminal

Open the graph on its own page — larger, printable, and an address you can send.

Walk it without running it — you answer what your environment would answer, and the path, the capabilities, the approvals and the distance back to an undo come out of the document. Nothing executes; there is no Run button here and there will not be one.

Trust

T2 · attested 2026-10-11 · runbooks.directory

Nobody has attested this record. That is the ordinary case: T2 is what the catalog can check on its own, and T3 needs somebody to run the procedure and sign for it.

Link liveness has not been checked: it needs a network and the catalog builds without one. Run pnpm gates --online where there is one.

Steps

s1 check — Confirm the volume is actually full
s2 check — Find the largest directories
s9 escalate — Escalate to the platform team

Capabilities

This is a privilege request. Check it against your own allowlist before running.

cli:df — used by s1
cli:du — used by s2

Provenance

Source: https://runbooks.directory/r/std/disk-pressure-triage/source.md
Fetched: 2026-09-02
Source last checked: not since it was captured on 2026-09-02 — recorded as current
Licence: CC-BY-4.0
How it got here: Written by this catalog's maintainers and reviewed in full.
Highest risk in this procedure: read-only

Take it with you

SKILL.md — the record as an Agent Skills file
workflow.yaml — Open Workflow DSL 1.0.3, for a runner
record.json — the catalog's own JSON
graph.svg — the graph, standalone

Run it under supervision

Runs here, on your machine, under supervision: every step is proposed before it happens, an approval gate stops for you, and a failed expectation goes where the procedure says rather than on to the next step. Nothing is sent anywhere. To supervise an agent that is doing the work instead, runbooks hook sits in its tool-call path.

npx @runbooks/cli run std/disk-pressure-triage@1.0.0 --as "$(whoami)" \
  --input mount=<mount point under pressure>