> ## Documentation Index
> Fetch the complete documentation index at: https://slackhive.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Coach

> Tune your agent's instructions, skills, and knowledge through an interactive chat panel.

Coach is an interactive chat panel that helps you refine an agent after it's created. Instead of hand-editing prompts and skill files, you describe what you want in plain English - Coach proposes concrete changes, and you apply or reject each one.

## Open the Coach panel

1. Go to the agent's detail page
2. Click **Coach** in the top-right - the panel slides in from the right
3. The panel stays open across tabs; close it with the × at top-right

## Ask in plain English

Tell Coach what you want the agent to do. Examples:

```
Help me build a weekly metrics router - route questions about
revenue to the data team and product metrics to PM.
```

```
This agent keeps paraphrasing user questions before answering.
Make it lead with the answer, then show the SQL.
```

Coach reads the current system prompt, skills, memories, and knowledge, then streams a reply. It is useful immediately after creating an agent: start with a short description, then ask Coach to build out the system prompt, skills, memory, evaluation cases, and operating rules over time.

## Attach a file

Click the **paperclip icon** in the composer to attach a document. Coach will read it and reference it when drafting proposals — useful for sharing a style guide, a sample conversation log, an API spec, or any context you want Coach to reason from.

```
[attach: slack-log.txt]
The agent gave this response but it's too long. Make it punchier.
```

Supported types: **PDF, Markdown, text, CSV, JSON, YAML, XML, HTML** — up to 20 KB of extracted text per message.

The file is **session-only** — it's not stored. If you want the content available to the agent permanently, add it as a wiki source in the [Knowledge Library](/agents/knowledge-base).

<Tip>
  Attaching a PDF style guide and asking "does this agent match our tone?" is a fast way to audit and tighten instructions in one pass.
</Tip>

## Review proposal cards

Coach's changes arrive as **proposal cards** - one per distinct change. Each card shows:

* **What will change** (system prompt, a skill, or a memory)
* **A diff preview** (green = added, red = removed)
* **Apply** and **Reject** buttons

You can apply some cards and reject others. Nothing changes until you click Apply.

## What Coach can change

| Proposal kind | What it is                                      |
| ------------- | ----------------------------------------------- |
| System prompt | Rewrites the agent's instructions               |
| Skill         | Adds, edits, or removes a skill (slash command) |
| Memory        | Adds, rewrites, or removes a saved fact/rule    |

Every applied change is **snapshotted automatically**, so you can restore via **History** if something goes wrong.

## Wiki access (read-only)

Coach can **read** the agent's assigned wiki folders for context — `list_file_sources` shows what file content is available across the agent's folders, and `read_file_source` returns the verbatim text of one source. This lets Coach audit system prompts or skills against actual reference material.

Coach **cannot** add, edit, or delete wiki sources. Wiki content is shared across many agents and belongs to the folder owner — edits go through the [Knowledge Library](/agents/knowledge-base) so the owner stays in control.

## Looking things up

Coach can browse the web while drafting a proposal - useful when you ask it to pull in an API shape, a canonical reference, or a public doc you mentioned.

## Close mid-stream

If you close the panel while Coach is still streaming, the turn still persists. Reopen the panel later and pick up where you left off - proposals that were mid-flight either landed as pending cards or were discarded cleanly.