CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

positioning-icp

When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit. Also use when the user mentions 'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer persona,' 'enrichment signals,' 'market positioning,' or 'competitive positioning.' This skill covers market positioning, ICP definition, messaging architecture, and PMF validation for AI-native products. Do NOT use for technical implementation, code review, or software architecture.

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

77%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 highly actionable, well-sequenced GTM playbook with concrete formulas, thresholds, and validation checkpoints. Its main weakness is structure: the body is long and self-duplicating, while the single reference file mirrors the body instead of carrying the detailed tables off the main context.

Suggestions

Move the stable detail tables (pricing trends, competitor-type strategies, enrichment waterfall, buyer-shift comparisons) into references/ and keep SKILL.md to the workflows, templates, and decision rules — the body currently carries ~470 lines.

De-duplicate the quick-reference: every key number in references/quick-reference.md (90-day cadence, 40% Sean Ellis, 0.85/0.50 thresholds, score weights) already appears in the body — have one location own each fact.

Isolate the time-sensitive 2025-2026 market statistics into a dated reference section so stale numbers can be updated without re-reading the whole skill.

DimensionReasoningScore

Conciseness

Mostly efficient domain content (formulas, thresholds, tables earn their place), but the ~470-line body has notable padding: three large ASCII diagrams, benchmark tables whose key numbers are duplicated verbatim in references/quick-reference.md, and time-sensitive 2025-2026 trend stats ("dropped from 21% to 15%", "surged from 27% to 41%") placed inline rather than in a dated reference section. Not clearly below the midpoint — anchor 3 fits best.

3 / 5

Actionability

Fully executable for an instruction-only skill: a fill-in positioning statement template, explicit Fit/Intent score formulas with component weights and point breakdowns, confidence-threshold decision tables, a landing-page structure, a 5-check messaging validation with pass/fail criteria, and a week-by-week checklist. Examples and Troubleshooting sections give concrete input→output and cause→fix pairs.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (ICP Definition Workflow, 10-step Dunford process, 6-week Implementation Playbook, 90-day revalidation cadence) with explicit validation checkpoints: "Test against your pipeline to see if the model would have predicted your last 10 wins," "Test messaging with 5 prospects," and the five-check validation run on every message. The Troubleshooting section supplies error-recovery cause/fix pairs. No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

One real reference file exists and is signaled ("read `references/quick-reference.md`"), but it largely duplicates numbers already inline in the body rather than offloading detail. The bulk of the material — pricing-trend tables, competitor-type matrices, enrichment waterfall diagram — sits inline in the ~470-line SKILL.md where anchor 3's "content that should be separate is inline" applies; structure exists but the split is underused.

3 / 5

Total

16

/

20

Passed

Description

91%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 strong description: explicit what/when structure, abundant natural synonyms, third-person voice, and an exclusion clause. Its only weaknesses are a redundant mid-sentence restatement and the slightly over-broad trigger "messaging."

Suggestions

Drop the restatement sentence ("This skill covers market positioning, ICP definition...") — it repeats the opening clause in vaguer language and adds tokens without new triggers.

Qualify the bare trigger "messaging" (e.g., "messaging architecture" or "product messaging") to avoid firing on chat/messaging-app or message-queue requests.

DimensionReasoningScore

Specificity

Names several concrete actions — "define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit" — with a domain scope ("for AI-native products"). The middle sentence "This skill covers market positioning, ICP definition..." partially restates the actions in vaguer "covers" language, keeping it just below the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ("covers market positioning, ICP definition, messaging architecture, and PMF validation for AI-native products") and when ("When the user wants to... Also use when the user mentions...") with concrete trigger phrases, plus an explicit exclusion ("Do NOT use for technical implementation, code review, or software architecture").

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms with synonyms: "'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer persona,' 'enrichment signals,' 'market positioning,' 'competitive positioning'" — these are exactly the phrases a user working on GTM would say, with both acronym and expanded forms.

5 / 5

Distinctiveness Conflict Risk

Clear GTM/positioning niche with distinct triggers and an explicit "Do NOT use" boundary. Minor overlap risk remains: the bare keyword "messaging" could fire for unrelated contexts (chat/messaging apps, message queues), and neighboring skills like ai-pricing or sales-motion-design cover adjacent trigger territory.

4 / 5

Total

18

/

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

tech-leads-club/agent-skills

Path

packages/skills-catalog/skills/(gtm)/positioning-icp/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.