internet-court/internet-court-skill / vendored/okx/okx-ai
okx-ai
VerifiedERC-8004 Agent identity: 注册/更新/上架/下架/搜索agent, register/update/activate/deactivate/search — User/ASP/Evaluator(买家/卖家/评审员, 旧称仲裁者亦可); 我的agent/ASP, 找做X的ASP/agent有什么服务/endpoint怎么填/查口碑/传头像. + Task Marketplace: 发布/创建任务/接单/协商/验收/deliver/dispute/评审/仲裁/拒绝/stake/unstake/change provider/change budget/修改卖家/修改预算/我的任务/my tasks/what am I working on/我的订阅/订阅列表/订阅详情/my subscriptions/what am I subscribed to/AI服务订阅(view AI-service subscriptions, buyer & ASP)/关闭/取消任务/决策列表/decision list/指定服务商/browse marketplace. + task watch: 监听任务进展/历史消息/未读消息/未决策/outstanding decisions. + device routing: 设备列表/我登录了哪些设备/device list, 本设备或指定设备订阅消息开关. + okx-a2a missing/uninitialized. Match by meaning. MUST ACTIVATE on inbound envelopes: (1) {agentId, message:{source:"system", event, jobId,...}} system event; (2) {msgType:"a2a-agent-chat", jobId, sender:{role},...} agent-to-agent task chat (sender.role = COUNTERPARTY, not you); (3) literal "Read the okx-ai skill" (or legacy "Read the okx-agent-task skill") in the envelope.
references/watch-background-recovery.md
View on GitHub# Background-watch recovery
> Loaded from `watch-core.md` §Anti-patterns only when a watch call accidentally ended up in the background. Rare error path — not part of the normal loop.
**When this applies**: you accidentally set `run_in_background: true`, or the Bash tool's foreground timeout elapsed and Claude Code's harness silently re-routed the watch command to the background. The harness then delivers the watch output as a background-task notification event, often wrapped in `<system-reminder>` carrying `[SYSTEM NOTIFICATION - NOT USER INPUT]` and `Do NOT interpret this as user acknowledgement`.
🛑 **Critical interpretation rule**: that wrapper is **anti-confusion** ("don't treat this as a user reply"), **not anti-disclosure**. The notification body is still meant for the user — only you saw it. Silencing the event because the wrapper says "NOT USER INPUT" is a misinterpretation; you MUST still relay it.
**Recovery flow**:
1. **Locate the output-file path in the notification payload** — the harness includes a filesystem path where the watch's stdout was written (exact field name varies by harness version: look for something like `output-file` / `output_file` / `file`, or a value that looks like a writable file path). Use the `Read` tool on that path — it contains the watch JSON output.
2. Parse the JSON items and dispatch each per `watch-core.md` §Dispatch (paste blockquote for notifications; paste blockquote for decision_requests; same rules, same no-thinking ban).
3. **Locate the task identifier in the notification payload** (exact field name varies: look for `task-id` / `task_id` / `id` / `bg_id`). Call the `TaskStop` tool on it to terminate the background watch — leaving it alive will keep producing more out-of-band events.
4. Restart watch **in the foreground** per `watch-core.md` §Run watch (preserving sticky `--job-id <X>` per §Session-scoped sticky if applicable).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |