ワンクリックで
opencode-result-handling
How Claude should process and present OpenCode worker results — validate, synthesize, present. Token-efficient.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
How Claude should process and present OpenCode worker results — validate, synthesize, present. Token-efficient.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Delegate one or more tasks to OpenCode workers (Haiku subagents). Single worker for focused tasks, multiple workers in parallel for complex ones. No tmux required.
How to compose effective prompts for OpenCode workers. Include context inline, be specific, set output format.
Spawn a Haiku worker to run a task via OpenCode. The worker calls oc-run.sh which executes opencode run headlessly. No tmux, no server, no custom UI.
SOC 職業分類に基づく
| name | opencode-result-handling |
| description | How Claude should process and present OpenCode worker results — validate, synthesize, present. Token-efficient. |
| user-invocable | false |
Workers return results via SendMessage. Claude validates and presents them — never regenerates from scratch.
Workers do the heavy analysis. Claude validates and synthesizes, spending ~200 tokens max on commentary. This is where the token savings compound.
If all 4 pass → present with a one-line "✓ validated" note and stop.
If issues found → add a brief "Claude notes:" section at the end, flag what's wrong.
(fallback: X, primary Y unavailable)Don't:
STOP after presenting. Do not auto-fix. Ask:
"Which of these issues would you like me to fix?"
Wait for the user to choose before touching any files.
Spend at most ~200 tokens on validation. If the worker's output is solid, just say so in one line.