MAC PARA Organizer
kellysun2258741977-source/mac-para-organizer
Reorganiza seu Mac em estrutura PARA sem quebrar nada.
Ver no GitHubSkill para Claude Code que organiza um Mac caótico em estrutura PARA (Projects, Areas, Resources, Knowledge, Archive) com segurança. Navega armadilhas do macOS como permissões TCC, venvs Python, dados de apps e iCloud, criando um plano antes de executar.
Instalação
npx convez-ai kellysun2258741977-source/mac-para-organizer1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Organizar Desktop, Downloads e Documents acumulados
- Limpar iCloud e Google Drive duplicados
- Arquivar dados de apps inutilizados respeitando permissões
- Deduplicar versões de arquivos e renomear por conteúdo
- Manter consistência futura com mapa de arquivo (_file-map.md)
Veredito

Skill bem pensado que resolve um problema real de usuários macOS — desembaraçar anos de desordem sem destruir venvs, dados de app ou documentos críticos. Implementação cuidadosa dos "traps" do macOS demonstra experiência. Recomendado para quem já usa Claude Code e quer delegar organização de verdade.
README
A tradução para o português deste README ainda está na fila.
🗂️ mac-para-organizer
Turn a chaotic Mac into a clean, durable PARA filing system — with an AI doing the heavy lifting, safely.
A Claude Code / Codex skill: point your AI agent at a messy Mac and it organizes everything folder-by-folder — Desktop, Downloads, Documents, Pictures, code, iCloud, Google Drive — into a PARA structure, while never breaking apps, touching secrets, or deleting anything you can't recover.
Why
A real Mac, after a year of use:
147 GB game you stopped playing · a Desktop buried in screenshots and scraper output · the same résumé in five slightly-different versions · app libraries dumped in
~/Moviesand~/Documents· an iCloud that's full of folders you can't even open ·Gemini_Generated_Image_4321wt4321wt.png× 20.
You could spend a Saturday on it. Or you let an agent do it — but a naive agent running mv and rm will hit Operation not permitted walls, break Python venvs, orphan app data, or delete a court document. This skill is the playbook that does it right.
What it does
- 📋 Survey → propose → execute → verify, one folder at a time. You approve the plan before anything moves.
- 🗂️ Sorts everything into PARA (
01_Projects / 02_Areas / 03_Resources / 04_Knowledge / 90_Archive). - 🏷️ Renames by content (opens/renders files to name them), dedupes versioned copies, archives unused app data.
- ☁️ Cleans iCloud and Google Drive — minimizes space, hides empty app folders, keeps one canonical copy of duplicated notes.
- 🍎 Handles the macOS traps a naive script gets wrong (see below).
- 🗺️ Leaves a
_file-map.mdbehind so future sessions (and other agents) keep filing things consistently.
The structure
~/Documents/
├── 01_Projects/ active, time-bound projects
├── 02_Areas/ ongoing responsibilities (job search, finances, health…)
├── 03_Resources/ reference material (PDFs, books, configs)
├── 04_Knowledge/ notes vault, prompts, AI-generated visual cards
└── 90_Archive/ retired projects + unused app data
Names localize freely (01_项目 / 02_领域 / 03_资源 / 04_知识库 / 90_归档). Full rationale in reference/para-structure.md.
Install & use
As a Claude Code skill (recommended)
# clone into your skills directory (or a plugin path)
git clone https://github.com/<you>/mac-para-organizer.git
Then just ask Claude Code, in any folder:
"My Mac is a mess — organize my files." • "Sort out my Desktop and Downloads." • "Clean up iCloud, it's full."
The skill triggers on those intents and walks you through it folder-by-folder. It always proposes a plan first.
With Codex / other agents
Point the agent at SKILL.md (and the reference/ docs). It's plain Markdown — any capable coding agent can follow the playbook. Add a one-line pointer to it in your AGENTS.md.
By hand
Even without an agent, SKILL.md + reference/ is a complete manual for organizing a Mac the PARA way. Copy examples/file-map-template.md to your own ~/Documents/_file-map.md and fill it in.
The macOS traps it knows about
Full list in reference/macos-gotchas.md. Highlights:
| Trap | What goes wrong | The fix |
|---|---|---|
| TCC protection | Operation not permitted on Photos Library, iCloud Drive, app containers | Grant Full Disk Access then restart the app, or move via Finder |
| iCloud "app folders" | They're projections — mv/chflags won't hide them | System Settings → iCloud → toggle the app off (empty apps only) |
chflags hidden | Hides from Finder while the app still works (ls still lists it) | Use for libraries you keep but don't want cluttering the view |
| Moving a Python venv | Absolute paths bake in — it dies | Recreate: capture deps → python3 -m venv → reinstall |
| MAS apps are root-owned | terminal mv → Permission denied | Uninstall via Launchpad / Finder (admin auth) |
What it will never do without asking
- Read, move, or delete
.env, keys, credentials, API tokens. - Move or delete legal / ID documents (court files, passports, bank cards) — it surfaces them and stops.
- Run destructive ops (
rm -rf, empty the Trash, uninstall paid apps, delete cloud data) without explicit confirmation. - Reorganize system territory (
~/Library, dotfiles, app containers) — they're left exactly as they are. - Edit your agent config (
CLAUDE.md/AGENTS.md) without asking.
Deletes go to the Trash, never rm -rf. You empty it after reviewing.
Repo layout
mac-para-organizer/
├── SKILL.md # the skill — methodology + triggers
├── reference/
│ ├── para-structure.md # the PARA buckets, explained
│ ├── decision-tree.md # "I have a file, where does it go?"
│ ├── macos-gotchas.md # TCC, FDA, chflags, venvs, iCloud projections
│ └── cloud-cleanup.md # iCloud + Google Drive
├── examples/
│ └── file-map-template.md # drop-in template for your own _file-map.md
├── assets/index.html # one-page visual overview
├── LICENSE
└── README.md
License
MIT — take it, use it, adapt it. See LICENSE.