Cleanup
simstudioai/sim
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
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…
MITAuto-check passed
Install Shared Drive Cleanup
$ npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills shared-drive-cleanup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/shared-drive-cleanup .claude/skills/shared-drive-cleanup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "shared-drive-cleanup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/shared-drive-cleanup into .claude/skills/shared-drive-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shared-drive-cleanup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/shared-drive-cleanupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills shared-drive-cleanup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/shared-drive-cleanup .agents/skills/shared-drive-cleanup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "shared-drive-cleanup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/shared-drive-cleanup into .agents/skills/shared-drive-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shared-drive-cleanup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills shared-drive-cleanup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/shared-drive-cleanup .cursor/skills/shared-drive-cleanup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "shared-drive-cleanup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/shared-drive-cleanup into .cursor/skills/shared-drive-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shared-drive-cleanup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/shared-drive-cleanup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills shared-drive-cleanup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/shared-drive-cleanup .gemini/skills/shared-drive-cleanup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "shared-drive-cleanup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/shared-drive-cleanup into .gemini/skills/shared-drive-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shared-drive-cleanup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills shared-drive-cleanupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/shared-drive-cleanup .github/skills/shared-drive-cleanup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "shared-drive-cleanup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/shared-drive-cleanup into .github/skills/shared-drive-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shared-drive-cleanup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills shared-drive-cleanup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/shared-drive-cleanup .opencode/skills/shared-drive-cleanup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "shared-drive-cleanup" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/shared-drive-cleanup into .opencode/skills/shared-drive-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "shared-drive-cleanup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
shared-drive-cleanup- GitHub stars
- 1.4k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 613 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Works in 5 steps: Ownership precedes organization: appoint… → Audit top-down, verdict at folder level:… → Archive, never delete — and say so… → …
- Asked our shared drive is a disaster
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Cleanup Rules and Output Format, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Shared Drive Cleanup is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked our shared drive is a disaster
- Clean up the team drive
- Who owns all these folders
- People are scared to delete anything
Example prompts
- “/shared-drive-cleanup”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Ownership precedes organization: appoint the steward (or become it) before touching anything — cleanups without an owner regress within a…
- Audit top-down, verdict at folder level: last-modified > 12 months + no named owner → archive candidate, whole. Duplicated concepts (three…
- Archive, never delete — and say so loudly: everything doubtful moves to _archive/[year]/[original-name] — visible, searchable, restorable…
- Ex-employee folders get a protocol, not a taboo: steward + the person's former manager skim for the live material (extract to owned…
- Regrowth prevention is norms plus cadence: the surviving structure gets placement rules (folder-structure-designer), the naming line…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Shared Drive Cleanup loads about 1.3k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 613 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 613 words, ~1,319 tokens.
Download SKILL.mdSave it as
.claude/skills/shared-drive-cleanup/SKILL.md (or your agent's skills folder).- name
- shared-drive-cleanup
- description
- 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.
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 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
Framework: The Cleanup Rules
- Ownership precedes organization: appoint the steward (or become it) before touching anything — cleanups without an owner regress within a quarter. Every top-level folder that survives gets a named steward too; "the team's" folders go to the audit's merge-or-archive pile.
- Audit top-down, verdict at folder level: last-modified > 12 months + no named owner → archive candidate, whole. Duplicated concepts (three Marketings) → one survivor, others merged-then-archived. File-by-file review is how cleanups die; folders are the unit.
- Archive, never delete — and say so loudly: everything doubtful moves to
_archive/[year]/[original-name]— visible, searchable, restorable. The announcement leads with this rule because fear is the blocker: "nothing is being deleted; everything is one search away" converts objectors into shruggers. (Actual deletion happens years later, per the document-retention-map, by the steward, quietly.) - Ex-employee folders get a protocol, not a taboo: steward + the person's former manager skim for the live material (extract to owned homes), then the folder archives whole. The taboo version — untouchable ghost folders — is how drives become graveyards.
- Regrowth prevention is norms plus cadence: the surviving structure gets placement rules (folder-structure-designer), the naming line (filename-convention), and a quarterly 30-minute steward review. A cleanup without the cadence is a before photo.
Show full SKILL.md (189 more words)Show less
Output Format
Drive Cleanup: [drive] — steward: [name]
The Audit Map
| Top-level folder | Last modified | Owner | Verdict |
|---|
The Archive Move
[_archive/2026/ plan · the announcement draft, leading with nothing-is-deleted · the restore-on-request promise]
Ownership Layer
[Surviving folders × stewards · the ex-employee protocol runs on: (list)]
Going Forward
[Placement rules posted · naming line · quarterly steward review, calendared]
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
- The quarterly review is calendared — cleanup without cadence is a photo
Anti-Patterns
- 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
Example Trigger Phrases
- "Our shared drive is a disaster."
- "Clean up the team drive."
- "Who owns all these folders?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/shared-drive-cleanup of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Shared Drive Cleanup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Shared Drive Cleanup this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cleanupsimstudioai/sim | 30k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Android Clean Architectureaffaan-m/ECC | 277k | 4 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Feishu Driveopenclaw/openclaw | 392k | — | ~375 | Automated safety check: Pass | MIT | |
| Cleancatlog22/Claude-Code-Workflow | 2.1k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Lovable Cleanupsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.7k | Automated safety check: Notes | MIT |
Similar skills
Android Clean Architecture
affaan-m/ECC
Applies Clean Architecture to Android and Kotlin Multiplatform projects: module layout, dependency rules, UseCases, Repositories and data layer patterns.
Feishu Drive
openclaw/openclaw
Feishu cloud-storage and comment workflows. An agent skill from openclaw/openclaw.
Clean
catlog22/Claude-Code-Workflow
Intelligent code cleanup with mainline detection, stale artifact discovery, and safe execution.
Lovable Cleanup
sickn33/agentic-awesome-skills
Audits and strips Lovable scaffolding from Vite + React projects — removes lovable-tagger, swaps placeholder assets, prunes unused Radix deps, cleans generated docs, and neutralizes stale…
- Official
Establishing Code Ownership
PostHog/posthog
Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed owners.yaml, products//product.yaml, and .github/CODEOWNERS).
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Shared Drive Cleanup
What does Shared Drive Cleanup 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 Drive Cleanup is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Shared Drive Cleanup?
Shared Drive Cleanup fits situations like: asked our shared drive is a disaster; clean up the team drive; who owns all these folders; people are scared to delete anything.
How do I install Shared Drive Cleanup in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a claude-code`. Or copy the skill folder (skills/shared-drive-cleanup in mohitagw15856/pm-claude-skills) into .claude/skills/shared-drive-cleanup in your project. Claude Code loads it when a task matches its description.
How do I install Shared Drive Cleanup in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a codex`. Or copy the skill folder (skills/shared-drive-cleanup in mohitagw15856/pm-claude-skills) into .agents/skills/shared-drive-cleanup in your project. Codex loads it when a task matches its description.
Can I use Shared Drive Cleanup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill shared-drive-cleanup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/shared-drive-cleanup, .gemini/skills/shared-drive-cleanup, .github/skills/shared-drive-cleanup and .opencode/skills/shared-drive-cleanup in your project.
What does Shared Drive Cleanup need to run?
SKILL.md names no scripts, command-line tools or credentials: Shared Drive Cleanup is instructions for the agent only.
Does Shared Drive Cleanup access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Shared Drive Cleanup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Shared Drive Cleanup use?
Shared Drive Cleanup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Shared Drive Cleanup use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Shared Drive Cleanup?
Skills that share tags, products or a category with Shared Drive Cleanup: Cleanup (simstudioai/sim, 30k stars), Android Clean Architecture (affaan-m/ECC, 277k stars), Feishu Drive (openclaw/openclaw, 392k stars) and Clean (catlog22/Claude-Code-Workflow, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Shared Drive Cleanup?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.