メニュー
Internal Oz child-agent orchestration playbook for Claude Code child runs. Invoke only when the Oz harness system prompt tells you to coordinate with a lead run through the Oz CLI in `OZ_CLI`, using `OZ_RUN_ID` and `OZ_PARENT_RUN_ID`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | oz-child-agent-orchestration |
| description | Internal Oz child-agent orchestration playbook for Claude Code child runs. Invoke only when the Oz harness system prompt tells you to coordinate with a lead run through the Oz CLI in `OZ_CLI`, using `OZ_RUN_ID` and `OZ_PARENT_RUN_ID`. |
| disable-model-invocation | false |
| user-invocable | false |
Use this skill when you are a spawned child agent running inside Claude Code in an Oz cloud agent environment.
You are a team agent started by another agent.
Your agent ID: the value of OZ_RUN_ID
Your parent agent ID: the value of OZ_PARENT_RUN_ID
Lead agent ID (the agent that started you): the value of OZ_PARENT_RUN_ID
Your Oz CLI command: the value of OZ_CLI
Coordinate progress and status through the lead agent. If you complete your task, provide a short summary and any validation steps for the lead agent to run.
OZ_PARENT_RUN_ID.OZ_RUN_ID, OZ_PARENT_RUN_ID, or OZ_CLI is missing from your environment, treat that as a blocker. Do not guess one; wait for corrected context before attempting to message the parent.IMPORTANT: You MUST use "$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>" to keep the lead agent informed. Do not silently complete your work.
IMPORTANT: Sending a message is not a terminal action. After every "$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>", you MUST check your inbox before deciding whether to continue, wait, or stop.
Send a message to the lead agent's ID in OZ_PARENT_RUN_ID at each of these milestones:
You have access to messaging commands for communicating with other agents:
"$OZ_CLI" run message send --sender-run-id \"$OZ_RUN_ID\" --to \"$OZ_PARENT_RUN_ID\" --subject \"<subject>\" --body \"<body>\": Send a message to one or more agents by their run IDs. Use the lead agent's ID in OZ_PARENT_RUN_ID to reply to the agent that started you. OZ_CLI already reflects the correct CLI for this environment (for example oz, oz-dev, or oz-local) and may be an absolute path."$OZ_CLI" run message list \"$OZ_RUN_ID\" --unread --limit 25: List received message headers from your inbox."$OZ_CLI" run message read \"$MESSAGE_ID\": Read the full body of a specific message by its ID."$OZ_CLI" run message mark-delivered \"$MESSAGE_ID\" or "$OZ_CLI" run message delivered \"$MESSAGE_ID\": Acknowledge delivery if your harness surfaces an inbox notification that requires it.
Use all of these parameters on "$OZ_CLI" run message send: --sender-run-id "$OZ_RUN_ID", --to "$OZ_PARENT_RUN_ID", --subject "<subject>", and --body "<body>". If OZ_RUN_ID, OZ_PARENT_RUN_ID, or OZ_CLI is missing, that is a blocker.Do not assume your harness will surface parent messages automatically. Use this workflow whenever you coordinate with the parent:
"$OZ_CLI" run message send --sender-run-id "$OZ_RUN_ID" --to "$OZ_PARENT_RUN_ID" --subject "<subject>" --body "<body>"."$OZ_CLI" run message list "$OZ_RUN_ID" --unread --limit 25."$OZ_CLI" run message read "$MESSAGE_ID" to fetch the full body of the ones you need, then continue from the latest parent instructions.Poll your inbox at these times even if you have not just sent a message:
If you are waiting on the parent, periodically poll for unread messages yourself instead of assuming the harness will wake you automatically. Use a modest cadence rather than a tight loop — for example, wait a short interval between checks, then run "$OZ_CLI" run message list "$OZ_RUN_ID" --unread --limit 25 again. Once a reply arrives, read it and resume work.
Never say you are standing by until a post-send or pre-idle inbox check has shown no unread parent messages that require action.
Report task completion or failure back to the Oz platform when done with a task.
Send a progress notification to the user who triggered this Oz task (e.g., via Slack or Linear).
Report a pull request back to the Oz platform after creating one.
Upload a local file to the Oz platform as a conversation artifact.