What do I need to use Shared Drive Cleanup?

The drive's shape; The political reality; The team's fear level; Platform.

Is Shared Drive Cleanup free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Shared Drive Cleanup

Q: How do I know the Shared Drive Cleanup output is good?

The skill verifies itself against its own quality checks: A steward exists before any move happens; Verdicts were made at folder level — no file-by-file audit; The announcement leads with the archive-not-delete rule; Every surviving top-level folder has a named steward.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The drive's shape — top-level listing with last-modified dates (the audit works at this altitude; no file inventories)

▸The political reality — whose folders are whose, any sensitive territories (Legal's corner, the exec folder), and whether a steward mandate exists or must be manufactured

▸The team's fear level — has deletion ever caused an incident? The archive rule's prominence scales with the scar tissue

▸Platform — Drive/SharePoint/Dropbox — permissions and versioning mechanics differ; the plan uses the real ones

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓A steward exists before any move happens

✓Verdicts were made at folder level — no file-by-file audit

✓The announcement leads with the archive-not-delete rule

✓Every surviving top-level folder has a named steward

✓The quarterly review is calendared — cleanup without cadence is a photo

⚠️ What it refuses to do

Do not clean without a mandate — unowned cleanups get reverted by the first objector

Do not review file-by-file — the audit dies at folder 40 of 4,000

Do not delete in round one — archive buys the same tidiness without the fear war

Do not leave ghost folders as memorials — the protocol extracts and archives them respectfully

Do not skip the announcement — silent cleanups read as data loss and generate the incident the fear predicted

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="shared-drive-cleanup"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Shared Drive Cleanup is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog