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.

86

1.35x
Quality

77%

Does it follow best practices?

Impact

92%

1.35x

Average score across 6 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./marketing-skill/skills/marketing-strategy-pmm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is a well-structured, actionable marketing playbook with explicit workflow validation steps, checklists, and clean one-level-deep references to real bundle files. Its main weakness is verbosity and validation steps that read as success metrics rather than error-recovery feedback loops.

Suggestions

Tighten the 'Proactive Triggers', 'Communication', and 'Quick Reference' sections — drop editorial commentary like 'Without clear positioning, all marketing is guesswork' to reclaim tokens.

Convert the bolded '**Validation:**' success criteria into gated feedback loops (e.g. 'If win rate <30%, revise battlecards and re-check next month') to add error-recovery guidance.

Add one fully worked example per major template (e.g. a complete battlecard and a complete positioning statement) so the templates are copy-paste ready rather than placeholder-only.

DimensionReasoningScore

Conciseness

The body is template- and table-driven without explaining concepts Claude already knows, which is efficient, but at ~380 lines it is long and sections like 'Proactive Triggers' commentary and the 'Communication'/'Quick Reference' blocks could be tightened or trimmed without losing value.

3 / 5

Actionability

Provides concrete, fill-in-the-blank templates (positioning statement, battlecard, demo flow, sales deck structure) plus a worked value-proposition example, but many templates remain placeholder-only without fully worked examples, leaving minor gaps versus level 5.

4 / 5

Workflow Clarity

Each major workflow is a numbered 1–8 sequence ending in an explicit bolded '**Validation:**' checkpoint, supplemented by checklists (ICP, Launch Day, Localization); however the validation steps are success-criteria rather than validate→fix→retry gating loops, leaving minor validation gaps versus level 5.

4 / 5

Progressive Disclosure

A Table of Contents plus a dedicated 'Reference Documentation' section clearly signals four one-level-deep reference files (positioning-frameworks.md, launch-checklists.md, international-gtm.md, messaging-templates.md), all of which exist in ./references/, with core workflows kept inline and deeper material split out — easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

83%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.

The description is strong: it explicitly states what the skill does, when to use it via concrete trigger phrases, and what deliverables it produces. Minor gaps are abstract category names in the capability list and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('positioning, GTM strategy, competitive intelligence, and product launches') and concrete deliverables ('positioning statements, battlecard documents, launch plans, and go-to-market strategies'), but several items are category names rather than fully concrete actions, so it stops short of level 5.

4 / 5

Completeness

Clearly answers 'what' ('Product marketing skill for...') and 'when' ('Use when the user asks about...') with concrete trigger phrases and an explicit deliverables list, matching the level-5 anchor pattern.

5 / 5

Trigger Term Quality

Explicit 'Use when' clause enumerates natural user phrases ('product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement'), giving good keyword coverage, but a few common synonyms/variants (e.g. 'win loss analysis', 'competitor repositioning') that appear in the triggers list are absent from the description.

4 / 5

Distinctiveness Conflict Risk

The 'product marketing / PMM' niche is distinct with specific triggers, but terms like 'sales enablement' and 'market research' overlap with adjacent marketing skills (the body itself lists launch-strategy, competitive-intel, and cmo-advisor as related), so minor overlap risk remains.

4 / 5

Total

17

/

20

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.

Validation — 15 / 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
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.