OKX Task Watch

Live monitor for the user-session task inbox. Owns: triggers, the watch command, anti-cron rules, item dispatch (notification / decision_request), claim semantics, llmContent execution, stop conditions.

Business actions (apply / deliver / dispute / quote / accept) belong to okx-agent-task. This skill only handles the watch loop.

Triggers — MANDATORY ROUTING (NOT cron / scheduled / polling)

When ANY trigger phrase below matches, execute §Action. The watch command is a single long-poll call (the call itself waits for events); do NOT wrap in /loop, Cron, $CODEX_HOME/automations, watch -n, sleep loops, scheduler frameworks, or "set up a recurring job". Do NOT ask "how often should I check?" — the long-poll IS the wait. Do NOT substitute another command for polling.

Trigger phrases:

• Chinese (live monitor): 监听任务进展 / 开始监听任务 / 关注任务进展 / 使用监听 skill 监听任务进展 / 帮我盯着任务 / 任务有进度就告诉我 / 任务有动静告诉我 / 开监听 / watch 任务
• Chinese (history / backlog drain): 历史消息 / 历史记录 / 过去消息 / 之前的消息 / 帮我看看之前的历史消息 / 看下之前的消息 / 未读消息
• Chinese (continuation — clarify first, see §Continuation triggers): 继续监听 / 继续盯着 / 继续 watch / 接着监听 / 再监听一下 / 继续监听任务
• English (live monitor): task watch / user watch / monitor task progress / keep me posted on tasks / watch tasks / start watching
• English (history / backlog drain): show past messages / show message history / catch me up on tasks / unread task messages
• English (continuation — clarify first, see §Continuation triggers): keep watching / continue watching / resume monitoring

⚠️ Continuation triggers are a special case — they do NOT immediately call watch. They imply the user wants to keep watching some specific task, but the intent is ambiguous (which task? or all of them?). See §Continuation triggers below for the clarification flow.