Ops Go
OPS on-demand: This skill should be used when the user asks to \"morning briefing\"...
Install
npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-go -g -a claude-code -y- Repository
- Lifecycle-Innovations-Limited/claude-ops547
- Category
- Engineering
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
OPS on-demand: This skill should be used when the user asks to \"morning briefing\", \"/ops:ops-go\", or…
OPS ► MORNING BRIEFING
Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).
Runtime Context
Before executing, load available context:
-
Preferences: Read
${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.jsonowner, use in the greeting header ("Good morning, [owner]")timezone, display all timestamps in this timezonedefault_channels, which channels to include in unread summary
-
Daemon health: Read
${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json- If
action_neededis not null → surface it before the briefing - Check
whatsapp-bridgestatus before including WhatsApp unread counts - Also check bridge liveness:
lsof -i :8080 | grep LISTEN
- If
-
WhatsApp pre-check: Only include WhatsApp data if bridge is running (
lsof -i :8080 | grep LISTEN).
CLI/API Reference
whatsapp-bridge (WhatsApp, mcpwhatsapp*)
Bridge health, check before any WhatsApp operation:
- Running:
lsof -i :8080 | grep LISTEN→ proceed - Not running →
launchctl kickstart -k gui/$(id -u)/com.${USER}.whatsapp-bridge, wait 5s
| 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} | Message array with is_from_me, content, timestamp |
