disk-usage
A command-line tool to identify large files, analyze partition usage, and monitor storage on Linux systems.
Install
mkdir -p .claude/skills/disk-usage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2353" && unzip -o skill.zip -d .claude/skills/disk-usage && rm skill.zipInstalls to .claude/skills/disk-usage
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Analyze disk space usage, filesystem mounts, and storage allocation on Linux systems. Identifies large files and directories, checks partition usage, and reports inode consumption. Use when the user asks about disk full errors, free space, storage usage, du/df output, finding large files, or checking which directories consume the most space.Key capabilities
- →Analyzes filesystem mount usage
- →Identifies large directories and files
- →Reports inode consumption
- →Lists block device information
How it works
It utilizes standard Linux utilities like df, du, and find to report on storage allocation and identify space-consuming files.
Inputs & outputs
When to use disk-usage
- →Troubleshooting disk full errors
- →Identifying largest directories and files
- →Checking filesystem mount usage
- →Auditing partition storage allocation
About this skill
Disk Usage Skill
Analyzes disk space and filesystem usage on Linux systems.
Suggested Workflow
- Run
./scripts/diskinfo.shfor a structured overview of mounts, block devices, and top directories. - Check
df -houtput for any filesystem above 80% usage. - Drill into high-usage mounts with
du -h --max-depth=1 /mountto find large subdirectories. - Locate specific large files with
find /path -type f -size +100M.
Commands Reference
Filesystem Overview
df -h- Disk space usage for all mounted filesystems (human-readable)df -i- Inode usage (number of files)lsblk- Block device tree (disks, partitions)mount- Currently mounted filesystems
Directory Size Analysis
du -sh /path- Total size of a directorydu -h --max-depth=1 /path- Size of immediate subdirectoriesdu -ah /path | sort -rh | head -20- Largest files/directories
Finding Large Files
find /path -type f -size +100M- Files larger than 100MBfind /path -type f -size +1G- Files larger than 1GBls -lhS /path | head -20- List files sorted by size (largest first)
Disk Information
cat /proc/partitions- Partition tablecat /proc/mounts- Mount informationstat -f /path- Filesystem statistics
Tips
- Always use
-hfor human-readable sizes - The
ducommand can be slow on large directories; use--max-depth=1to limit recursion - Root filesystem (
/) usage above 90% may cause issues
When not to use it
- →Non-Linux filesystems
- →Real-time performance monitoring
Prerequisites
Limitations
- →du command can be slow on large directories
- →Requires root access for full system analysis
How it compares
It provides a structured diagnostic workflow for disk issues instead of requiring manual command chaining.
Compared to similar skills
disk-usage side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| disk-usage (this skill) | 3 | 4mo | Review | Beginner |
| network-info | 3 | 4mo | Review | Beginner |
| debug-cluster | 2 | 8mo | Review | Intermediate |
| doctor | 1 | 3mo | Caution | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by UKGovernmentBEIS
View all by UKGovernmentBEIS →You might also like
network-info
UKGovernmentBEIS
Gather network configuration and connectivity information including interfaces, routes, and DNS
debug-cluster
openshift
Provides systematic debugging approaches for HyperShift hosted-cluster issues. Auto-applies when debugging cluster problems, investigating stuck deletions, or troubleshooting control plane issues.
doctor
Yeachan-Heo
Diagnose and fix oh-my-claudecode installation issues
replit-advanced-troubleshooting
jeremylongshore
Apply Replit advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Replit support escalation. Trigger with phrases like "replit hard bug", "replit mystery error", "replit impossible to debug", "difficult replit issue", "replit deep debug".
devops-troubleshooter
sickn33
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use PROACTIVELY for debugging, incident response, or system troubleshooting.
vastai-common-errors
jeremylongshore
Diagnose and fix Vast.ai common errors and exceptions. Use when encountering Vast.ai errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "vastai error", "fix vastai", "vastai not working", "debug vastai".