원클릭으로
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.