positioning-statement

Create a Geoffrey Moore-style positioning statement. Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives.

Quality

73%

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/positioning-statement/SKILL.md

Quality

Content

60%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 skill is well-structured and actionable with a clear five-step workflow and quality checks, but it is padded with positioning theory Claude already knows and, critically, references bundle files (template.md, examples/sample.md) that do not exist in the skill bundle. Trimming the redundant explanation and either providing the referenced files or inlining their content would materially raise both conciseness and progressive disclosure.

Suggestions

Remove the verbatim repeat of the frontmatter intent in the Purpose section and condense 'Why This Structure Works' / 'Anti-Patterns', which restate positioning concepts Claude already knows.

Resolve the dangling references: either ship template.md and examples/sample.md in the bundle, or inline the template fully (it already is) and drop the file pointers.

Fold the Common Pitfalls section into the existing Step quality checks to eliminate the duplicated guidance and tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is noticeably padded — the Purpose section repeats the frontmatter intent verbatim, 'Why This Structure Works' and 'Anti-Patterns' explain positioning concepts Claude already knows, and the Common Pitfalls section re-covers ground already addressed by the Step quality checks.	3 / 5
Actionability	The two fill-in templates (Value Proposition, Differentiation Statement) and the 5-question stress test are concrete, copy-ready guidance with specific quality checks; it falls just short of a 5 because there is no executable worked example beyond the brief Slack excerpt.	4 / 5
Workflow Clarity	Steps 1-5 are clearly sequenced with embedded quality-check checkpoints and an explicit 'If any answer is no or sort of, revise' revision loop; it is not a 5 because the validation is judgment-based rather than a hard verify-and-proceed gate.	4 / 5
Progressive Disclosure	The body tells the reader to 'Use template.md' and 'See examples/sample.md', but no references/ or assets/ bundle exists and neither file is present — the references are dangling/buried rather than realized, and content that should live in those files is inlined into SKILL.md.	2 / 5
	Total	13 / 20 Passed

Description

87%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.

A well-crafted description that cleanly states what it does and when to use it, anchored to a specific named framework that distinguishes it from sibling skills. It is third-person and trigger-rich; the only mild gap is missing common synonyms like 'value proposition' or 'messaging'.

Dimension	Reasoning	Score
Specificity	The phrase 'Create a Geoffrey Moore-style positioning statement' names a concrete action and framework, and 'clarifying who you serve, what problem you solve, your category, and why you're different' enumerates several specific actions; minor gaps in coverage keep it just below a 5.	4 / 5
Completeness	It explicitly answers what ('Create a Geoffrey Moore-style positioning statement') and when ('Use when clarifying who you serve, what problem you solve, your category, and why you're different from alternatives') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'positioning statement', 'who you serve', 'what problem you solve', 'category', and 'different from alternatives' are natural phrases users would say, though common synonyms like 'value proposition' or 'messaging' are absent.	4 / 5
Distinctiveness Conflict Risk	'Geoffrey Moore-style positioning statement' carves a clear niche with distinct triggers; minimal overlap risk with adjacent product-strategy skills given the named framework.	5 / 5
	Total	18 / 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/positioning-statement/SKILL.md
Commit: 1b5a524

Reviewed: ~8 hours 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.