problem-statement

Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.

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 ./skills/problem-statement/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 instruction-only skill with a clear five-step workflow and embedded quality checks. Its main weaknesses are verbosity from duplicated sections and references to bundle files (template.md, examples/sample.md) that are not present in the skill bundle.

Suggestions

Remove the verbatim repeat of the frontmatter intent in the Purpose section and consolidate the Anti-Patterns and Common Pitfalls sections, which cover the same ground twice.

Either add the referenced `template.md` and `examples/sample.md` under references/ (or assets/) or drop the references so signaled navigation does not point to missing files.

Trim the "Why This Structure Works" and placeholder "Dean's Work" lines, which explain concepts Claude already knows or carry no usable content.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but includes padding that could be tightened — the Purpose section repeats the frontmatter intent verbatim, "Why This Structure Works" re-explains framework rationale Claude already knows, and Common Pitfalls substantially overlaps the Anti-Patterns section, plus a placeholder "Dean's Work" line.	3 / 5
Actionability	It provides a concrete fill-in narrative template, an explicit final-statement formula, a worked mini example, and per-step quality checks — actionable guidance with only minor gaps (placeholders rather than a fully worked end-to-end example inline), fitting the 4 anchor.	4 / 5
Workflow Clarity	Steps 1–5 are clearly sequenced with quality-check checkpoints after each draft step and a validate/socialize/iterate loop in Step 5, but it stops short of the fully explicit validate→fix→retry feedback loop that would warrant a 5.	4 / 5
Progressive Disclosure	The body is sectioned and signals references to `template.md` and `examples/sample.md`, but those bundle files do not exist in references/ or assets/, so the signaled navigation points to missing material and the split is not actually realized, capping it at 3.	3 / 5
	Total	14 / 20 Passed

Description

78%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 well-constructed, clearly answering both what the skill does and when to use it with a concrete trigger clause. Trigger term coverage is strong and the niche is reasonably distinct, though specificity is a single composite action rather than a list of concrete operations.

Dimension	Reasoning	Score
Specificity	"Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels" names the domain and enumerates concrete sub-elements, but it is essentially a single action with component parts rather than several distinct concrete actions, so it sits at the 3 anchor rather than 4.	3 / 5
Completeness	It explicitly answers both what ("Write a user-centered problem statement with...") and when ("Use when framing discovery, prioritization, or a PRD") with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	"Use when framing discovery, prioritization, or a PRD" plus "problem statement" gives good natural keyword coverage a user would actually say, though common synonyms like "user research" or "problem framing" are only weakly covered, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	"user-centered problem statement" carves a fairly distinct niche, but it could still overlap with closely related framing skills like positioning-statement or user-story, so minor overlap risk keeps it at 4 rather than 5.	4 / 5
	Total	16 / 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/problem-statement/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.