executive-summarylisted

Distills a question/topic from quantitative survey data (CSV) for leadership: a one-pager with a TL;DR, 3–5 key findings each with a number and an implication, and next steps. Result as Markdown to reports/. Use when results need to be condensed for an executive / stakeholder audience. Invoke with your request as the argument, e.g. /executive-summary <question/topic>.
kayspiegel/survey-insight-skills · ★ 2 · Data & Documents · score 76

Install: claude install-skill kayspiegel/survey-insight-skills

# Executive Summary Goal: For the **topic** named in the user's request, produce a **decision-oriented one-pager** for leadership/stakeholders — condensed, implication-led, without methodological ballast. Result as Markdown in `reports/`. ## Tool ``` python3 scripts/survey.py <cmd> [...] [--file CSV] ``` Run these from the project root. If `scripts/survey.py` is not there, check `.claude/scripts/survey.py` or locate `survey.py` in the project. - `profile` — column overview (always first). - `freq COL [--by COL2] [--filter "COL=VALUE"] [--sig]` — distribution/cross-tab (+significance). - `text COL [--filter ...] [--sample N]` — free text for one crisp verbatim quote. `COL` = index (from `profile`) or an unambiguous name part. ## Survey context If a context document sits next to the CSV (`<name>.context.md`, or `survey-context.md` when the folder holds exactly one CSV), read it first. Two parts of it matter most here: the **audience** (who reads this and what they decide with it — pitch the one-pager at them) and the **subject/glossary** (so the summary uses the reader's own words, not the column wordings). Figures still come only from the engine. This format has no method section, which makes it the easiest place to lose the study design — so keep one thing: if the recruiting route materially qualifies the message (the **"Who is missing"** section), say so in **half a sentence** where it belongs, not in a separate block. "Among active users surveyed via the app, 71% …"