---
name: selge-weekly-digest
description: Generates a plain-text weekly digest of Selge survey activity, formatted for posting to Slack or pasting into a team update. Use when the user wants something to share with their team - not for personal analysis (use selge-review-results for that). Designed to be run on a schedule.
---

# Selge weekly digest

You produce a plain-text digest of the past week's survey activity, formatted so the user can paste it directly into Slack, Discord, or a written team update. No markdown headers, no emoji, no bold - just clean prose and a few dashes.

If the user wants the data for themselves, send them to `selge-review-results` instead - this skill is for outbound communication.

## Workflow

1. Call `list_surveys` with `status: "active"`.
2. For each survey with at least 1 response in the last 7 days, call `get_results` with `period: "last-7d"`.
3. Compute totals (account-wide response count).
4. Format the digest per the template below.

Run the `get_results` calls in parallel.

## Output format (the contract)

Use this structure exactly. Adjust the numbers and findings - don't restructure.

```
Selge weekly digest - <Mon DD>-<Mon DD>

<one-sentence headline - the most interesting thing this week>

Activity
- <n> total responses across <n> active surveys
- <n> new responses vs <n> the prior week (<up/down/flat>)
- <top survey by responses>: <n>

Top findings
- <survey name>: <one-line finding from the data>
- <survey name>: <one-line finding>
- <survey name>: <one-line finding>

(Cap at 3. If fewer than 3 surveys had meaningful activity, only list those.)

Quotes worth reading
- "<verbatim visitor quote>" - <survey name>
- "<verbatim visitor quote>" - <survey name>

(One or two short quotes. Skip the section entirely if nothing notable.)

Next: <single concrete suggestion, optional>
```

## Style rules

- **No markdown headers** (no `#`, no `##`). Plain section labels followed by a blank line.
- **No bold or italics** - Slack renders some markdown, plain text channels don't. Keep it portable.
- **No emoji.**
- **Use single dashes** for bullets, not asterisks.
- **Round all percentages** to whole numbers.
- **One blank line** between sections.
- **Under 200 words** for the whole digest. If you're approaching the limit, cut the "Quotes" section first, then trim findings.

## Tone

Calm. Factual. The kind of update an experienced PM would write at 9 AM Monday with their first coffee. Not a hype reel.

Good: "Plan confusion is up 7 points on the pricing exit survey."
Bad: "Huge week for Selge data!! 🚀 We saw plan confusion shoot up!!"

## Don'ts

- Don't include survey IDs.
- Don't include response counts under 5 (statistical noise).
- Don't suggest the team "discuss this in the next meeting" - if there's an action, name it. If there isn't, leave it off.
- Don't fabricate quotes. If there are no open-text answers worth quoting, skip the section.