CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

persona

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

53

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/persona/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 admirably lean and organized around usage, input format, and examples, but it is hampered by dead references (the cited script and skill-reference files do not exist in the bundle) and by the absence of an executable script invocation or a sample persona output. A reader knows the commands exist but not exactly how to run or validate the underlying generator.

Suggestions

Fix or remove the dead references: either include persona_generator.py in a scripts/ directory with a correct relative path, or drop the Scripts and Skill Reference sections pointing to non-bundle files.

Show an executable invocation example for the script (e.g. "python scripts/persona_generator.py json") and what its positional arguments accept.

Add a brief sample persona output (or field list) so the expected structure of the generated persona is unambiguous, and trim the Examples section that duplicates the Usage commands.

DimensionReasoningScore

Conciseness

The body is lean (~40 lines) with no concept explanations and assumes competence ("Interactive mode prompts for product context"). Minor trims exist: the Examples section repeats the two Usage commands, and the trailing "Skill Reference" line adds little value, keeping it just below anchor 5's every-token-earns-its-place standard.

4 / 5

Actionability

Slash commands ("/persona generate", "/persona generate json") are concrete, but the Scripts section never shows an executable invocation of persona_generator.py (e.g. a python command line), gives no sample persona output structure, and the referenced script path does not exist in the bundle. Concrete-but-incomplete guidance with missing key details matches anchor 3 rather than 4.

3 / 5

Workflow Clarity

As a simple single-action skill with clear interactive-vs-inline input paths, the simple-skill exception applies; the single action is largely unambiguous. It falls short of 5 because there is no example persona or output structure, and it is unclear how the script is actually invoked versus the slash command.

4 / 5

Progressive Disclosure

Sections are present and labeled (Usage, Input Format, Examples, Scripts), but both referenced paths ("product-team/skills/ux-researcher-designer/scripts/persona_generator.py" and the "Skill Reference" SKILL.md) point to files absent from the bundle — no scripts/, references/, or assets/ directories exist. The cross-skill "Skill Reference" indirection is also poorly signaled navigation, matching anchor 3 (some structure, references present but problematic) rather than 4.

3 / 5

Total

14

/

20

Passed

Description

53%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 communicates a clear purpose in a distinct niche, but stops at a single action verb and omits any "Use when..." trigger guidance, leaving Claude without explicit cues for when to reach for this skill. Invocation syntax ("Usage: /persona generate [options]") is not a substitute for usage triggers, and natural-language synonyms are thin.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. "Use when the user asks for user personas, customer personas, or audience profiles for UX research or product planning."

Enumerate the concrete actions/outputs (e.g. demographics, goals, pain points, behavioral patterns, JSON export) so the description matches the body's actual capabilities.

Include common synonyms and natural phrasings users would say ("customer persona", "audience profile", "user research") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Generate data-driven user personas for UX research and product design" names the domain and one concrete action, but lists no further specific actions (no demographics, pain points, or output formats). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

The description clearly answers "what" ("Generate data-driven user personas for UX research and product design") but has no "Use when..." clause or equivalent trigger guidance; "Usage: /persona generate [options]" is invocation syntax, not usage timing. Per the guideline, a missing trigger clause caps completeness at 3, matching anchor 3 exactly (clear what, when missing).

3 / 5

Trigger Term Quality

Keywords "user personas", "UX research", and "product design" are relevant, but common natural variations a user would say ("customer personas", "audience profiles", "user research") are absent. Some relevant keywords with missing synonyms fits anchor 3 rather than 4's good-but-incomplete coverage.

3 / 5

Distinctiveness Conflict Risk

"Generate data-driven user personas for UX research" carves a mostly distinct niche with only minor overlap risk against adjacent UX-research or writing skills. It is not 5 because there are no explicit trigger phrases and "product design" is a broad surface for overlap.

4 / 5

Total

13

/

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

alirezarezvani/claude-skills

Path

.gemini/skills/persona/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.