CtrlK
BlogDocsLog inGet started
Tessl Logo

marketing-strategy-pmm

Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Use when the user asks about product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry. Produces deliverables including positioning statements, battlecard documents, launch plans, and go-to-market strategies.

88

1.35x
Quality

81%

Does it follow best practices?

Impact

92%

1.35x

Average score across 6 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Discovery

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.

This is a strong skill description that clearly defines its domain (product marketing), lists specific capabilities and deliverables, and includes an explicit 'Use when...' clause with comprehensive trigger terms. The description is well-structured, uses third person voice throughout, and covers both common user language and domain-specific terminology like 'April Dunford positioning' and 'battlecards' that help distinguish it from generic marketing skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and deliverables: positioning, GTM strategy, competitive intelligence, product launches, battlecards, launch playbooks, international market entry, positioning statements, and go-to-market strategies.

3 / 3

Completeness

Clearly answers both 'what' (positioning, GTM strategy, competitive intelligence, product launches, deliverables) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like product positioning, go-to-market planning, competitive analysis, etc.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'product positioning', 'go-to-market', 'competitive analysis', 'target audience', 'ICP', 'market research', 'launch plans', 'sales enablement', 'battlecards'. These are terms practitioners naturally use.

3 / 3

Distinctiveness Conflict Risk

Clearly carved out niche in product marketing with distinct triggers like 'April Dunford positioning', 'competitive battlecards', 'ICP definition', and 'launch playbooks' that are unlikely to conflict with general marketing or other skills.

3 / 3

Total

12

/

12

Passed

Implementation

62%

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

This is a comprehensive product marketing skill with strong workflow clarity—each section has numbered steps and explicit validation criteria. However, it suffers from being too long for a SKILL.md overview, inlining detailed templates and frameworks that Claude likely already knows (positioning statements, sales deck structures, demo flows) rather than focusing on the unique patterns and decisions specific to this skill. The content would benefit from moving detailed templates to reference files and keeping the main file as a concise orchestration guide.

Suggestions

Move detailed templates (battlecard template, sales deck structure, demo flow, firmographics template) into the referenced files and keep only brief summaries with links in the main SKILL.md

Add at least one complete worked example showing a finished positioning statement or battlecard with real (fictional) data, rather than only bracket-placeholder templates

Trim generic marketing knowledge Claude already knows (e.g., what firmographics are, basic sales deck slide ordering) and focus on the specific decision logic and patterns unique to this skill

DimensionReasoningScore

Conciseness

The skill is reasonably structured but includes substantial content that could be more concise. Many tables and templates are useful but some sections (like the full battlecard template, demo flow, and sales deck structure) contain generic marketing knowledge Claude already possesses. The document is quite long (~300+ lines) with content that could be split into reference files.

2 / 3

Actionability

The skill provides structured templates, checklists, and numbered workflows which give concrete guidance. However, it lacks executable code or commands—everything is conceptual marketing frameworks with placeholder brackets like '[Competitor A, B]' and '[Your advantage + evidence]'. The templates are fill-in-the-blank rather than truly copy-paste ready with real examples showing completed output.

2 / 3

Workflow Clarity

Each major section follows a clear numbered sequence with explicit validation checkpoints at the end (e.g., '7+ customers describe value unprompted', 'Sales team uses battlecards in 80%+ competitive deals', '3+ paying customers from market in first 90 days'). The ICP workflow, positioning development, and launch planning all have well-defined steps with measurable success criteria.

3 / 3

Progressive Disclosure

The skill has a table of contents and references four external files (references/positioning-frameworks.md, etc.), which is good progressive disclosure structure. However, the main file itself is very long with substantial inline content that could be moved to those reference files. The battlecard template, sales deck structure, and demo flow would be better as referenced materials rather than inline content.

2 / 3

Total

9

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
alirezarezvani/claude-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.