positioning-workshop

Run a positioning workshop that surfaces target customer, unmet need, category, benefits, and differentiation. Use when your product messaging feels fuzzy, generic, or misaligned.

Quality

88%

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 content is highly actionable and clearly sequenced with embedded quality checks and refinement loops, but it is verbose for its length and keeps the entire question bank, examples, and pitfalls inline rather than progressively disclosing them into bundle files.

Suggestions

Remove the redundant Purpose paragraph (it restates the frontmatter intent verbatim) and trim the 'Why This Works' and 'Anti-Patterns' sections to the essential bits, since Claude already understands positioning and discovery concepts.

Move the two worked examples and the five Common Pitfalls into a separate references/ file (e.g. examples.md), keeping SKILL.md as an overview that links to it — this raises progressive disclosure from inline-heavy to appropriately split.

Consolidate the per-question enumerated option banks (which repeat the same B2B SMB example across Q1-Q5) into a single adaptation table or reference file to cut repeated tokens while preserving actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient domain guidance, but the "Why This Works" and "Anti-Patterns (What This Is NOT)" sections plus the Purpose paragraph (which restates the frontmatter intent nearly verbatim) are padding Claude does not need, fitting "mostly efficient but includes some unnecessary explanation" rather than lean (anchor 3).	2 / 3
Actionability	Each question supplies exact prompts, 3-4 enumerated options with concrete examples (e.g., "B2B: SMB decision-makers — Small business owners (10-50 employees)"), adaptation tips, and a fill-in output template, giving copy-paste-ready instruction-only guidance rather than vague direction.	3 / 3
Workflow Clarity	The flow is explicitly sequenced (Step 0 gather context → Questions 1-5 → Output statement → Next Steps), with inline quality checks (Q4 "Avoid features... Focus on outcomes") and a feedback loop in Next Steps ("If target feels too broad → Narrow further"; stress-test with 5 customers), matching clear sequence with validation/refinement.	3 / 3
Progressive Disclosure	References are well-signaled and one-level-deep (e.g., "Use [`workshop-facilitation`]... as the default interaction protocol"; "uses `positioning-statement.md`"), but no bundle files exist and the full question bank, two worked examples, and five pitfalls all live inline in a ~415-line SKILL.md, so content that could be separate is inline (anchor 2) rather than appropriately split (anchor 3).	2 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, concrete, and uses third-person imperative voice with no first/second-person. It cleanly answers both what the skill does and when to use it, with natural trigger terms and a distinctive positioning niche.

Dimension	Reasoning	Score
Specificity	"surfaces target customer, unmet need, category, benefits, and differentiation" lists five concrete, specific outputs the skill produces, matching the anchor for multiple specific concrete actions rather than the vague single-domain anchor at 2.	3 / 3
Completeness	It states what ("Run a positioning workshop that surfaces...") and an explicit when trigger ("Use when your product messaging feels fuzzy, generic, or misaligned"), clearly answering both halves rather than leaving when only implied (anchor 2).	3 / 3
Trigger Term Quality	The clause "product messaging feels fuzzy, generic, or misaligned" plus "positioning" are natural phrases a PM would actually say when they need this skill, giving good coverage rather than only some relevant keywords (anchor 2).	3 / 3
Distinctiveness Conflict Risk	"positioning workshop" is a clear niche with distinct triggers tied to messaging clarity, making it unlikely to fire for unrelated skills; it is not generic like "Helps with code and documents" (anchor 1) nor merely domain-named like "Works with document files" (anchor 2).	3 / 3
	Total	12 / 12 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/positioning-workshop/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.