wsl-debloat — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited wsl-debloat (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Clears caches and frees disk space. The script handles all cleanup - your job is to decide which flags to pass based on what the user wants.
| Flag | What it does |
|---|---|
--scan | Report purgeable sizes only - no changes |
| _(none)_ | WSL caches only - always safe |
--vps | Also prune Docker build cache, unused images, volumes on VPS via SSH |
--clean-lab | Also remove node_modules from mad-house projects |
| Both | Full cleanup: WSL + VPS + mad-house node_modules |
Always run scan first so you know what's available before touching anything:
~/.claude/commands/wsl-debloat/scripts/debloat.sh --scanReport the sizes to the user. If VPS shows "(ssh failed)" or is missing, note that --vps won't work.
If the user asked for everything or the scan shows meaningful sizes, proceed. If they only said "free disk space", infer from context: WSL caches are always safe, VPS pruning requires explicit intent.
~/.claude/commands/wsl-debloat/scripts/debloat.sh [--vps] [--clean-lab]Read the BEFORE / AFTER disk usage and the per-cache summary. Report:
--vps)--clean-lab)One paragraph is enough unless the user wants details.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.