← ClaudeAtlas

things-orientlisted

Lazy-load current Things 3 board state. Invoke before creating/updating tasks (for dedup) or when the user asks "what should I work on?" / "what's on my plate?". NOT for session start — use a lighter tripwire/hook for that if your setup has one. This is the heavier read (full items), meant to be called deliberately rather than on every turn.
stanleytejakusuma/things-orient · ★ 0 · AI & Automation · score 60
Install: claude install-skill stanleytejakusuma/things-orient
# things-orient — Lazy board read ## When to invoke - User asks: "what's on my plate?" / "what should I work on?" / "show me my tasks" - You're about to `add_todo` — dedupe first by searching existing open items - You're about to `update_todo` — confirm the target still exists and has expected state - Conversation shifts from brainstorming → planning active work ## Do NOT invoke - On session start, if a lighter hook already surfaces counts there — this is the heavier read, not the cheap one - When you don't need titles, just counts you already have - Repeatedly within one session — cache the read mentally ## Protocol 1. Call `mcp__things3__get_inbox` and `mcp__things3__get_projects` with `include_items: true` in parallel. 2. Synthesize for the user in this shape: ``` 📥 Inbox (N) - [TAG] Task title - ... 💡 Ideas (K) — Project A · Project B · ... 📥 Backlog (J) - [TAG] Task title 🧭 Next (M) - [TAG] Task title 🛠️ In Progress (P/3) - [TAG] Task title 🧱 Waiting (W) - [TAG] Task title — waiting on: ... ``` 3. Don't dump Logbook unless asked. 4. Never auto-propose changes from this read alone — it's observation, not mutation. Pair it with a separate sync/write skill for mutations. ## When used for dedup before `add_todo` Instead of the full render above, call `mcp__things3__search_todos` with the proposed title as query. If ≥80% token overlap with an open task, report the match and propose UPDATE instead of ADD.