Skip to main content
ClaudeWave
Skill283 repo starsupdated 25d ago

cowork-folder-organizer

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.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/OneWave-AI/claude-skills /tmp/cowork-folder-organizer && cp -r /tmp/cowork-folder-organizer/cowork-folder-organizer ~/.claude/skills/cowork-folder-organizer
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# 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.
5. **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`.
6. **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`
accessibility-auditorSkill

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

agent-armySkill

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

agent-swarm-deployerSkill

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

agent-team-builderSkill

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

agent-to-agentSkill

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

ai-readiness-assessmentSkill

Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.

animateSkill

Generate animated videos and motion graphics from natural language descriptions. Creates a standalone Vite + React project with Framer Motion scenes that auto-play in the browser. Use when the user wants to create animations, motion graphics, video intros, animated presentations, or product demos.

api-documentation-writerSkill

Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.