Preface¶

A red-bulging C drive is a frequent issue for Windows users. Directly using disk cleanup tools or casually deleting folders often results not in freeing up space, but in deleting project files, cloud drive sync directories, or touching system-protected files. This risk is even higher when applied to automated Agents: a single erroneous deletion command from an Agent has a greater impact than a single manual misclick.

Here we introduce C Drive Cleanup Master, a Skill that breaks “Measure—Scan—Clean” into a disciplined pipeline. The focus is not on cleaning more, but on cleaning verifiably, with red lines blocking errors before deletion occurs.

What is this¶

C Drive Cleanup Master is a Windows-oriented expert process Skill. It is used to perform a structured C drive space cleanup when users say things like “Clean up C drive,” “C drive space insufficient,” “C drive is red,” “Disk cleanup,” “WinSxS too big,” “Windows Temp taking too much space,” “Help me free up C drive space,” or “C Drive Cleanup Master.”

It is maintained by community publisher user_839f3063 and hosted on SkillHub at the coordinates @user_839f3063/c-drive-cleanup-master. The current version is 1.9.2, categorized under it-ops-security. The SkillHub page rating is 100,000 with 1,325 downloads. Official API: https://api.skillhub.cn/user_839f3063/c-drive-cleanup-master, Page: https://www.skillhub.cn/skills/user_839f3063/c-drive-cleanup-master.

In one sentence: It is not just writing another cleanup script; it solidifies the pitfalls the author encountered during a real 4.7GB to 27GB cleanup into a discipline, ensuring the Agent follows the process.

The Six Phases of the Cleanup Pipeline¶

The Skill embeds a six-phase cleanup pipeline with a fixed sequence:

1. Temporary cache cleanup (Windows Temp, etc.);
2. WinSxS governance via DISM rather than direct directory deletion;
3. Volume Shadow Copy handling;
4. System cache recyclerization (ensuring rollback capability);
5. Disabling search indexing;
6. WeChat-specific sub-module.

Each phase measures first before acting; it is not about “deleting as soon as a directory is seen.”

Red Lines and Three Disciplines¶

The value of this Skill lies mainly in its discipline, which is worth a separate section in the main text.

Safety Red Line¶

Never delete personal data or project data by mistake. The author explicitly states in the introduction that this is a built-in red line, not a post-mortem remediation note.

Measurement Discipline¶

Three stable reads via fsutil. Manual caps on directory traversal are prohibited—one of the pitfalls the author encountered was space miscalculation caused by traversal caps. Duplicate calculation of junction targets during scanning leads to inflated space estimates; this is also specifically listed.

Estimation Discipline¶

Authoritative breakdowns must be run before deletion; “rule of thumb” estimates of freed space are prohibited. The introduction cites ResetBase’s near-zero benefit as a counter-example: it looks like it takes up space, but the actual cleanup benefit is close to zero.

Pitfall Checklist (Author’s Real-world Testing)¶

The author listed pitfalls encountered during real cleanups in the introduction, which can be used directly as a pitfall avoidance checklist:

• Traversal caps causing space miscalculation;
• ResetBase yields almost zero benefit;
• The “three-step axe” for deletion in cloud drive sync environments;
• Protected services must go through the SCM API, not direct registry modification;
• Domestic antivirus kernel self-protection may lock files;
• Sandboxes may block sc/reg but allow Dism/vssadmin; permission paths must be selected based on actual conditions;
• Instantaneous space fluctuations during cleanup are normal phenomena, not errors;
• System locked files cannot be force-deleted if they do not go to the Recycle Bin;
• Junction targets being calculated repeatedly leading to inflated estimates.

WeChat Specific Sub-module¶

The WeChat directory is a common source of C drive bloat. The Skill provides automatic WeChat directory detection, relying neither on users manually finding paths. WeChat-specific cleanup is attached as an independent sub-module in the sixth phase of the pipeline, handled separately from general temporary file cleanup to avoid mistaking chat data for cache and deleting it.

Safety Gates: dry-run and –confirm¶

All deletion scripts are written in pure ASCII and default to dry-run. They will only perform actual deletions when explicitly adding --confirm. This means the first run only outputs a report and a deletion list by default; the user manually verifies the list before deciding whether to confirm execution.

The deletion strategy is graded: “System junk can be deleted on restart / Deep governance items must go to the Recycle Bin.” Ordinary system junk can be deleted directly, while items involving deep governance must go to the Recycle Bin first to ensure recoverability.

Progress and Reporting¶

The scanning process includes a real-time heartbeat, preventing the caller from waiting indefinitely during long scans. The cleanup results output an HTML visualization report, facilitating direct inspection of which directories occupied how much space and how much space was freed.

Regarding error code handling, the Skill translates raw error codes returned by Windows into human-readable language, rather than throwing codes like 0x80070005 directly to the user.

Installation and Activation¶

Official API: https://api.skillhub.cn/user_839f3063/c-drive-cleanup-master

The materials do not provide a general installation command or configuration fields, so no guesses are made here. Please install according to the instructions on the official SkillHub page during actual use. The installation source is community, and tags show requires_api_key=false, meaning no API key is required.

Applicable Scenarios and Limitations¶

Suitable for: Troubleshooting and cleaning C drive space insufficiency on Windows desktops/servers; scenarios where the Agent’s cleanup process needs to be auditable and rollback-capable; scenarios where WeChat chat files fill up the C drive.

Notes:

• This is a Windows-only Skill; it is not applicable to macOS/Linux environments;
• Cleanup involves system-protected files and relies on system permissions such as DISM and SCM API, requiring an environment with administrator privileges;
• Domestic antivirus software, cloud drive sync software, and sandbox policies all affect whether deletion takes effect. If a file cannot be deleted, check these three causes first;
• Dry-run is enabled by default, but actions after --confirm are irreversible. Deep governance items rely on the Recycle Bin as a fallback. It is recommended to verify the deletion list before execution.

Conclusion¶

What C Drive Cleanup Master solves is not “how to delete,” but “how to measure accurately before deleting, how to grade during deletion, and how to report after deletion.” Measurement discipline, estimation discipline, safety red lines, the six-phase pipeline, and default dry-run constitute a complete, verifiable cleanup process. The author validated these pitfalls during a real 4.7GB to 27GB cleanup, representing a process design based on practical combat.

Official API: https://api.skillhub.cn/user_839f3063/c-drive-cleanup-master