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

# Use cases

> Prompts to try once your agent is connected, and patterns that work well.

## Weekly check-in

> Give me a Monday summary for acme.com: headline numbers, what moved since last week, the two biggest slips, and the top three actions.

Your agent calls `list_sites`, `get_visibility_summary`, `search_prompts` and `get_actions`, then writes the summary.

## Competitive brief

> Who is beating us on Perplexity and why? Show the prompts, what they said, and which sources they used.

`get_competitors`, `search_prompts`, `get_prompt_detail`, `get_citations`.

## Content planning in your editor

> I have one afternoon. Should I write something new or fix an existing page? Show me the options with effort.

`get_page_revisions` first (cheaper, faster), then `get_content_opportunities`. Follow with `get_revision_detail` for the exact edits.

## Did it work?

> We published the CRM migration guide three weeks ago. Is AI citing it yet?

`get_content_performance`, framed honestly: engines take a few weeks.

## Technical health

> Can AI crawlers read our site? What is blocked and what is missing?

`get_site_health`.

## Agency roll-up

> For every client in the Northbank workspace, list Prompt Visibility Rate and its change, sorted worst first.

`list_workspaces`, `list_sites`, then `get_visibility_summary` per site.

## Patterns that work

* **Ask for the numbers before the narrative.** Agents summarise better when they have quoted the figures first.
* **Name the site.** Agencies with many sites should say which one; the agent will otherwise ask.
* **Let the agent quote freshness.** Every tool carries a Data as of stamp; a good summary repeats it.
* **Do not ask it to change things.** It cannot. Use Kevin in the app for board cards and drafts.