marketing-strategy-pmm
Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-skills --skill marketing-strategy-pmm68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 an excellent skill description that hits all the marks. It provides specific methodologies and deliverables (April Dunford, battlecards, launch playbooks), comprehensive trigger terms including abbreviations, and a clear 'Use when...' clause. The description is well-structured, uses third person voice, and carves out a distinct niche in product marketing that won't conflict with adjacent skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and methodologies: 'ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides' - these are concrete, named deliverables and frameworks. | 3 / 3 |
Completeness | Clearly answers both what (positioning, GTM strategy, competitive intelligence, ICP definition, etc.) AND when with explicit 'Use when...' clause listing specific trigger scenarios and terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, sales enablement, product launches, messaging, competitors' - includes both full terms and common abbreviations like GTM. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche in product marketing with distinct triggers like 'April Dunford positioning methodology', 'competitive battlecards', 'ICP definition' that are unlikely to conflict with general marketing or sales skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive but severely over-engineered for Claude's context window. It explains basic marketing concepts Claude already understands, includes extensive boilerplate templates, and fails to leverage progressive disclosure by keeping most content inline. The actionability is moderate with useful checklists but lacks executable specificity.
Suggestions
Reduce content by 70-80% by removing explanations of basic concepts (ICP, PLG, positioning) and keeping only project-specific configurations and non-obvious guidance
Move detailed templates (battlecard template, sales deck structure, launch checklists) to separate reference files and link to them
Add validation checkpoints to critical workflows like market entry and positioning development (e.g., 'Validate positioning with 5 customer interviews before proceeding')
Replace generic framework descriptions with specific, executable examples tailored to the company's actual products and markets
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 800+ lines with extensive explanations of concepts Claude already knows (what PLG is, what ICP means, basic marketing frameworks). Contains massive amounts of template content and boilerplate that could be condensed significantly. | 1 / 3 |
Actionability | Provides some concrete templates and checklists (battlecard template, launch playbook), but much content is generic guidance rather than executable instructions. Code examples exist but are minimal; most content is descriptive frameworks rather than copy-paste ready actions. | 2 / 3 |
Workflow Clarity | Multi-step processes like the 90-day launch playbook have clear sequences, but validation checkpoints are largely missing. No explicit feedback loops for error recovery in critical processes like market entry or positioning development. | 2 / 3 |
Progressive Disclosure | References external files (references/, scripts/, assets/) appropriately, but the main document is a monolithic wall of text that should have much more content split into separate files. The 800+ line body defeats the purpose of progressive disclosure. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1164 lines); consider splitting into references/ and linking | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 14 / 16 Passed | |
- 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.