ops-inboxlisted

Full inbox management across all channels — WhatsApp (whatsmeow bridge via mcp__whatsapp__*), iMessage (chat.db reader + AppleScript send via mcp__plugin_imessage_imessage__*), Email (Gmail MCP), Slack (MCP), Telegram (user-auth MCP), Discord (webhook + REST read), Notion (MCP — comments, mentions, assigned tasks). Scans FULL inbox (not just unread), identifies messages needing replies, archives handled conversations.
Lifecycle-Innovations-Limited/claude-ops · ★ 17 · AI & Automation · score 86

Install: claude install-skill Lifecycle-Innovations-Limited/claude-ops

# OPS ► INBOX ZERO ## ⚠️ WHATSAPP TRANSPORT — MCP ONLY, NEVER `wacli` For **all** WhatsApp operations in this skill (list chats, read messages, search contacts, send replies, archive chats), use the `mcp__whatsapp__*` tool family backed by the whatsmeow (Go) whatsapp-bridge — upstream `lharries/whatsapp-mcp`. (Earlier docs misnamed this as "Baileys" — Baileys is the Node.js WhatsApp library; this bridge uses `go.mau.fi/whatsmeow`.) **NEVER call the legacy `wacli` CLI** (`wacli chats list`, `wacli messages list`, `wacli send`, `wacli doctor`, `wacli history backfill`, etc). The wacli store and keepalive daemon are deprecated for this skill. If you find yourself reaching for any `wacli ...` shell command, stop and use the MCP tool with the same intent: | Intent | ✅ Use this | ❌ Do NOT use | |-------------------------|--------------------------------------------------------------------------|---------------------------| | List recent chats | `mcp__whatsapp__list_chats {sort_by: "last_active", limit: 25}` | `wacli chats list` | | Read full thread | `mcp__whatsapp__list_messages {chat_jid, limit: 20}` | `wacli messages list` | | Full-text search | `mcp__whatsapp__list_messages {query: "<text>", limit: 20}` | `wacli messages search` | | Resolve a contact | `mcp__whatsapp__search_contacts {query: "<name>"}`