Menu

Individual skill

cowork-folder-organizer

0upvotes

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.

cowork-folder-organizer/SKILL.md

Read pinned source

Source commit b2267d9171af4f56848d82992381b20b89b44056

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
425
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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

1. **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.
2. **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).
3. **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.
4. **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.
Back to top