research-decision-room
Skill6 starsChanged 6 months agoApache-2.0View on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- davidanthonyn/claude-skillsword for word, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 1
- davidanthonyn/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository169 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apps/AGENTS.mdAGENTS.md
- design-templates/AGENTS.mdAGENTS.md
- e2e/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- plugins/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- tools/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- od-contributeSkill
- 8-bit-orbit-video-templateSkill
- ad-creativeSkill
- after-hours-editorial-templateSkill
- agent-browserSkill
- ai-music-albumSkill
- algorithmic-artSkill
- apple-higSkill
- article-magazineSkill
- artifacts-builderSkill
- brainstormingSkill
- brand-extractSkill
- brand-guidelinesSkill
- brandkitSkill
- industrial-brutalist-uiSkill
- canvas-designSkill
- card-twitterSkill
- card-xiaohongshuSkill
- color-expertSkill
- competitive-ads-extractorSkill
- copywritingSkill
- creative-directorSkill
- d3-visualizationSkill
- data-reportSkill
- deck-guizang-editorialSkill
- deck-open-slide-canvasSkill
- deck-swiss-internationalSkill
- design-briefSkill
- design-consultationSkill
- design-mdSkill
- design-reviewSkill
- digits-fintech-swiss-templateSkill
- doc-kami-parchmentSkill
- docSkill
- docxSkill
- domain-name-brainstormerSkill
- ecommerce-image-workflowSkill
- editorial-burgundy-principles-templateSkill
- emilkowalski-motionSkill
- enhance-promptSkill
- export-download-debuggingSkill
- fal-3dSkill
- fal-generateSkill
- fal-image-editSkill
- fal-kling-o3Skill
- fal-lip-syncSkill
- fal-realtimeSkill
- fal-restoreSkill
- fal-trainSkill
- fal-tryonSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Create a single-page HTML decision artifact that helps a product or design team turn messy evidence into a clear next move.
- Very specific: line 65
Read references/evidence-model.md before synthesis and run references/checklist.md before emitting the artifact.
- Distinctive: line 70
Use this skill when the user has any mix of:
- Distinctive: line 81
Do not use it for pure visual inspiration, campaign ideation, or brand moodboards.
- Distinctive: line 90
Write a short frame with:
- Distinctive: line 98
If key context is missing and the task is not blocked, proceed with labelled assumptions instead of asking a broad question.
- Distinctive: line 117
Never invent quotes, participant counts, dates, revenue impact, or metrics.
- Distinctive: line 131
Prefer verbs over nouns: "Teams abandon setup when the first blank state asks for too much" is better than "Onboarding problem".
- Distinctive: line 136
Create an opportunity matrix with 3 to 5 options.
- Distinctive: line 149
Write a decision memo with:
- Distinctive: line 158
Keep the memo short enough to read in under one minute.
- Distinctive: line 177
No framework dependency is required.
- Distinctive: line 181
Run the checklist. Then emit one concise orientation sentence and one HTML artifact:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
research-decision-room/
├── SKILL.md
├── example.html
└── references/
├── checklist.md
└── evidence-model.mdRead 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 asI-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".
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:
- Recommended move.
- Why now.
- What evidence supports it.
- What could be wrong.
- What to measure next.
- 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:
- Header with decision question, confidence, and last-updated label.
- Executive readout with recommendation, risk, and next experiment.
- Evidence ledger with filter chips.
- Theme map with evidence ids and confidence.
- Opportunity matrix.
- Decision memo.
- Experiment queue with owner, metric, and success threshold.
- 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:
<artifact identifier="research-decision-room" type="text/html" title="Research Decision Room">
<!doctype html>
<html>...</html>
</artifact>Nothing after the closing </artifact>.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

