CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/positioning-statement/SKILL.md
SKILL.md
Quality
Evals
Security

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 delivers a clear, actionable, well-sequenced positioning workflow with strong validation checkpoints and useful domain pitfalls. Its main weaknesses are verbosity from repeated template/concept restatements and a progressive-disclosure structure that names files (template.md, examples/sample.md) which are not present in the bundle.

Suggestions

Dedupe the body: state the Moore template once and have Purpose/Anti-Patterns point to it instead of restating it, and remove the verbatim repetition of the frontmatter intent in the Purpose section.

Either create the referenced `template.md` and `examples/sample.md` as real bundle files and keep SKILL.md as a lean overview, or remove the dangling references and consolidate the content inline so the disclosure structure is honest.

DimensionReasoningScore

Conciseness

Much of the body is genuinely useful positioning expertise (pitfalls, quality checks), but it is padded by redundancy: the Purpose section repeats the frontmatter intent verbatim, the Moore template appears three times, and "Anti-Patterns" / "Why This Structure Works" overlap with the later "Common Pitfalls" section; it is not level 1 because the content is domain-specific rather than generic concepts Claude already knows, and not level 3 because the redundancy could be tightened.

2 / 3

Actionability

As an instruction-only skill it provides a concrete fill-in template, per-slot quality checks, a five-question stress test, and a Slack mini-example — specific and actionable guidance; per the scoring notes the absence of code is not penalized, so it meets the level-3 anchor for actionable instruction.

3 / 3

Workflow Clarity

The five Application steps are clearly sequenced, and Step 4 (Stress-Test) is an explicit validation checkpoint with the feedback loop "If any answer is 'no' or 'sort of,' revise," matching the level-3 anchor of clear sequence with validation and error-recovery; it is not level 2 because checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

The body is well-sectioned and references are clearly signaled ("Use `template.md`", "See `examples/sample.md`"), but no bundle files exist, so those one-level references point to missing files and the ~220-line skill remains effectively monolithic with content that should be split kept inline; it is not level 1 because sections are organized and references are not deeply nested, and not level 3 because the referenced files are absent rather than appropriately realized.

2 / 3

Total

10

/

12

Passed

Description

75%

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 cleanly answers both what the skill does and when to use it, with a distinct, well-scoped niche. It is held back from the top tier only by a single stated action and somewhat formal trigger phrasing that under-cover natural user terms.

Suggestions

Add one or two more concrete actions (e.g., "draft and stress-test a positioning statement") to lift specificity toward level 3.

Include common natural variations users would say — "value proposition," "messaging," or "differentiate from competitors" — alongside "positioning statement" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain and one concrete action ("Create a Geoffrey Moore-style positioning statement") but does not list multiple specific concrete actions; the remainder ("clarifying who you serve, what problem you solve, your category, and why you're different from alternatives") describes scope/trigger rather than additional actions, so it stops short of the level-3 anchor.

2 / 3

Completeness

It explicitly states what it does ("Create a Geoffrey Moore-style positioning statement") and gives an explicit "Use when clarifying..." trigger clause, clearly answering both what and when as in the level-3 anchor; it is not level 2 because the when is explicit rather than implied.

3 / 3

Trigger Term Quality

"positioning statement" is a natural term a user would say, and "different from alternatives" / "who you serve" are relevant, but the phrasing is somewhat formal and omits common variations such as "value proposition," "messaging," or "differentiate from competitors," so coverage is good but not comprehensive as required for level 3.

2 / 3

Distinctiveness Conflict Risk

The "Geoffrey Moore-style positioning statement" framing plus triggers around category and differentiation form a clear niche unlikely to fire for unrelated skills; it is not level 2 because the triggers are specific to positioning rather than broadly overlapping.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
deanpeters/Product-Manager-Skills
Reviewed

Table of Contents

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.