Agent skill · Design & Presentation

research-decision-room

Turn messy user research notes, interviews, support tickets, surveys, and product context into an evidence-backed decision room: a single HTML artifact with an evidence ledger, theme map, confidence heatmap, opportunity matrix, decision memo, and experiment queue. Use when teams need to move from qualitative signals to product or design decisions without fabricating certainty.

nexu95,528★ · +2,037/wk · 5 repos on radarProfile →
claude-codecodexcursorApache-2.0
Install
npx skills add nexu-io/open-design --skill research-decision-room --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/research-decision-room/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 83,577 · +1,339 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Research Decision Room Skill Create a single-page HTML decision artifact that helps a product or design team turn messy evidence into a clear next move. The output is not a decorative research deck. It is a working room for debate: evidence, themes, confidence, tradeoffs, and recommended experiments stay visible together. ## Resource map ```text research-decision-room/ ├── SKILL.md ├── example.html └── references/ ├── checklist.md └── evidence-model.md ``` Read `references/evidence-model.md` before synthesis and run `references/checklist.md` before emitting the artifact. ## When to use this skill Use this skill when the user has any mix of: - Interview notes, usability-test observations, support tickets, sales call notes, app-store reviews, NPS comments, survey open text, analytics snippets, or product-decision context. - A decision that needs evidence: "Should we build X?", "Which onboarding path should we try?", "Why are users dropping off?", "What do customers actually mean by slow?" - A need to share findings with stakeholders who will not read a long research report. Do not use it for pure visual inspiration, campaign ideation, or brand moodboards. ## Workflow ### Step 1 - E

What's inside
Steps it walks through
  1. Resource map
  2. When to use this skill
  3. Workflow
  4. Step 1 - Establish the decision frame
  5. Step 2 - Build the evidence ledger
  6. Step 3 - Synthesize themes and tensions
  7. Step 4 - Score opportunities
  8. Step 5 - Draft the decision memo
  9. Step 6 - Create the HTML artifact
  10. Step 7 - Self-check and emit
Ships with 3 files
  • example.html
  • references/checklist.md
  • references/evidence-model.md
More from open-design
All skills →
About this skill
What does the research-decision-room skill do?

Turn messy user research notes, interviews, support tickets, surveys, and product context into an evidence-backed decision room: a single HTML artifact with an evidence ledger, theme map, confidence heatmap, opportunity matrix, decision memo, and experiment queue. Use when teams need to move from qualitative signals to product or design decisions without fabricating certainty.

How do I install it?

Run `npx skills add nexu-io/open-design --skill research-decision-room --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going