CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

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

73%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 tightly constructed orchestration skill: the 8-step workflow has genuine validation gates (onlyness test, Done-when checklist, termination rules) and the guidance is unusually concrete for an instruction-only skill. The main costs are token-level repetition of the registry-events propose clause and cross-skill links, and dependence on external files for the output templates that are not bundled here.

Suggestions

State the registry-events.py 'operation: propose' submission procedure once (e.g., in Skill Contract) and refer back to it, instead of repeating the full clause in the scope guard, Reads/Writes, and steps 1, 3, and Save Results.

Trim the duplicated cross-skill links: keep each sibling skill link in Reference Materials / Next Best Skill and remove the repeated inline mentions of message-house-builder and audience-mapper in the intro, scope guard, and step 8.

Inline a compact canvas skeleton (section headings plus the beachhead scoring table columns) or the save-results template, so the output format is concrete without requiring the external skill-contract.md reference.

DimensionReasoningScore

Conciseness

The 8-step instructions are terse and imperative with no explanation of concepts Claude already knows, but the phrase 'via an authorized `operation: propose` request to `registry-events.py`' is repeated 5-6 times, the message-house-builder link appears in five sections, audience-mapper in four, and the 'Label every data point Measured / User-provided / Estimated' instruction three times. This is more than minor trimming, matching the 'mostly efficient but could be tightened' anchor rather than anchor 4's 'minor instances'.

3 / 5

Actionability

The body gives a copy-paste onlyness sentence template, three named beachhead scoring criteria with definitions, exact save paths, and named connector/registry scripts. It falls short of fully executable because the canvas document shape and the save/handoff templates are delegated to external files (skill-contract.md) that are not part of this bundle, leaving the output format described rather than concretely templated.

4 / 5

Workflow Clarity

Eight numbered steps are clearly sequenced with an explicit feedback loop ('If a named alternative can honestly claim the same sentence, return to steps 2-4 and sharpen; do not resolve the failure by softening the wording'), a routing stop when persona evidence is missing, a 'Done when' checklist with three concrete criteria, and explicit termination rules (visited-set, max-depth 3, ambiguity stop). This matches the anchor for clear sequence with explicit validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

Sections are well organized (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with an annotated one-level-deep reference index, and methodology detail is appropriately kept in the body. However, no bundle files exist (references/, scripts/, assets/ are absent) so referenced formats cannot be resolved from the skill itself, and the same links are repeated both inline and in the index — minor organization gaps consistent with anchor 4 rather than the fully self-evident navigation of anchor 5.

4 / 5

Total

16

/

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.

An exemplary description: third-person voice, explicit quoted trigger phrases, a fully enumerated concrete output, and explicit disambiguation against three sibling skills. The only quibble is the trailing bilingual keyword string, which duplicates the summary but serves CJK trigger matching rather than being pure padding.

DimensionReasoningScore

Specificity

The description enumerates the complete output concretely: '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'. This is multiple specific concrete actions with comprehensive coverage (anchor 5), not anchor 4, since no output component is missing.

5 / 5

Completeness

Both halves are explicit: 'Use when the user asks to…' gives concrete trigger phrases for when, and 'produces a Dunford-style positioning canvas — …' fully answers what. This exactly matches anchor 5 (clear and explicit what AND when with concrete trigger phrases); it is above anchor 4 because the 'when' is not merely present but spelled out in quoted user language.

5 / 5

Trigger Term Quality

It quotes natural user phrasings ('"map our positioning", "name our competitive alternatives", or "pick a beachhead segment for the launch"') and adds synonym coverage in a second language (定位画布/竞争替代品/独特价值/滩头细分). Coverage of natural terms including synonyms matches anchor 5; anchor 4's 'a few natural terms missing' does not apply given the quoted phrasings plus bilingual synonyms.

5 / 5

Distinctiveness Conflict Risk

The niche is distinct (launch positioning canvas) and the description adds explicit negative boundaries routing adjacent intents elsewhere: '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'. Clear niche with distinct triggers and minimal conflict risk — anchor 5.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

CriteriaDescriptionResult

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

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.