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

81%

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

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-sequenced and actionable, with a clear five-step workflow and concrete templates and quality checks. Its weaknesses are conciseness (duplicated framework and verbatim intent restatement) and progressive disclosure (dangling references to missing bundle files plus inline content that should be split out).

Suggestions

Remove the verbatim duplication of the frontmatter intent in the 'Purpose' section and consolidate the framework so it appears once rather than across Key Concepts, the Application template, and the mini example.

Create the referenced bundle files (template.md and examples/sample.md) or remove the dangling references, and move the inline fill-in template into template.md so the SKILL.md body stays a lean overview.

Expand the description's trigger terms to include natural variations like 'problem framing', 'define the problem', and 'align stakeholders' to improve trigger coverage.

Dimension	Reasoning	Score
Conciseness	The ~250-line body restates the framework three times (Key Concepts, the Application template blocks, and a mini example) and the 'Purpose' section duplicates the frontmatter intent verbatim, so it could be tightened despite being well-organized.	2 / 3
Actionability	It provides a concrete fill-in template, a synthesis formula, a worked example, and per-section quality checks — specific, copy-paste-ready guidance appropriate for an instruction-only skill.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced (Gather → Draft → Document → Craft → Validate) with explicit quality-check checklists and a validation/socialize step acting as checkpoints.	3 / 3
Progressive Disclosure	It signals references to template.md and examples/sample.md, but those files do not exist in the bundle, and the framework template is duplicated inline rather than split into template.md, leaving structure partial.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 specific, complete, and distinct, clearly stating what it produces and when to use it. Its main weakness is trigger-term coverage, which captures the obvious cases but omits several natural phrasings a user might say.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete sub-actions — 'who is blocked, what they are trying to do, why it matters, and how it feels' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It answers both 'what' ('Write a user-centered problem statement...') and 'when' ('Use when framing discovery, prioritization, or a PRD.') with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes relevant natural terms ('framing discovery, prioritization, or a PRD') but misses common variations like 'problem framing', 'define the problem', or 'align stakeholders', so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The 'user-centered problem statement' framing tied to discovery/prioritization/PRD triggers carves a distinct niche; adjacency to sibling PM skills is minor and unlikely to cause wrong-skill triggering.	3 / 3
	Total	11 / 12 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: 9971018

Reviewed: 3 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.