tool-description-agent-usage-notes

name	Tool Description: Agent (usage notes)
description	Usage notes and instructions for the Task/Agent tool, including guidance on launching subagents, background execution, resumption, and worktree isolation
ccVersion	2.1.161
variables	["TOOL_BASE_DESCRIPTION","TOOL_PARAMETERS_DESCRIPTION","DESCRIPTION_FORMAT_NOTE","ENVIRONMENT_CONFIG","IS_SUBAGENT_CONTEXT_FN","HAS_SUBAGENT_TYPES","SEND_MESSAGE_TOOL_NAME","AGENT_TOOL_NAME","IS_TEAMMATE_CONTEXT_FN","ADDITIONAL_USAGE_NOTES","EXTRA_USAGE_NOTES","SUBAGENT_TYPE_DEFINITIONS","DEFAULT_AGENT_DESCRIPTION"]
allowed-tools	Read Write Edit Bash
license	BSD-3-Clause license
metadata	{"skill-author":"Lord1Egypt"}

${TOOL_BASE_DESCRIPTION} ${TOOL_PARAMETERS_DESCRIPTION}

Usage notes

• Always include a short description summarizing what the agent will do${DESCRIPTION_FORMAT_NOTE}
• When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.
• Trust but verify: an agent's summary describes what it intended to do, not necessarily what it did. When an agent writes or edits code, check the actual changes before reporting the work as done.${!ENVIRONMENT_CONFIG.CLAUDE_CODE_DISABLE_BACKGROUND_TASKS&&!IS_SUBAGENT_CONTEXT_FN()&&!HAS_SUBAGENT_TYPES?`
• You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, you will be automatically notified when it completes — do NOT sleep, poll, or proactively check on its progress. Continue with other work or respond to the user instead.
• Foreground vs background: Use foreground (default) when you need the agent's results before you can proceed — e.g., research agents whose findings inform your next steps. Use background when you have genuinely independent work to do in parallel.`:""}
• To continue a previously spawned agent, use ${SEND_MESSAGE_TOOL_NAME} with the agent's ID or name as the to field — that resumes it with full context. A new ${AGENT_TOOL_NAME} call${HAS_SUBAGENT_TYPES?" with a subagent_type":""} starts a fresh agent with no memory of prior runs, so the prompt must be self-contained.
• Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.)${HAS_SUBAGENT_TYPES?"":", since it is not aware of the user's intent"}
• If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first.
• If the user specifies that they want you to run agents "in parallel", you MUST send a single message with multiple ${AGENT_TOOL_NAME} tool use content blocks. For example, if you need to launch both a build-validator agent and a test-runner agent in parallel, send a single message with both tool calls.
• With isolation: "worktree", the worktree is automatically cleaned up if the agent makes no changes; otherwise the path and branch are returned in the result.${IS_SUBAGENT_CONTEXT_FN()?`
• The run_in_background, name, team_name, and mode parameters are not available in this context. Only synchronous subagents are supported.:IS_TEAMMATE_CONTEXT_FN()?
• The name, team_name, and mode parameters are not available in this context — teammates cannot spawn other teammates. Omit them to spawn a subagent.`:""}${ADDITIONAL_USAGE_NOTES}${EXTRA_USAGE_NOTES}

${HAS_SUBAGENT_TYPES?SUBAGENT_TYPE_DEFINITIONS:DEFAULT_AGENT_DESCRIPTION}