---
name: showpilot-answer-the-gaps
description: Turn what visitors asked and the ShowPilot agent could not answer into knowledge the agent can use. Use when someone asks what people are confused about, why the agent keeps escalating, or wants to improve its answers.
---

# Answer the gaps

The agent writes down every question it could not answer. This turns that list into knowledge.

## Steps

1. `whoami`. Confirm the workspace.
2. `find_knowledge_gaps` with `status: "open"` and a `limit` of 100. Add `from` to look at one period.
3. Cluster the questions yourself. They arrive unclustered on purpose. Use the wording, not `normalized` — that field only collapses exact repeats.
4. For each cluster, decide which of three things it is:
   - **We know the answer, it is just not written down.** The fix is knowledge.
   - **We know the answer and it is written down badly.** The fix is a better source.
   - **We do not know the answer.** The fix is a person, not a document. Say so and stop.
5. For the first two, draft the answer and show it. Ask before writing anything.
6. On approval, add it with `execute create_knowledge_source`, then `execute refresh_knowledge_base` so the agent can use it.

## Rules

- Never invent an answer. If the cluster is about something you cannot verify from the workspace's own content, say it needs a human and move on. A confident wrong answer in the knowledge base is worse than the gap.
- Show the draft before writing. Knowledge changes what the agent tells real visitors.
- One source per cluster, not one per question. Ten phrasings of "do you support SSO" need one good answer.
- `reason` says why the agent stalled. A guardrail is a different problem from missing knowledge, and adding a document will not fix it.
- A question already `answered` by a person is the best raw material there is — that answer was approved by someone who knew.