Create skills page, update commands, refine docs (#17842)

docs/core/subagents.md

@@ -24,30 +24,29 @@ the main agent's context or toolset.
 
 ## What are sub-agents?
 
-Think of sub-agents as "specialists" that the main Gemini agent can hire for a
-specific job.
+Sub-agents are "specialists" that the main Gemini agent can hire for a specific
+job.
 
 - **Focused context:** Each sub-agent has its own system prompt and persona.
 - **Specialized tools:** Sub-agents can have a restricted or specialized set of
   tools.
 - **Independent context window:** Interactions with a sub-agent happen in a
-  separate context loop. The main agent only sees the final result, saving
-  tokens in your main conversation history.
+  separate context loop, which saves tokens in your main conversation history.
 
-Sub-agents are exposed to the main agent as a tool of the same name which
-delegates to the sub-agent, when called. Once the sub-agent completes its task
-(or fails), it reports back to the main agent with its findings (usually as a
-text summary or structured report returned by the tool).
+Sub-agents are exposed to the main agent as a tool of the same name. When the
+main agent calls the tool, it delegates the task to the sub-agent. Once the
+sub-agent completes its task, it reports back to the main agent with its
+findings.
 
 ## Built-in sub-agents
 
-Gemini CLI comes with powerful built-in sub-agents.
+Gemini CLI comes with the following built-in sub-agents:
 
 ### Codebase Investigator
 
 - **Name:** `codebase_investigator`
-- **Purpose:** Deep analysis of the codebase, reverse engineering, and
-  understanding complex dependencies.
+- **Purpose:** Analyze the codebase, reverse engineer, and understand complex
+  dependencies.
 - **When to use:** "How does the authentication system work?", "Map out the
   dependencies of the `AgentRegistry` class."
 - **Configuration:** Enabled by default. You can configure it in
@@ -67,20 +66,25 @@ Gemini CLI comes with powerful built-in sub-agents.
 ### CLI Help Agent
 
 - **Name:** `cli_help`
-- **Purpose:** Expert knowledge about Gemini CLI itself, its commands,
+- **Purpose:** Get expert knowledge about Gemini CLI itself, its commands,
   configuration, and documentation.
 - **When to use:** "How do I configure a proxy?", "What does the `/rewind`
   command do?"
 - **Configuration:** Enabled by default.
 
+### Generalist Agent
+
+- **Name:** `generalist_agent`
+- **Purpose:** Route tasks to the appropriate specialized sub-agent.
+- **When to use:** Implicitly used by the main agent for routing. Not directly
+  invoked by the user.
+- **Configuration:** Enabled by default. No specific configuration options.
+
 ## Creating custom sub-agents
 
 You can create your own sub-agents to automate specific workflows or enforce
-specific personas.
-
-### Prerequisites
-
-To use custom sub-agents, you must enable them in your `settings.json`:
+specific personas. To use custom sub-agents, you must enable them in your
+`settings.json`:
 
 ```json
 {
@@ -123,10 +127,10 @@ vulnerabilities.
 
 Focus on:
 
-1. SQL Injection
-2. XSS (Cross-Site Scripting)
-3. Hardcoded credentials
-4. Unsafe file operations
+1.  SQL Injection
+2.  XSS (Cross-Site Scripting)
+3.  Hardcoded credentials
+4.  Unsafe file operations
 
 When you find a vulnerability, explain it clearly and suggest a fix. Do not fix
 it yourself; just report it.
@@ -147,17 +151,16 @@ it yourself; just report it.
 
 ### Optimizing your sub-agent
 
-The main agent system prompt contains language that encourages use of an expert
-sub-agent when one is available for the task at hand. It decides whether an
-agent is a relevant expert based on the agent's description. You can improve the
-reliability with which an agent is used by updating the description to more
-clearly indicate:
+The main agent's system prompt encourages it to use an expert sub-agent when one
+is available. It decides whether an agent is a relevant expert based on the
+agent's description. You can improve the reliability with which an agent is used
+by updating the description to more clearly indicate:
 
 - Its area of expertise.
 - When it should be used.
 - Some example scenarios.
 
-For example: the following sub-agent description should be called fairly
+For example, the following sub-agent description should be called fairly
 consistently for Git operations.
 
 > Git expert agent which should be used for all local and remote git operations.
@@ -173,7 +176,7 @@ that your sub-agent was called with a specific prompt and the given description.
 
 ## Remote subagents (Agent2Agent) (experimental)
 
-Gemini CLI can also delegate tasks to remote subagents using the Agent-to-Agent
+Gemini CLI can also delegate tasks to remote sub-agents using the Agent-to-Agent
 (A2A) protocol.
 
 > **Note: Remote subagents are currently an experimental feature.**