CtrlK
BlogDocsLog inGet started
Tessl Logo

user-personas

Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights. Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions.

65

Quality

82%

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

67%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 content is a clear, well-structured instruction skill with concrete output fields and a sequenced analysis workflow. Its main gaps are minor role-play padding, overlap between Best Practices and Analysis Steps, and the absence of a worked example or explicit validation feedback loop.

Suggestions

Remove the opening role-play sentence ("You are an experienced product researcher...") and deduplicate Best Practices against the Analysis Steps to trim token use.

Add one short worked persona example (or a compact output template) so the expected output depth and format are unambiguous.

Make the Validation step an explicit feedback loop: if personas are not grounded in the data, return to Pattern Recognition/Enrichment and revise before finalizing.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept-explanation filler, but the opening role-play line ("You are an experienced product researcher specializing in persona development and user research synthesis") and the Best Practices list, which overlaps the Analysis Steps, add unnecessary tokens.

3 / 5

Actionability

The Output Structure gives concrete, named fields with sub-bullets (JTBD, Top 3 Pain Points, Desired Gains, Unexpected Insight, Product Fit Assessment) and the analysis steps are specific, but no worked example or template demonstrates expected depth, capping it below 5.

4 / 5

Workflow Clarity

Five numbered analysis steps are clearly sequenced including a Validation step, but the validation lacks an explicit error-recovery/feedback loop (what to do when personas are not grounded), leaving a minor validation gap.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (Purpose, Input, Analysis Steps, Output Structure, Best Practices, Further Reading) and is self-contained with cleanly separated one-level external links, but it sits just past the simple-skill threshold and the links point off-site rather than to organized bundle material.

4 / 5

Total

15

/

20

Passed

Description

87%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 strong: it states a concrete deliverable count and contents, then gives three explicit natural-language use-when triggers with synonyms. Its only weakness is mild output-vs-action framing and the soft adjective "refined."

DimensionReasoningScore

Specificity

"Create refined user personas from research data" names the domain and lists several concrete deliverables ("3 personas with JTBD, pains, gains, and unexpected insights"), but framing is output-oriented rather than action-oriented and "refined" is mild fluff, so it falls just below the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both what ("Create refined user personas... with JTBD, pains, gains, and unexpected insights") and when ("Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when building personas from survey data, creating user profiles from research, or segmenting users for product decisions" offers good natural-keyword coverage with synonyms (personas, user profiles, segmentation), missing only a few variations like interview data.

4 / 5

Distinctiveness Conflict Risk

The persona-from-research niche with distinct triggers (building personas, user profiles, user segmentation) is clearly distinguishable from other skills and carries minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-skills
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.