Individual skill
research-readout
Turns synthesized research findings into a crisp stakeholder readout - so-what up front, 3-5 confidence-tagged findings each following the finding-evidence-implication rule, and owned recommendations. Use when someone says "present these research findings", "turn this study into a readout for leadership", "our research isn't landing with the product team", or needs a deck or brief that gets findings acted on. Do NOT use for building a narrative around quantitative metrics and charts - use data-story instead; for the upstream analysis that produces the findings, use interview-synthesis or research-synthesis; for slide craft itself, use slide-deck-builder.
skills/research-readout/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- data Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Research Readout
A readout is not a research report: its job is to transfer the minimum context stakeholders need to make a decision or change direction, then get out of the way. Most research goes unacted on not because it is wrong but because the readout is too long, too hedged, or buries the recommendations at the end - stakeholders decide in the first 60 seconds whether to stay engaged, and a sea of "mights" and "possiblys" reads as noise.
## Inputs to collect
1. The synthesized findings (from interview-synthesis, research-synthesis, or equivalent) - the readout communicates analysis, it does not perform it. If handed raw transcripts, route to synthesis first.
2. The audience and the decision on the table. A readout without a live decision becomes FYI content and dies; if no decision exists, ask what the study was supposed to unlock.
3. Study metadata: goal, method, sample size, and per-finding participant counts (needed for confidence tags).
4. Format constraint. Default by audience: async stakeholders get a deck, one finding per slide, headline in the title bar; live sessions get 20-30 minutes of findings plus 10-15 of discussion; engineering audiences get a one-page brief with a findings table.
## Operating procedure
1. **Write the so-what first.** Open with 2-3 bullets stating the most important findings and their implications for the product or business. This section is drafted first and rewritten last.