CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, highly actionable, and uses progressive disclosure effectively with real reference files. It is instruction-only but the guidance is concrete and specific, with a clear sequenced workflow and self-check checkpoint.

Suggestions

Trim reframing lines like 'The output is not a decorative research deck. It is a working room for debate' and the 'When to use' bullet list that restates frontmatter triggers, to tighten conciseness toward a 5.

The 'When to use this skill' section duplicates the frontmatter trigger guidance; consider consolidating to a single location to avoid redundancy.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes competence (concrete ledger schema, scoring scale, memo template), but a few lines restate the frontmatter or add mild framing ('The output is not a decorative research deck. It is a working room for debate') that could be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance throughout — a full ledger row schema with field names and enumerated values, a 1–5 opportunity scoring rubric with defined directionality, a 6-part decision memo template, an 8-section information architecture, and the exact artifact emission block.

5 / 5

Workflow Clarity

Seven explicitly sequenced steps with a self-check/validation checkpoint in Step 7 ('Run the checklist. Then emit...') and the prior instruction to run references/checklist.md before emitting, giving a clear feedback loop.

5 / 5

Progressive Disclosure

Includes a resource map and clearly signals one-level-deep references — 'Read references/evidence-model.md before synthesis and run references/checklist.md before emitting' — both of which exist as real files in references/.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive, with strong natural trigger terms. It clearly states what the skill produces and when to use it without vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and outputs — 'evidence ledger, theme map, confidence heatmap, opportunity matrix, decision memo, and experiment queue' — bundled into a 'single HTML artifact', giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both what ('Turn...into an evidence-backed decision room: a single HTML artifact...') and when ('Use when teams need to move from qualitative signals to product or design decisions without fabricating certainty').

5 / 5

Trigger Term Quality

The triggers field provides comprehensive natural-phrase coverage ('user research synthesis', 'interview synthesis', 'qualitative research board', 'opportunity solution tree', 'usability findings dashboard') that users would genuinely say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (evidence-backed research synthesis decision artifact) with distinct, specific trigger phrases and an explicit boundary ('Do not use it for pure visual inspiration, campaign ideation, or brand moodboards'), minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.