Check disk pressure
Agent capability that loads only when the task needs it. The Skills layer of QA Veritas.
npx -y skills add qa-veritas/skillpack --skill check_disk_pressureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Decide whether a node's storage is under pressure and recommend an action. Use when a mount is filling, a workload reports no-space-left, or capacity planning needs a verdict.
SKILL.md
1.5 KB, as published. Nobody here has run it
check_disk_pressure
Purpose
Turn raw storage usage into a decision. "85% full" is not a decision;
"/data will hit 100% in ~6 hours at the current write rate; the top
consumer is the index store; reclaim 40 GB of expired snapshots first"
is.
Inputs
df_output_or_metrics—df -h/df -itext, or per-mount used/total bytes (two timestamped samples enable a fill-rate estimate).thresholds(optional) — warn/critical. Default warn 80%, critical 90%; inode warn 85%.
Outputs
Per mount: state (ok/warn/critical), time_to_full (if a rate
exists), top_consumers, and a recommended_action that prefers
reclaiming over resizing.
Prompt template
Assess disk pressure. Parse usage per mount including inodes (inode exhaustion looks fine on
df -h). If two samples exist, compute a fill rate and time-to-full (state the linear assumption). Identify top consumers. Recommend the smallest reversible action first, and call out when a "full disk" is really a retention/rotation bug.
Examples
- Index mount at 86%, no rate data → critical by threshold; check shard count and retention before resizing.
- Root at 92% from inodes, 30% bytes → byte view fine, inode view critical; target the directory with millions of small files.