[Free] Computer Organizer Skill

Dickie, Cole, and Mitch make the case that prompts have a ceiling and that Claude Desktop’s Cowork mode — which can touch your actual filesystem — represents a step change. The article contrasts web-based chatbot responses (a numbered list about organizing files) with Cowork actually moving 3,000+ files, then introduces “skills” as the mechanism for making that behavior repeatable and consistent.

Key Takeaways

Prompts vs. skills distinction: A prompt gets you a one-off response; a skill is a plain-English instruction file that ensures Cowork executes the same way every time. The analogy used is a temp worker on day one vs. a trained employee with years of tenure. Without a skill, Cowork “wings it” and may organize differently on each run.

Computer Organizer skill uses GTD framework: Files are classified into four buckets (Action, Reference, Trash, Waiting) using a fixed decision tree. Files over 100MB get flagged, duplicates are surfaced, and a weekly review mode scans only new files since the last run via a log file.

Alex Lieberman (Morning Brew) example: Has a skill that runs every Monday scanning Notion, Slack, Gmail, and Cowork session history to identify manual processes that should become new skills. The meta-pattern: using AI to find more work to delegate to AI.

Broader skill ideas for writers: newsletter drafting in your voice, research folder scanning and insight extraction, content repurposing (one newsletter into 10 social posts, email teaser, blog version), weekly content calendar review.

RDCO Mapping

The skills architecture described here is essentially what we have already built with our ~/.claude/skills/ directory. The GTD-based file classification pattern could be adapted for vault inbox triage. The Lieberman “meta-skill” pattern (AI auditing for delegation opportunities) is worth noting as a potential Sanity Check topic — it illustrates the operator-vs-user gap we track.

Post promotes Claude Cowork Bootcamp 2.0 (closing that day).