ops-commslisted

# OPS ► COMMS ## Runtime Context Before executing, load available context: 1. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/daemon-health.json` - Check bridge liveness before any WhatsApp operation: `lsof -i :8080 | grep LISTEN` - If bridge not running, prompt user to restart: `launchctl kickstart -k gui/$UID/com.${USER}.whatsapp-bridge` 2. **Ops memories**: Before drafting any message, check `${CLAUDE_PLUGIN_DATA_DIR}/memories/`: - `contact_*.md` — load profile for the recipient - `preferences.md` — match user's communication style, language, and tone - `donts.md` — restrictions that must not appear in any draft 3. **Preferences**: Read `${CLAUDE_PLUGIN_DATA_DIR}/preferences.json` for `default_channels` to determine which channel to prefer when multiple are available for a contact. ## CLI/API Reference ### whatsapp-bridge (WhatsApp — mcp__whatsapp__*) **Bridge health** — check bridge is running before any WhatsApp operation: ```bash lsof -i :8080 | grep LISTEN launchctl list com.${USER}.whatsapp-bridge ``` If not running: `launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge` | Tool | Params | Output | |------|--------|--------| | `mcp__whatsapp__list_chats` | `{sort_by: "last_active"}` | Array of chats with jid, name, last_message_time | | `mcp__whatsapp__list_messages` | `{chat_jid, limit, query}` | Array of messages with is_from_me, content, timestamp, sender | | `mcp__whatsapp__search