positioning-mapper

Use when the user asks to "map our positioning", "name our competitive alternatives", or "pick a beachhead segment for the launch"; produces a Dunford-style positioning canvas — named competitive alternatives (including spreadsheet and status quo), unique attributes (verifiable, or routed to the claims ledger), value themes (attribute→benefit→value chains), a target beachhead segment scored on serviceability / pain intensity / reachability, and a one-sentence onlyness statement — the sole upstream of the message house and the entity-signal source for the canonical entity profile. Not for the message house or per-channel launch copy — use message-house-builder; not for audience/persona profiling itself — use audience-mapper; not for SEO keyword positioning — use keyword-research. 定位画布/竞争替代品/独特价值/滩头细分

Quality

92%

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

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable multi-step workflow with clear validation feedback loops and clean one-level reference navigation. Its main weakness is conciseness: several handoffs and the registry-events phrasing are repeated many times and could be consolidated.

Suggestions

Consolidate the message-house-builder handoff — it is stated in the intro, scope guard, contract, step 8, Reference Materials, and Next Best Skill; keep it in the contract and Next Best Skill only.

Factor the recurring 'via an authorized operation: propose request to registry-events.py' phrasing (repeated 5+ times) into a single defined convention stated once and referenced thereafter.

Trim the Scope guard paragraph, since the frontmatter description's 'Not for... use X' exclusions already cover the same boundary.

Dimension	Reasoning	Score
Conciseness	The guidance is information-dense rather than padded with generic concepts, but it repeats itself: the message-house-builder handoff appears ~6 times and 'via an authorized operation: propose request to registry-events.py' is restated verbatim 5+ times, so it could be tightened.	2 / 3
Actionability	Concrete, copy-paste-ready templates and criteria are provided — the onlyness sentence '[Product] is the only [category frame] that [unique value] for [beachhead] [in this context]', the three beachhead scoring criteria, and the attribute→benefit→value chain structure — giving executable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	Eight numbered steps are clearly sequenced with explicit feedback loops — step 6 sends failure back to 'steps 2-4 and sharpen', step 5 stops and routes to audience-mapper when evidence is missing — plus a concrete 'Done when' checklist.	3 / 3
Progressive Disclosure	The body is an organized overview (Quick Start, Skill Contract, Data Sources, Instructions, Reference Materials, Next Best Skill) with one-level-deep, clearly signaled markdown links and a dedicated Reference Materials list; no deeply nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, trigger-rich, complete (what + when + exclusions), and strongly distinctive, with explicit conflict-avoidance routing to sibling skills. Voice is third person ('the user asks'), so no pronoun penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete outputs — 'named competitive alternatives (including spreadsheet and status quo)', 'unique attributes (verifiable, or routed to the claims ledger)', 'value themes (attribute→benefit→value chains)', 'a target beachhead segment scored on serviceability / pain intensity / reachability', and 'a one-sentence onlyness statement' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Clearly answers both what (the canvas and its components) and when ('Use when the user asks to...') with explicit triggers, plus explicit 'Not for...' exclusions, matching the top anchor.	3 / 3
Trigger Term Quality	Opens with quoted natural triggers users would say — '"map our positioning"', '"name our competitive alternatives"', '"pick a beachhead segment for the launch"' — giving good coverage of phrasings a user would actually utter in this domain.	3 / 3
Distinctiveness Conflict Risk	Explicit routing clauses — 'Not for the message house... use message-house-builder; not for audience/persona profiling... use audience-mapper; not for SEO keyword positioning... use keyword-research' — carve a clear niche and actively prevent mis-triggering.	3 / 3
	Total	12 / 12 Passed

Validation

75%

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

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 31 suspicious	Warning
referenced_paths_exist	Referenced path issues: 4 missing, 4 deeper-than-1-level	Warning

	Total	12 / 16 Passed

Repository: aaron-he-zhu/aaron-marketing-skills
Path: launch/research/positioning-mapper/SKILL.md
Commit: 4a77c48

Reviewed: 9 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.