skills/skills/disk-master/SKILL.md

name, description

name

description

disk-master

Diagnose Windows disk usage with the bundled read-only disk-master.exe. Use when a user asks why C: or another Windows drive is full, wants the largest files or folders, needs AppData or installed app/game space analysis, or asks for a SpaceSniffer-style HTML disk report. The scan stays local and does not delete, uninstall, move, or clean anything. Do not use for non-Windows or network-drive analysis, or as an automatic cleanup tool.

Disk Master

Disk Master collects Windows drive data as JSON, explains what is consuming space, and can turn the same JSON into an interactive HTML report.

When to use

Use it for:

• Diagnosing a full Windows drive or low free space.
• Finding the largest directories, files, and file types.
• Inspecting AppData, user folders, installed applications, or games.
• Producing a local SpaceSniffer-style disk report.
• Getting an application inventory or a quick text-only disk summary.

Use another approach for non-Windows systems, UNC/network drives, or requests to automatically delete, uninstall, move, or clean data. Disk Master may identify candidates for review; it does not prove that a file is safe to remove.

Safety boundary

The executable does not modify scanned user data. This workflow writes the requested JSON and, when requested, an HTML report generated from that JSON; elevation may also use temporary status/output files for process handoff. Treat every recommendation as review-only and state that no cleanup was performed.

Workflow (SOP)

1. Choose the operation from the user's goal:

   • Full diagnosis or final report: scan --scan full.
   • Fast, incomplete estimate: scan --scan quick.
   • Installed applications only: apps.
   • Short text-only overview: summary.

2. Resolve the target drive. If the user did not name one, list available Windows drive letters and ask which to scan. Do not silently assume C:.

3. Before every scan or summary, ask once whether the user allows a Windows UAC prompt. Explain that approval lets --mode auto use the faster NTFS/MFT path when eligible; declining keeps the local read-only scan in normal mode. Combine this with the drive question when both are needed. apps does not require this scan confirmation.

4. Infer scope and output from the request instead of asking a confirmation checklist. Words such as “quick”, “rough”, or “estimate” select quick; “complete”, “full”, “final”, or “report” select full. Otherwise use full. Generate HTML only when the user asks for a report, visualization, treemap, or SpaceSniffer-style view.

5. For each JSON-producing operation, create an explicit absolute output path. A drive scan and its optional HTML report share one timestamped basename: disk-master-<drive>-<YYYYMMDD-HHmmss>.json and .html. Remove the colon from the drive token, for example disk-master-C-20260519-170000.json and disk-master-C-20260519-170000.html. Name an app-only inventory disk-master-apps-<YYYYMMDD-HHmmss>.json.

6. Run the bundled executable from the skill directory. Use --mode auto for normal operation and add --elevate only after the user approves UAC:

   disk-master.exe scan --drive C: --scan full --mode auto --out <absolute-json-path>
   disk-master.exe scan --drive C: --scan quick --mode auto --out <absolute-json-path>
   disk-master.exe scan --drive C: --scan full --mode auto --elevate --out <absolute-json-path>
   disk-master.exe apps --out <absolute-apps-json-path>
   disk-master.exe summary --drive C: --mode auto
   

   Optional public flags are --depth <N>, --top <N>, --no-apps, and --mode <auto|mft|walk>. --depth limits quick-scan depth and JSON tree depth. Prefer auto; force mft or walk only when the user requests it or when diagnosing scan behavior.

7. On a successful scan, use the command's status output as the authoritative JSON path. For apps, use the explicit output path after a successful exit. Read large JSON in chunks or extract relevant fields. Cover the disk state, scan completeness and errors, largest directories/files, extension totals, user folders, AppData hotspots, applications, and advice that materially affects the answer. Label a quick scan as incomplete.

8. If HTML was requested, read template.html, replace the single %%DATA%% marker with the raw JSON text, and write the matching .html path from step 5. The CLI has no report command.

9. Present the result in this order: concise diagnosis, highest-impact findings, uncertainty or scan errors, JSON/HTML absolute paths, then the safety note that all actions remain suggestions and no cleanup occurred.

If a command fails or UAC is declined/cancelled, report the error plainly and offer the non-elevated --mode auto scan when applicable. Do not claim an output file exists unless the command reported success.