# Org Life Organizer

> Use when the user wants to organize their entire digital life across multiple surfaces at once, or asks where to start. Surveys preferences and recommends which sub-skill to run in what order. Triggers: 'organize my life', 'where do I start', 'clean up everything', 'organize across all my apps', 'set up a personal knowledge graph'.

- Skill: `pooriaarab/org-life-organizer` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add pooriaarab/org-life-organizer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pooriaarab/org-life-organizer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: pooriaarab (https://skillmd.com/u/pooriaarab)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pooriaarab/org-life-organizer

---


# Life Organizer

Master skill for organizing across surfaces. **Survey + dispatch model:** asks scoping questions, recommends a sequence based on dependencies, and tells you which sub-skill to run for each step. Does not invoke sub-skills directly — that keeps each one independently maintainable.

For the catalog of available sub-skills, see [`../organizer/README.md`](../organizer/README.md). For the shared taxonomy, see [`../_lib/taxonomy.md`](_lib/taxonomy.md).

---

## Step 1 — Survey the user

Ask these questions, **one at a time**, before recommending anything:

### Q1. Which surfaces are in scope?

Multi-select. Common options (default = all of "Personal essentials"):

Names prefixed `org-` are top-level, independently loadable skills. Bare names
(`mac`, `notion`, `google-drive`) are still nested under `organizer/<surface>/SKILL.md`
pending content reconciliation — invoke them by that full path.

**Personal essentials**
- [ ] Local Mac (Downloads / Desktop / Documents / caches) → `mac`
- [ ] Apple Notes (iCloud) → `org-apple-notes`
- [ ] Notion → `notion`
- [ ] Google Drive → `google-drive`
- [ ] Gmail → `org-gmail`
- [ ] Contacts.app → `org-contacts`
- [ ] Calendars (Google + iCloud) → `org-gcal`, `org-icloud-calendar`
- [ ] Reminders.app → `org-apple-reminders`
- [ ] Google Tasks → `org-gtasks`

**Communication**
- [ ] iMessage → `org-imessage`
- [ ] Slack DMs → `org-slack-dm`
- [ ] Slack Later / saved messages → `org-slack-later`
- [ ] Email subscriptions / unsubscribe pass → `org-email-subscriptions`

**Media**
- [ ] iCloud Photos → `org-icloud-photos`
- [ ] Google Photos → `org-google-photos`
- [ ] Spotify playlists → `org-spotify-playlist`

**Social bookmarks**
- [ ] X / Twitter → `org-x-bookmarks`
- [ ] LinkedIn → `org-linkedin-bookmarks`
- [ ] Instagram → `org-instagram-saved`
- [ ] Threads → `org-threads-bookmarks`

**Code**
- [ ] GitHub repos / stars / orgs → `org-github`
- [ ] Browser bookmarks (Chrome / Arc / Safari) → `org-browser-bookmarks`

### Q2. Work / personal split?

- **All personal** — single taxonomy across everything.
- **Work + personal split** — separate accounts/folders per surface (e.g. work Gmail vs personal Gmail). Each runs the surface skill twice with different scopes.
- **Personal-only** (skip work surfaces this pass).

### Q3. Taxonomy preference?

Pick one — see [`../_lib/taxonomy.md`](_lib/taxonomy.md) for definitions:

- **Default lowercase** — `personal`, `people`, `ideas`, `finances`, `health`, `legal`, `drafts`, `reference`, `archive` (Recommended for first-time users).
- **PARA** — Projects / Areas / Resources / Archive (Tiago Forte).
- **Karpathy-flat** — minimal hierarchy, tag-heavy, single bucket per surface.
- **GTD** — Inbox / Next / Waiting / Someday / Reference / Archive.
- **Custom** — user provides their own list.

### Q4. Aggressiveness?

- **Dry-run only** — every move is proposed, user approves before write.
- **Move-only auto** — auto-move into folders, never delete.
- **Move + flag deletes** — auto-move, present a delete-candidate list for manual review.
- **Move + auto-delete obvious junk** — empty / 1-char-title items get deleted automatically.

### Q5. First-time setup or maintenance pass?

- **First-time** — full deep-clean. Plan for hours total across surfaces, but each surface is an hour or less.
- **Maintenance** — quick pass, only act on items added since last run. Sub-skills should support a `since:<date>` flag.

---

## Step 2 — Recommend a sequence

Based on the answers, output a checklist with cross-surface dependencies honored:

### Default sequence (first-time, all surfaces selected)

```
1. mac                 ← clean local first; everything else syncs from here
2. contacts            ← clean people foundation; gmail/messages depend on this
3. apple-notes         ← topical organization, no dependencies
4. notion              ← independent of Notes
5. google-drive        ← after local Documents is clean
6. gmail               ← after contacts is clean (label-by-person works better)
7. email-subscriptions ← right after gmail; same surface
8. icloud-calendar + gcal  ← independent of others
9. apple-reminders     ← independent
10. github             ← code surfaces last (lower urgency for daily flow)
11. browser-bookmarks  ← after notion (move research-link bookmarks → notion or reference)
12. icloud-photos + google-photos  ← independent, time-consuming
13. spotify-playlist   ← low priority
14. x/linkedin/instagram/threads bookmarks  ← review and prune; keep what's actionable, archive the rest
15. imessage / slack-dm / slack-later  ← cleanup last; slack-later mirrors keepers to notion, then clears the queue
```

### Maintenance sequence

```
1. mac (downloads + desktop only)
2. gmail (last 7 days)
3. apple-notes (notes added since last run)
4. notion (untitled pages)
5. browser-bookmarks (last 30 days)
```

### Dependencies to honor

| If you run... | Run this first | Why |
|---|---|---|
| `org-gmail` | `org-contacts` | Better person-based labeling |
| `google-drive` | `mac` | Local cleanup before sync upstream |
| `org-email-subscriptions` | `org-gmail` | Same surface, do label cleanup first |
| `org-browser-bookmarks` | `notion` | Bookmarks often belong in Notion as reference |
| `org-apple-notes` | (none) | Independent |
| `notion` | (none) | Independent |
| `org-github` | (none) | Independent |

---

## Step 3 — Dispatch

Output to the user:

```
Recommended sequence:

1. Run mac-organizer:       /run mac
2. Run contacts:            /run contacts
3. Run apple-notes:         /run apple-notes
   ...
```

Each step is a separate session — sub-skills are not invoked from here. The user runs them one at a time, reports back, and you check off the list.

For each sub-skill, pass these as inputs:

- **Taxonomy** (chosen in Q3)
- **Scope** (work / personal — defined in Q2)
- **Aggressiveness** (Q4)
- **Mode** (first-time vs maintenance — Q5)

The sub-skill's Step 1 will re-confirm with the user; that's fine — overlap is intentional safety.

---

## What this skill does NOT do

- Does not maintain global state across sub-skill runs. Each run is self-contained.
- Does not enforce a specific taxonomy. The user's choice in Q3 propagates as a recommendation; sub-skills may diverge if the surface demands it (e.g. Gmail labels can be more granular than Notes folders).

## Edge cases

- **User picks "all surfaces" but most aren't ready:** scan each surface for connectivity (does the MCP / CLI / OAuth work?) before recommending. Mark unavailable surfaces "blocked — needs setup" with the specific fix.
- **User has both personal and work accounts:** sub-skills generally support an account selector. Recommend running the surface twice — once per account — for those that span (Gmail, Drive, Calendar, GitHub).
- **User wants a custom taxonomy not on the menu:** accept any flat lowercase list. Pass it through to sub-skills as-is.

---

## See also

- [`../organizer/README.md`](../organizer/README.md) — full catalog of sub-skills
- [`../organizer/DESIGN.md`](../organizer/DESIGN.md) — architecture decisions
- [`../_lib/taxonomy.md`](_lib/taxonomy.md) — shared default taxonomy
- [`../_lib/patterns.md`](_lib/patterns.md) — implementation patterns reused across sub-skills