shared-drive-cleanup
Clean up a shared drive nobody owns — the ownership-first move, the top-down audit that finds the 80% (stale projects, duplicates, ex-employee folders), the archive-don't-delete discipline for shared property, and the norms that prevent regrowth. Use when asked our shared drive is a disaster, clean up the team drive, who owns all these folders, or people are scared to delete anything. Produces the audit map, the archive plan with the fear-killing rule, the ownership assignments, and the going-forward norms.
npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Shared Drive Cleanup Skill Shared drives rot for one structural reason: shared ownership is no ownership. Nobody deletes (it might be someone's), nobody files (whose rule?), and the drive becomes archaeology — ex-employees' folders, three "Marketing" directories, project debris from 2022. The cleanup starts with ownership (one named steward, or nothing sticks), proceeds top-down (folder-level verdicts, never file-by-file), and replaces deletion fear with the archive rule: *nothing is destroyed; everything doubtful moves to a dated archive that nobody has ever actually needed to reopen — but could.* ## What This Skill Produces - **The audit map** — top-level folders × last-modified × apparent owner × verdict (keep / archive / merge) - **The archive plan** — `_archive/2026/` moves, the fear-killing everything-is-recoverable rule, the announcement - **The ownership layer** — steward named per surviving top-level folder; unowned folders can't survive the audit - **The norms** — the placement rules + naming convention + quarterly review that prevent the regrowth ## Required Inputs Ask for these if not provided: - **The drive's shape** — top-level listing with last-modified dates (the
- What This Skill Produces
- Required Inputs
- Framework: The Cleanup Rules
- Output Format
- The Audit Map
- The Archive Move
- Ownership Layer
- Going Forward
- Quality Checks
- Anti-Patterns
What does the shared-drive-cleanup skill do?
Clean up a shared drive nobody owns — the ownership-first move, the top-down audit that finds the 80% (stale projects, duplicates, ex-employee folders), the archive-don't-delete discipline for shared property, and the norms that prevent regrowth. Use when asked our shared drive is a disaster, clean up the team drive, who owns all these folders, or people are scared to delete anything. Produces the audit map, the archive plan with the fear-killing rule, the ownership assignments, and the going-forward norms.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.