CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

Run fast, source-grounded UX research on the highest-signal problems users are experiencing with a user-specified digital product. Use when the user asks to research user pain, UX friction, onboarding issues, docs/help problems, developer experience friction, support pain, product workflow issues, or current user complaints for a named product.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/product-design/skills/research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-structured, lean instruction skill with a concrete workflow, explicit source lists, and a fully specified output format. Its weaknesses are duplicated rules across the Contract and Rules sections, the absence of an explicit validation step in the workflow, and body references pointing to bundle files that do not exist.

Suggestions

Fix or remove the dangling references: ../index/SKILL.md, ../../references/critical-overrides.md, and ../user-context/SKILL.md do not exist in the skill bundle, so either ship those files or drop the pointers.

Deduplicate the Contract and Rules sections: "Do not overclaim from anecdotes" appears verbatim in both, and "Cite sources wherever available" / "Use citations wherever available" are the same rule stated twice; merge them into one section.

Add an explicit validation checkpoint to the workflow (e.g., after clustering, verify each problem has at least two independent sources and mark single-source problems as low confidence) to close the feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no concept explanations Claude already knows, but rules are duplicated between the Contract and Rules sections ("Cite sources wherever available" vs "Use citations wherever available", and "Do not overclaim from anecdotes" appears verbatim in both). These minor redundancies could be trimmed, matching the efficient-with-minor-excess anchor rather than the every-token-earns-its-place anchor of 5.

4 / 5

Actionability

As an instruction-only skill it gives concrete guidance: named public sources (Reddit, X/Twitter, Hacker News, Stack Overflow, GitHub issues), named internal sources (Slack, Gong, Notion, Drive, Linear/Jira), explicit clustering categories, ranking criteria (severity, frequency, confidence, product leverage), and a fully specified output template with an executive read of 5-7 sentences and three opportunity buckets. Minor gaps remain, such as how to formulate searches or how to gauge frequency signal, so it stops short of fully executable guidance.

4 / 5

Workflow Clarity

The seven numbered steps form a clear, coherent sequence from scope restatement through source searching, clustering, ranking, and storytelling, with partial checkpoints via the Contract ("Say clearly when source access is missing or weak", "Separate observed evidence from inference"). However, there is no explicit validation or feedback step in the workflow itself, so it matches "clear sequence with most checkpoints present; minor validation gaps" rather than the explicit feedback-loop anchor of 5.

4 / 5

Progressive Disclosure

Sections are well organized and the inline content is appropriately sized for a research skill, but all three file references in the body ([../index/SKILL.md], [../../references/critical-overrides.md], [../user-context/SKILL.md]) point to files that do not exist in this bundle, and no references/ or scripts/ files are provided. Navigation is therefore broken for the referenced materials, fitting "references present but not clearly signaled / could be better organized" rather than the good-structure anchor of 4.

3 / 5

Total

15

/

20

Passed

Description

78%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.

A strong description that explicitly covers both what the skill does and when to use it, with a rich set of natural trigger phrases and a well-scoped niche. The main gap is that it names only one composite action rather than enumerating the specific research actions performed, and a few common trigger synonyms are missing.

DimensionReasoningScore

Specificity

"Run fast, source-grounded UX research on the highest-signal problems users are experiencing with a user-specified digital product" names the domain and one concrete action with strong qualifiers, but does not enumerate several discrete actions (e.g., searching sources, clustering evidence, ranking problems). This matches the anchor for 1-2 concrete actions without comprehensive coverage; a 4 would require a list of several specific actions.

3 / 5

Completeness

It clearly states what the skill does ("Run fast, source-grounded UX research on the highest-signal problems...") and explicitly answers when to use it with concrete trigger phrases ("Use when the user asks to research user pain, UX friction, onboarding issues..."). Both what and when are explicitly and concretely answered, matching the top anchor.

5 / 5

Trigger Term Quality

The "Use when" clause lists eight natural phrases users would say ("user pain", "UX friction", "onboarding issues", "docs/help problems", "developer experience friction", "support pain", "product workflow issues", "current user complaints") with synonym variation. Coverage is good but misses common variants such as "usability issues", "customer feedback", or "user reviews", so it does not reach the comprehensive-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The niche of UX pain research for a named product with listed trigger surfaces is mostly distinct, but the broad verb "research" leaves minor overlap risk with closely related skills such as market research or competitive analysis. It fits "mostly distinct; minor overlap risk" rather than the minimal-conflict anchor of 5.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

plugins/product-design/skills/research/SKILL.md

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.