proto-persona

Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.

Quality

60%

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 ./skills/proto-persona/SKILL.md

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 content is a well-structured, actionable guide with clear steps, templates, quality checks, and pitfalls. Its weaknesses are conceptual padding that restates what Claude already knows and dangling references to bundle files (template.md, examples/sample.md) that are not provided.

Suggestions

Trim the 'Key Concepts' conceptual exposition (What is a Proto-Persona, Proto vs Validated, Why Use, Anti-Patterns) since Claude already knows persona fundamentals; keep only what is non-obvious.

Either add the referenced `template.md` and `examples/sample.md` to the bundle or remove the references and keep the templates inline to avoid dangling pointers.

Add a short 'Definition of done' or validation checklist to Step 6 to close the feedback loop and raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with actionable steps, templates, and pitfalls, but it carries conceptual padding Claude already knows (the 'What is a Proto-Persona', 'Proto vs Validated', 'Why Use', and 'Anti-Patterns' sections) plus a Purpose block that restates the frontmatter intent.	3 / 5
Actionability	It provides concrete fill-in markdown templates for every persona field plus per-field quality checks, worked examples, and pitfall fixes; as an instruction-only skill the absence of code is not penalized, though the templates still use placeholder brackets rather than fully worked outputs.	4 / 5
Workflow Clarity	Steps 1-6 are clearly sequenced with per-field 'Quality checks' acting as checkpoints and a dedicated Step 6 'Validate and Iterate' feedback loop; it stops short of a 5 because there is no explicit error-recovery or done-state checklist.	4 / 5
Progressive Disclosure	Sections are well organized, but the body references `template.md` and `examples/sample.md` that are not present in any bundle directory, and the template content is inlined in SKILL.md rather than split out, leaving references dangling and structure only partially realized.	3 / 5
	Total	14 / 20 Passed

Description

57%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 clearly states what the skill does and gives an explicit use-trigger, with a distinct proto-persona niche. Its main weaknesses are a single concrete action, missing synonym coverage, and second-person phrasing ('you need') that triggers a specificity penalty.

Suggestions

Replace 'you need' with third-person phrasing (e.g., 'Use when a working customer profile is needed before deeper validation') to avoid the second-person specificity penalty.

Broaden trigger-term coverage with natural synonyms such as 'user persona', 'target user', or 'buyer persona' alongside 'customer profile'.

Add 1-2 more concrete actions (e.g., 'synthesizes signals, flags assumptions needing validation') to lift specificity beyond a single verb.

Dimension	Reasoning	Score
Specificity	The description names the domain ('proto-persona') and one concrete action ('Create'), pulling from research/market/team knowledge, but offers only a single action and no granular capabilities; specificity is further reduced by one per the second-person ('you need') penalty, dropping it from 3 to 2.	2 / 5
Completeness	Both 'what' ('Create a proto-persona from current research, market signals, and team knowledge') and 'when' ('Use when you need a working customer profile before deeper validation') are explicitly present, though the trigger clause is a single condition rather than a concrete list of phrases.	4 / 5
Trigger Term Quality	It includes some natural phrases users would say ('working customer profile', 'deeper validation'), but misses common synonyms like 'user persona', 'target user', or 'buyer persona' and leans on the somewhat technical 'proto-persona'.	3 / 5
Distinctiveness Conflict Risk	'proto-persona' carves a clear niche that is mostly distinct from adjacent research skills, with only minor overlap risk against general persona or user-research skills; it is not fully conflict-free because 'customer profile' is broad.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/proto-persona/SKILL.md
Commit: a03af68

Reviewed: 11 days 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.