Agent-generated summaries
Agent-generated summaries audience
Agent-generated summaries are for people who want the point without opening every panel.
They are also useful for the user. A good summary makes it easier to decide what to do next.
Report contents
The summary should stay close to the dashboard evidence.
Ask CLEA to include what changed, why it matters, and what should happen next. It should also say when data is missing.
Generation timing
Schedule summaries after the related data exists.
For example, a summary should run after visibility prompts, not before them. A launch summary should run after the new page has had time to be checked by prompts.
Run after data
Schedule summaries after the related prompt or check.
Ask for evidence
Require the summary to name what changed.
Keep it short
Make the output easy to review.
Share after review
Read it before sending it outside the workspace.
Review before sharing
Read the summary before sharing it.
If it is too broad, make the prompt smaller. If it is too short, ask CLEA to include the evidence. If it guesses, tell it to keep missing data visible.
Summarize the latest Analytics and Calendar work. Show what ran, what changed, and what needs action. Do not guess missing Search Console or Google Analytics data.