problem-framing-canvas

Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/problem-framing-canvas/SKILL.md

Quality

Content

77%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 highly actionable and well-sequenced with concrete prompts, options, and an output template, but it is held back by verbosity (repeated description, conceptual padding) and a missing referenced bundle file (template.md) that leaves progressive disclosure only partially realized.

Suggestions

Remove the verbatim repeat of the description in the Purpose section and trim the "What is", "Why This Works", and "Anti-Patterns" conceptual blocks, which restate knowledge Claude already has.

Bundle the referenced template.md and examples/sample.md files (or inline only what is essential and drop the dangling references), since progressive disclosure only works when signaled files actually exist.

Consider moving the full canvas output template into template.md and keeping SKILL.md as a concise overview that points to it, reducing the inlined bulk.

Dimension	Reasoning	Score
Conciseness	The body is roughly 460 lines with notable padding: the frontmatter description is repeated verbatim in the Purpose section, and explanatory blocks ("What is the MITRE Problem Framing Canvas?", "Why This Works", "Anti-Patterns") restate concepts Claude already knows; it is mostly efficient but could be tightened significantly.	3 / 5
Actionability	Each phase supplies exact agent prompts, enumerated option sets with examples, capture/extract instructions, and a copy-paste-ready markdown output template, giving fully executable guidance that covers the common cases.	5 / 5
Workflow Clarity	The three-phase sequence (Look Inward → Look Outward → Reframe) with Step 0 context gathering, numbered questions, and explicit approve/modify checkpoints provides a clear, well-sequenced workflow with feedback loops; no destructive or batch operations trigger the validation cap.	5 / 5
Progressive Disclosure	References are one-level-deep and clearly signaled (template.md, examples/sample.md, workshop-facilitation), but no bundle files are actually present so the referenced template/sample files do not exist, and the full eight-question flow plus the complete output template is inlined rather than split out.	3 / 5
	Total	16 / 20 Passed

Description

70%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 clear, third-person, and answers both what and when with an explicit trigger clause, landing in a solid 4 range for most dimensions. Its main weakness is specificity, since it names only one overarching action rather than enumerating the canvas's concrete steps.

Suggestions

Add 1-2 concrete actions to raise specificity, e.g. "Guide teams through MITRE's Problem Framing Canvas — examine assumptions, map stakeholders, and synthesize a 'How Might We' statement."

Broaden trigger terms with natural synonyms users say, such as "reframe", "problem framing workshop", or "are we solving the right problem".

Make the 'when' clause more concrete with triggering situations, e.g. "Use when starting discovery, reframing a stakeholder request, or before committing to a solution."

Dimension	Reasoning	Score
Specificity	"Guide teams through MITRE's Problem Framing Canvas" names the domain and a single concrete action anchored to a specific named framework, which fits the anchor listing 1-2 concrete actions; it does not enumerate the multiple specific actions required for a 4.	3 / 5
Completeness	It states what the skill does ("Guide teams through MITRE's Problem Framing Canvas") and gives an explicit "Use when..." trigger ("when you need a clearer problem statement before jumping to solutions"), but the trigger is general rather than listing concrete triggering situations, so it is not a 5.	4 / 5
Trigger Term Quality	"problem statement", "jumping to solutions", and "Problem Framing Canvas" are natural phrases a PM might say, giving good keyword coverage; common synonyms like "reframe" or "workshop" are missing, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	The MITRE Problem Framing Canvas niche and the "before jumping to solutions" trigger make it mostly distinct with only minor overlap against general problem-statement/discovery skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/problem-framing-canvas/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.