persona

Generate data-driven user personas for UX research and product design. Usage: /persona generate [options]

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/persona/SKILL.md

Quality

Content

82%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 notably concise and well-structured with concrete invocation examples, though it relies on external non-bundled script references and omits an inline spec of the persona output structure. Tightening the external references and documenting the output shape would lift the score.

Suggestions

Document the generated persona's structure inline (the fields/demographics/goals/pain points/behavioral patterns it produces) so the output is predictable without the external script.

Replace the absolute external plugin paths with real bundle files under ./scripts/ and ./references/ so the references are one-level-deep and self-contained.

If multiple output modes (interactive vs. JSON) exist, add a short validation cue (e.g., confirm the JSON is well-formed before returning it).

Dimension	Reasoning	Score
Conciseness	The body is lean and direct with no padding or explanation of concepts Claude already knows; every section (usage, input format, examples, scripts) earns its place.	5 / 5
Actionability	Concrete invocations and an inline input example plus a real script path are provided, but the generated persona's output structure is not specified inline and the generation logic lives only in an external non-bundled script.	4 / 5
Workflow Clarity	This is a simple single-action skill with an unambiguous flow, qualifying for the simple-skill exception; it lands at 4 rather than 5 because two output modes are shown with no note on verifying the generated persona's quality.	4 / 5
Progressive Disclosure	Content is well-organized into short sections, but the "Scripts" and "Skill Reference" sections point at absolute external plugin paths rather than real bundle files in this skill's directory, and the two outward references overlap slightly.	4 / 5
	Total	17 / 20 Passed

Description

61%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 states a clear, concrete capability and uses natural trigger terms, but omits any explicit "when to use" guidance and lists only one action. Adding a trigger clause and one or two more specific actions would raise the score.

Suggestions

Add a "Use when..." clause naming concrete trigger situations (e.g., "Use when planning UX research, defining target audiences, or grounding product decisions in user profiles").

Expand the action list beyond a single verb, e.g., "Generate data-driven user personas with demographics, goals, pain points, and behavioral patterns for UX research and product design."

Include common synonyms users might say ("target users", "audience", "user profiles") alongside "user personas".

Dimension	Reasoning	Score
Specificity	"Generate data-driven user personas for UX research and product design" names the domain plus one concrete action, but action coverage is limited to a single verb rather than several specific capabilities.	3 / 5
Completeness	The "what" is clear (generate data-driven personas), but there is no "Use when..." trigger clause — only a "Usage:" invocation hint — so per the rubric a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	"user personas", "UX research", and "product design" are natural phrases a user would say, though common synonyms like "target users", "audience", or "user profiles" are missing.	4 / 5
Distinctiveness Conflict Risk	"Generate data-driven user personas for UX research and product design" carves a clear niche with minimal conflict risk, though it could mildly overlap with general research/design skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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: alirezarezvani/claude-skills
Path: .gemini/skills/persona/SKILL.md
Commit: 19392f7

Reviewed: ~11 hours ago

Table of Contents

Discovery Implementation Validation

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.