ops-inbox

What it does

The skill performs full-channel inbox management across multiple messaging platforms. It scans entire inboxes (not just unread), identifies conversations requiring replies, and archives handled conversations. It combines channel-aware scanning, context gathering, and draft-based reply capability to support agents in replying with full-thread context and tailored messaging.

How it works

• It loads runtime context and preferences before acting, including channel defaults and daemon health.
• It supports a broad set of tools (Bash, Read, Grep, Glob, Skill, Agent, and many channel-specific tools). It can run either in parallel via Agent Teams or sequentially depending on configuration.
• For each channel, it conducts a FULL scan: Email via gog gmail search in:inbox, WhatsApp via wacli chats list and wacli messages list for full threads, Slack via MCP tools, Telegram via user-auth MCP. (Notion/Discord/Notion specifics are listed in the toolset and environment.)
• It classifies conversations by the last message sender (NEEDS REPLY if contact sent last, WAITING if user sent last, ARCHIVE if no recent activity or closed).
• For NEEDS REPLY items, it builds a full-context draft by aggregating the entire thread (up to 20 messages for WhatsApp), cross-channel contact history, topic context, and any stored memories, then presents a draft with options to Send/Edit/Read/Skip. Drafts reference the full thread and channel-specific context.
• It presents a batched AskUserQuestion flow with up to four channel options per prompt, guiding the user to select which channels to address.
• The runtime includes safety rules: never draft or send without understanding the full conversation (summarize arc, identify participants, last user message intent).

When to use it

• Use when you need to manage a multi-channel inbox and determine which conversations require a reply.
• Use when you want to prioritize cross-channel NEEDS REPLY items and draft replies in full context.
• Use when you want to archive completed conversations and keep an organized inbox state.

What it can touch

• Email: gog gmail search, gog gmail thread get, gog gmail get, gog gmail archive, gog gmail send, gog gmail labels.
• WhatsApp: wacli chats list, wacli messages list.
• Slack: Slack MCP tools (prefixed as per configuration).
• Telegram: user-auth MCP tools.
• Notion: MCP tools for search and updates.
• Notation for channel availability and credentials is read from environment variables and preference files.

Caveats

• Requires various channel configurations and credentials to be present (e.g., Slack MCP, Telegram user-auth MCP, Notion MCP, Gmail access).
• Behavior depends on availability and health of external daemons (e.g., wacli) and proper token/config setup.
• Architecture relies on multiple external CLI tools; failures in any tool may impact scan results.
• License: MIT