← ClaudeAtlas

inbox-ledgerlisted

Keep one JSONL ledger of inbound messages across channels so an unattended agent never answers the same message twice or forgets one. Dedupes, tracks done, and lists messages past a reply SLA. Use in any shift that reads DMs, comments or email.
Tommyapi/ai-employee-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill Tommyapi/ai-employee-skills
# Inbox ledger Each shift re-reads the same inbox. Without a ledger the agent either replies twice or loses track. The ledger is the single source of truth for "has this been handled". ## Steps 1. On every read, add what you see (safe to repeat; identical messages are stored once, case and spacing ignored): `python scripts/inbox_ledger.py --ledger inbox.jsonl add --channel dm --sender alice --text "price?"` Output is `added <id>` or `duplicate <id>`. Only act on `added`. 2. Work the queue: `... open` lists unanswered messages. 3. After replying AND reading the reply back on the platform: `... done <id> --note "sent pricing page"`. 4. Each shift start: `... overdue --sla-hours 4` and handle those first. ## Rules - "Done" means the reply is verified sent, not that a draft exists. - Same text from the same sender on a different channel counts as new. - The ledger is plain JSONL: grep it, diff it, back it up. - Keep personal data out of the repo; the ledger belongs in your private workspace.