mcpbeat Sign in

Cowork Folder Organizer Skill for Claude

Cowork-style cleanup of a messy folder or shared drive -- classifies every file, proposes a target structure, renames to a consistent convention, deduplicates, and writes an index. Use on Downloads, Desktop, client folders, or team shared drives.

877 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OneWave-AI/claude-skills --skill cowork-folder-organizer

The instruction itself

6 sections, as written by the author

Cowork Folder Organizer

Turn a chaotic folder into an organized, navigable workspace the way Claude Cowork works through a directory: inventory everything first, propose before moving, then execute with a full undo trail. Never destroy information -- every move is logged and reversible.

Input

Take a directory path. If none is provided, ask for one. Confirm scope before touching anything: subdirectories included or not, and whether any paths are off-limits.

Workflow

  • Inventory. Walk the directory. For every file record name, extension, size, modified date, and a one-line content summary (read headers/first lines for documents, metadata for media). Do not open files larger than 50MB; classify by name and type only.
  • Classify. Group files into categories inferred from the actual contents -- not a generic template. Typical clusters: active project files, reference material, financial documents, contracts, media/assets, installers and archives, duplicates, junk (temp files, ~$ locks, empty files).
  • Detect duplicates. Match by checksum first, then by near-identical names with version suffixes (final, final2, v3, (1)). Identify the canonical copy (newest complete version) and mark the rest.
  • Propose. Present the target folder tree, the naming convention (default: YYYY-MM-DD-descriptive-name.ext for dated documents, client-project-doctype for client work), the duplicate resolution list, and the junk list. Wait for approval before moving anything.
  • Execute. Create the structure, move and rename files, quarantine duplicates and junk into _review-before-deleting/ -- never delete outright. Log every operation as old-path -> new-path in _organizer-log.md.
  • Index. Write INDEX.md at the root: the new tree, what lives where, and a table of the 20 most recently active files so the owner can re-orient instantly.

Rules

  • Propose first, move second. Never reorganize without showing the plan.
  • Never delete. Quarantine to _review-before-deleting/ and let the human pull the trigger.
  • Preserve anything that looks like the only copy of original work (contracts, signed PDFs, raw footage) in place if its location seems intentional.
  • Keep names human-readable. No hash suffixes, no ALL_CAPS, no spaces-to-underscores churn on files that are already well named.
  • If the folder is a shared drive, flag files other people may have links to before renaming them.
  • Report at the end: files processed, moved, renamed, duplicates found, space reclaimable.

Scheduled Mode

When run as a recurring Cowork scheduled task (e.g. weekly on Downloads), skip the approval step only for previously approved rules: apply the established convention to new files, quarantine new junk, and post a summary of what moved. Anything that does not match an existing rule goes to _needs-decision/ and is listed in the summary.

Quick Commands

  • "Organize [path]" -- full workflow with proposal
  • "Just show me the plan" -- phases 1-4 only, no changes
  • "Dedupe only" -- duplicate detection and quarantine, no restructuring
  • "Undo" -- reverse the last run from _organizer-log.md

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take onewave-ai/cowork-folder-organizer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.