← ClaudeAtlas

messages-historylisted

Browse VantagePeers peer-message history with day/sender filters, envelope-safe defaults, broadcast read-receipt audits, and safe mark-as-read / delete operations, so orchestrators can audit conversations without the unread-inbox tunnel vision of check-messages. Use this skill whenever the user says "messages history", "show past messages", "messages from <peer>", "messages on day N", "broadcast status", "who read the broadcast", "mark messages read", "delete a message" -- even if they don't say "messages-history" explicitly.
vantageos-agency/vantage-peers · ★ 2 · AI & Automation · score 64
Install: claude install-skill vantageos-agency/vantage-peers
Browse and audit VantagePeers peer-message history — past DMs and broadcasts across the fleet — with day/sender filters, envelope-safe defaults, broadcast read-receipt audits, and safe mark-as-read / delete operations scoped to the sender. **Canonical source**: VantageRegistry (`get_skill_content name=messages-history`). The local `.claude/skills/messages-history/SKILL.md` in each workspace MUST be a byte-exact mirror of the VR canonical content. End of hand-copy — fetch from VR, do not edit locally. PRINCIPLE — `check-messages` shows the live unread inbox; `messages-history` shows the ledger. History reads are envelope-aware (capped limit + sessionDay/from filters), provenance-preserving (always surface `messageId`, `from`, `to`, `sessionDay`, `readAt`), and write-cautious (delete is sender-only and irreversible — broadcast deletions cascade to all receipts). ## WORKFLOW **Step 1 — Detect orchestrator identity** Read the first 20 lines of `CLAUDE.md` to determine your role and instanceId. Identity is used to (a) bias relevance (messages from/to you are highlighted), (b) gate `delete_message` (sender-only) on the client side before the server rejects, and (c) compute the default `sessionDay` window. **Step 2 — Resolve mode** - User said "show messages on day N", "history day N", "DMs from <peer>", "messages between days" → LIST mode → Step 3. - User said "who read the broadcast <messageId>", "broadcast status <id>" → BROADCAST-STATUS mode → Step 6. - User said "mark <r