New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Research Decision Room

by nexu-io in nexu-io/open-design

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…

Apache-2.0Auto-check passedFrontend & Design

Install Research Decision Room

skills CLI
$ npx skills add nexu-io/open-design --skill research-decision-room -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nexu-io/open-design research-decision-room --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nexu-io/open-design.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/research-decision-room .claude/skills/research-decision-room && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
research-decision-room
GitHub stars
100k
Token cost
~1.6k tokens
SKILL.md length
637 words
Files
4 (incl. references)
Skills in repo
245
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Works in 7 steps: Establish the decision frame → Build the evidence ledger → Synthesize themes and tensions → …
  • Teams need to move from qualitative signals to product
  • SKILL.md covers Resource map, When to use this skill and Workflow
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Research Decision Room is an agent skill from nexu-io/open-design. 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.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/checklist.md` and `references/evidence-model.md`).

It sits in Frontend & Design, covering HTML artifacts, Customer support and Architecture decision records. The repository describes itself as: 🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes… The licence is Apache-2.0.

When your agent uses it

  • Teams need to move from qualitative signals to product
  • Design decisions without fabricating certainty

Example prompts

  • “/research-decision-room”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Establish the decision frame
  2. Build the evidence ledger
  3. Synthesize themes and tensions
  4. Score opportunities
  5. Draft the decision memo
  6. Create the HTML artifact
  7. Self-check and emit

What it can do on your machine

Read from SKILL.md and the folder at commit 17e2559. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are xml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Research Decision Room loads about 1.6k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 637 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nexu-io/open-design at commit 17e2559, republished under its Apache-2.0 licence (© nexu-io). 637 words, ~1,564 tokens.

Download SKILL.mdSave it as .claude/skills/research-decision-room/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
research-decision-room
description
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.
triggers
research decision room, user research synthesis, research synthesis dashboard, evidence-backed product decision, interview synthesis, opportunity solution…
od.mode
prototype
od.platform
desktop
od.scenario
research
od.example_prompt
Synthesize 8 interview notes, 24 support tickets, and recent activation metrics into a research decision room for whether a project-management app should add…
od.capabilities_required
file_write

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 - Establish the decision frame

Identify the decision scope from the user's prompt. If the user did not give a decision, derive one from the evidence and label it as inferred.

Write a short frame with:

  • Decision question.
  • Audience or segment.
  • Time horizon.
  • Known constraints.
  • What this artifact will not decide.

If key context is missing and the task is not blocked, proceed with labelled assumptions instead of asking a broad question.

Step 2 - Build the evidence ledger

Normalize every useful signal into ledger rows using the model in references/evidence-model.md.

Each ledger row must include:

  • id: short stable id, such as I-03, T-14, M-02.
  • source_type: interview, usability, support, survey, analytics, sales, field note, or stakeholder.
  • segment: user type or "unknown".
  • signal: one-sentence observation.
  • quote_or_metric: direct quote, metric, or "not provided".
  • strength: strong, medium, or weak.
  • limitations: why this evidence may be biased or incomplete.

Never invent quotes, participant counts, dates, revenue impact, or metrics. If the user did not provide a number, use "not provided" and explain what evidence would increase confidence.

Step 3 - Synthesize themes and tensions

Cluster evidence into 4 to 6 themes. For each theme:

  • Name the theme in plain human language.
  • List the evidence ids that support it.
  • Explain the behavior behind it, not just the UI complaint.
  • Mark confidence as high, medium, or low.
  • Note contradictions or segment differences.

Prefer verbs over nouns: "Teams abandon setup when the first blank state asks for too much" is better than "Onboarding problem".

Show full SKILL.md (236 more words)Show less
Step 4 - Score opportunities

Create an opportunity matrix with 3 to 5 options. Score each option on a 1 to 5 scale:

  • Evidence strength.
  • User pain.
  • Business leverage.
  • Implementation risk, where 5 means low risk and 1 means high risk.

Show the total score, but do not let the score replace judgment. Add one sentence on why the top recommendation wins.

Step 5 - Draft the decision memo

Write a decision memo with:

  1. Recommended move.
  2. Why now.
  3. What evidence supports it.
  4. What could be wrong.
  5. What to measure next.
  6. Reversible next step.

Keep the memo short enough to read in under one minute.

Step 6 - Create the HTML artifact

Produce a self-contained index.html. Use the active DESIGN.md for typography, spacing, color roles, and component tone, but keep the information architecture stable:

  1. Header with decision question, confidence, and last-updated label.
  2. Executive readout with recommendation, risk, and next experiment.
  3. Evidence ledger with filter chips.
  4. Theme map with evidence ids and confidence.
  5. Opportunity matrix.
  6. Decision memo.
  7. Experiment queue with owner, metric, and success threshold.
  8. Assumptions and limitations.

The artifact should be interactive but durable. Simple vanilla JavaScript is allowed for filtering evidence, switching views, or highlighting related ids. No framework dependency is required.

Step 7 - Self-check and emit

Run the checklist. Then emit one concise orientation sentence and one HTML artifact:

xml
<artifact identifier="research-decision-room" type="text/html" title="Research Decision Room">
<!doctype html>
<html>...</html>
</artifact>

Nothing after the closing </artifact>.

© nexu-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/research-decision-room of nexu-io/open-design.

  • SKILL.md
  • example.html
  • references/checklist.md
  • references/evidence-model.md

Open the folder on GitHubat commit 17e2559

Compare with similar skills

Research Decision Room next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Research Decision Room compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Research Decision Room this skillnexu-io/open-design100k—~1.6kAutomated safety check: PassApache-2.0
Nova Act UsabilityLeoYeAI/openclaw-master-skills2.2k—~7.4kAutomated safety check: PassMIT
Pm Synthesize Researchevolution-foundation/evo-nexus545—~4.3kAutomated safety check: PassCustom licence
LobeHub Interactive Prototypelobehub/lobehub83k—~1.6kAutomated safety check: PassCustom licence
Paperclip Pagepaperclipai/paperclip100k—~1kAutomated safety check: PassMIT
Openkb Deck NeonVectifyAI/OpenKB4.8k1 repos~4.3kAutomated safety check: PassApache-2.0

Similar skills

  • Nova Act Usability

    LeoYeAI/openclaw-master-skills

    AI-orchestrated usability testing using Amazon Nova Act. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~7.4k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed

  • Pm Synthesize Research

    evolution-foundation/evo-nexus

    Synthesize user research from interviews, surveys, and feedback into structured insights.

    545 GitHub stars~4.3k tokensUpdated 5 mo ago
    Product & Project ManagementAuto-check passed

  • LobeHub Interactive Prototype

    lobehub/lobehub

    Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.

    83k GitHub stars~1.6k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Paperclip Page

    paperclipai/paperclip

    Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.

    100k GitHub stars~1k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Openkb Deck Neon

    VectifyAI/OpenKB

    A skill your agent uses when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content AND wants a dark, high-tech, neon / glow /…

    4.8k GitHub starsUsed in 1 repo~4.3k tokens
    Frontend & DesignAuto-check passed

  • Webhome Homepage Builder

    webhtv/webhtv

    Build, review, debug, reverse-engineer data sources for, and package FongMi/WebHome custom homepage single-file HTML.

    1.7k GitHub stars~3.8k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

More from nexu-io/open-design

All 245 skills in this repo

  • Humanize PPT

    nexu-io/open-design

    Turns raw notes into a talk-ready slide outline with per-page image, diagram or video decisions, then checks the rendered deck against that outline.

    100k GitHub stars~4k tokensUpdated yesterday
    Auto-check passed

  • Last 30 Days Trend Research

    nexu-io/open-design

    Produces a cited Markdown briefing on recent community sentiment and social reaction to a topic, labeling every source it could not actually check.

    100k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • OpenDesign Contribution Flow

    nexu-io/open-design

    Helps newcomers contribute to OpenDesign: ship a skill or design system, translate docs, fix docs or report a bug, ending in a pull request or issue.

    100k GitHub stars~3.5k tokensUpdated yesterday
    Auto-check: notes

  • Chat Motion Overlay Generator

    nexu-io/open-design

    Turns a chat transcript or screenshot into a configurable animated chat clip, rendered as a Remotion bundle with optional transparency.

    100k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Flowai Live Dashboard Template

    nexu-io/open-design

    Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity…

    100k GitHub stars~865 tokensUpdated yesterday
    Auto-check passed

  • Hatch Pet

    nexu-io/open-design

    Create, repair, validate, preview, and package Codex-compatible animated pet spritesheets from character art, screenshots, generated images, or visual references.

    100k GitHub stars~6k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Research Decision Room

What does Research Decision Room 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…. Research Decision Room is an agent skill from nexu-io/open-design. 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.

When should I use Research Decision Room?

Research Decision Room fits situations like: teams need to move from qualitative signals to product; design decisions without fabricating certainty.

How do I install Research Decision Room in Claude Code?

Run `npx skills add nexu-io/open-design --skill research-decision-room -a claude-code`. Or copy the skill folder (skills/research-decision-room in nexu-io/open-design) into .claude/skills/research-decision-room in your project. Claude Code loads it when a task matches its description.

How do I install Research Decision Room in Codex?

Run `npx skills add nexu-io/open-design --skill research-decision-room -a codex`. Or copy the skill folder (skills/research-decision-room in nexu-io/open-design) into .agents/skills/research-decision-room in your project. Codex loads it when a task matches its description.

Can I use Research Decision Room in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nexu-io/open-design --skill research-decision-room -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/research-decision-room, .gemini/skills/research-decision-room, .github/skills/research-decision-room and .opencode/skills/research-decision-room in your project.

What does Research Decision Room need to run?

SKILL.md names no scripts, command-line tools or credentials: Research Decision Room is instructions for the agent only.

Does Research Decision Room access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Research Decision Room safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Research Decision Room use?

Research Decision Room is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Research Decision Room use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Research Decision Room?

Skills that share tags, products or a category with Research Decision Room: Nova Act Usability (LeoYeAI/openclaw-master-skills, 2.2k stars), Pm Synthesize Research (evolution-foundation/evo-nexus, 545 stars), LobeHub Interactive Prototype (lobehub/lobehub, 83k stars) and Paperclip Page (paperclipai/paperclip, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Research Decision Room?

nexu-io (a GitHub organization) maintains it in nexu-io/open-design, which has 100,280 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 10, 2026.

Source: nexu-io/open-design on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.