CtrlK
BlogDocsLog inGet started
Tessl Logo

launch-positioning-builder

Research competitors, analyze their messaging, and generate a positioning document with category definition, differentiation claims, value propositions, and proof points. Chains web research, competitor site analysis, and review mining to produce a positioning doc ready for website copy and sales deck use. Use when a product marketing team needs to define or refresh positioning ahead of a launch, rebrand, or competitive shift.

68

Quality

82%

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

65%

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 positioning workflow with concrete templates and tooling, held back by some redundancy and a monolithic single-file structure with no external references or explicit validation gates.

Suggestions

Remove the 'Trigger Phrases' section (it duplicates 'When to Use') and trim the intro line that restates the frontmatter description to improve conciseness.

Add explicit validation checkpoints between phases — e.g., 'Before drafting the doc, confirm every unique attribute in 2C maps to a proof point' — to lift workflow clarity.

Move the large Phase 4 output template into a reference file (e.g. references/positioning-template.md) and link to it from Phase 4 so the main SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient — the bulk is templates/tables, not prose about concepts Claude already knows — but the 'Trigger Phrases' section duplicates 'When to Use' and the intro restates the frontmatter description, so it could be tightened.

2 / 3

Actionability

Provides concrete, executable guidance: specific search strings ('Search: "[competitor name]" site:[competitor-url]'), named tools (web_search, fetch_webpage, review-site-scraper), extraction checklists, and a copy-paste-ready output template.

3 / 3

Workflow Clarity

The Phase 0→4 sequence is clear with decision criteria, but there are no explicit validation checkpoints (e.g., confirm each differentiator maps to a proof point before finalizing); checkpoints are implicit rather than gated.

2 / 3

Progressive Disclosure

Sections are well organized, but with no bundle files everything lives inline in a ~250-line SKILL.md, and the ~100-line output template is inline content that could be split into a one-level-deep reference.

2 / 3

Total

9

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities and gives an explicit, natural-voiced 'Use when' trigger. It is specific, complete, and clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'Research competitors, analyze their messaging, and generate a positioning document with category definition, differentiation claims, value propositions, and proof points' plus 'Chains web research, competitor site analysis, and review mining' — matching the anchor that lists several specific actions.

3 / 3

Completeness

Answers both 'what' (research competitors, analyze messaging, generate a positioning doc) and 'when' via an explicit 'Use when a product marketing team needs to define or refresh positioning ahead of a launch, rebrand, or competitive shift' clause.

3 / 3

Trigger Term Quality

Uses natural PMM vocabulary a buyer would actually say — 'positioning', 'competitors', 'messaging', 'launch, rebrand, or competitive shift' — giving good coverage of likely trigger terms.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear PMM niche with distinct triggers ('positioning doc', 'launch/rebrand/competitive shift') unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
gooseworks-ai/goose-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.