CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ux-research

Planeja pesquisa de usuarios, jornadas e testes de usabilidade. Trigger em: "pesquisa com usuário", "user research", "UX research", "discovery", "entrevista com usuário", "entrevista em profundidade", "persona", "criar persona", "mapa de jornada", "journey map", "mapa de empatia", "teste de usabilidade", "usability testing", "validar problema", "arquitetura de informação", "card sorting", "taxonomia", "proposição de valor", "produto que ninguém usa", "começar pelo usuário", "focus group".

Quality

84%

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

77%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, instruction-only skill with an exemplary protocol sequence — explicit checkpoints, a remediation feedback loop, gates, and a completion checklist — and textbook progressive disclosure into three well-signaled reference files. The main drag is token efficiency: book citations, anecdotes, and known-concept exposition recur across sections and could be trimmed without losing actionability.

Suggestions

Trim the anecdotes and attributed quotes (QR code case, Steve Jobs/Whitney Hess citations, flashlight story) from Protocolo and Heuristicas — keep the derived rule, drop the motivational narrative Claude doesn't need to execute.

Remove explanations of concepts Claude already knows, e.g., the qualitative-vs-quantitative exposition in step 2 ('Quantitativo dá o o quê... qualitativo dá o por quê'); the method-selection table already conveys the decision rule.

Consolidate the repeated provenance citations (Fabricio Teixeira book is referenced in the intro, Protocolo, and Heuristicas) into the single 'Fonte' section at the end.

DimensionReasoningScore

Conciseness

The body is mostly efficient actionable guidance, but several sections pad with material Claude does not need to execute: repeated book citations and quotes (Whitney Hess, Steve Jobs), anecdotes (the QR code case, the flashlight/basement story), and exposition of concepts Claude already knows (qualitative gives the 'why', quantitative the 'what'). This fits anchor 3 (mostly efficient with some unnecessary explanation that could be tightened) better than 4, as the over-explanation recurs across the Protocolo and Heuristicas sections.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: a question-to-method selection table, specific numbers ("teste com 3-5 usuários", "3-7 bullets", "5+ sessões" triggers the thematic pipeline), and concrete recruiting/environment/posture rules. It sits at anchor 4 rather than 5 because some steps remain high-level pointers into the references (e.g., step 5 'conforme o pedido') rather than fully specified guidance.

4 / 5

Workflow Clarity

A numbered six-step protocol (definir problema → escolher método → conduzir → sintetizar → produzir artefato → gates + handoff) with an explicit source-tracing checkpoint that includes an error-recovery loop ("reescrever ou remover a afirmação antes de entregar"), integrity and anti-AI gates in step 6, and a completion checklist in 'Evidencia de Conclusao'. This matches anchor 5's explicit validation, feedback loops, and checklists; the destructive/batch cap does not apply since research synthesis is neither.

5 / 5

Progressive Disclosure

The ~160-line body is a genuine overview with three real, correctly-pathed reference files, each given a one-line content description in a dedicated 'Referencias (carregar sob demanda)' section plus a load rule ('Carregar apenas a referência que o entregável pedido exige'). References are one level deep with no nested pointers, matching anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

17

/

20

Passed

Description

86%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 with an explicit, well-structured trigger clause covering both Portuguese and English phrasing, plus a clear third-person capability statement. Its main weakness is that the 'what' understates the skill's actual scope — personas, information architecture, card sorting and value proposition are only visible as trigger words, not as stated capabilities.

DimensionReasoningScore

Specificity

The description names the domain and three concrete actions ("Planeja pesquisa de usuarios, jornadas e testes de usabilidade"), but core deliverables like personas, card sorting, arquitetura de informação and proposição de valor appear only as trigger terms, not as stated actions. This matches anchor 3 (domain and 1-2 concrete actions, not comprehensive) rather than 4, since the gaps go beyond minor.

3 / 5

Completeness

It explicitly answers both questions: a clear third-person 'what' ("Planeja pesquisa de usuarios, jornadas e testes de usabilidade") and an explicit 'when' clause ("Trigger em: ...") with concrete trigger phrases, mirroring the anchor-5 example structure. It does not fall to 4 because the 'when' is fully explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Twenty-one natural trigger phrases with comprehensive synonym and bilingual coverage — "pesquisa com usuário", "user research", "UX research", "persona", "criar persona", "mapa de jornada", "journey map", "teste de usabilidade", "usability testing", "card sorting", "focus group". Users would naturally say nearly all of these when they need the skill, matching the comprehensive anchor 5.

5 / 5

Distinctiveness Conflict Risk

The UX-research niche is clear with mostly distinct triggers (journey map, card sorting, teste de usabilidade), but a few terms like "discovery", "taxonomia" and "arquitetura de informação" carry overlap risk with adjacent skills (ui-ux-design, data-analytics, content organization). This fits anchor 4 (mostly distinct, minor overlap with closely related skills) rather than 5's 'minimal conflict risk'.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/51-ux-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.