CtrlK
BlogDocsLog inGet started
Tessl Logo

startup-positioning

Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or refine their market positioning, find their unique position, differentiate from competitors, craft a positioning statement, choose a market category, or figure out "how should we position this product." Triggers for "positioning", "how to position", "market position", "differentiation strategy", "positioning statement", "competitive positioning", "category strategy", "where do we fit in the market", "how are we different", "unique value proposition", or any request to define, sharpen, or rethink positioning. Works standalone — no prior startup-design or startup-competitors session needed, but leverages their output if available.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, multi-phase instruction skill with explicit sequencing, validation checkpoints, feedback loops, and exemplary one-level-deep progressive disclosure backed by real reference files. The only weaknesses are minor editorial padding and deferred agent-template details.

Suggestions

Trim the editorializing in Phase 3 (e.g., the 'Positioning is a reasoning problem...' paragraph and the 'sppend extended thinking here' guidance) to tighten conciseness.

Reduce the inline anti-pattern table in the Honesty Protocol section since the full table already lives in references/honesty-protocol.md; keep only positioning-specific additions.

Consider inlining a compact Wave-1/Wave-2 agent prompt skeleton so the body is executable without opening the reference files, or confirm the deferral is intentional.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but includes some editorial padding (e.g., 'Positioning is a reasoning problem, not a fill-in-the-blanks exercise...') and a partially redundant anti-pattern table that duplicates the referenced honesty-protocol.md.

4 / 5

Actionability

Concrete guidance throughout — exact intake questions, output file paths, and copy-paste Moore/Onliness statement templates — but the per-agent research prompts are deferred to reference files, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

Clear sequence (Phase 0 → 1 → 1.5 → 2 → 3 → 3.5) with explicit validation checkpoints (Post-Research Checkpoint, PAUSE for user input, Onliness/Mental-Ladder tests with a 'revisit if it fails' feedback loop, and Phase 3.5 verification with critical/warning handling).

5 / 5

Progressive Disclosure

SKILL.md is an overview with a Reference Files table (file, when-to-read, line count, purpose) and per-phase '> Reference: Read ...' callouts; all 8 referenced files exist and are one level deep, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

100%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 third-person, specific, and explicitly separates capability ('what') from invocation triggers ('when'), with extensive natural-language trigger phrasing. It is a strong, low-conflict description that closely matches the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — 'positioning document, positioning statement, competitive alternatives map, and market category analysis' — plus named frameworks (Dunford, JTBD, Moore, Neumeier), giving comprehensive coverage of capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (produces the four named deliverables) and 'when' (an explicit 'Use when...' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and verbatim user phrasings: 'positioning', 'how to position', 'market position', 'how are we different', 'unique value proposition', and 'how should we position this product'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (startup market positioning) with distinct triggers and an explicit relationship to the sibling startup-design/startup-competitors skills, minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ferdinandobons/startup-skill
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.