product-marketing-context
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
86
83%
Does it follow best practices?
Impact
87%
3.48xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 with excellent trigger term coverage and clear completeness. The main weakness is the lack of specific concrete actions—it tells you it creates a context document but doesn't enumerate what specific information it captures (e.g., value propositions, competitive positioning, audience segments). The description effectively communicates when to use it and how it relates to other skills in the workflow.
Suggestions
Add 2-3 specific capabilities describing what information the context document captures (e.g., 'Captures product value propositions, target audience segments, competitive positioning, and key messaging pillars')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (product marketing context) and mentions creating/updating a context document, but lacks specific concrete actions beyond 'create or update.' Does not detail what information is captured or how it's structured. | 2 / 3 |
Completeness | Clearly answers both what (creates/updates product marketing context document at `.agents/product-marketing-context.md`) and when (explicit 'Use when' clause with multiple trigger scenarios, plus guidance to use at start of new projects before other marketing skills). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'product context,' 'marketing context,' 'positioning,' 'target audience,' 'describe my product,' 'ICP,' 'ideal customer profile.' These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific file path reference, clear niche (foundational context setup vs. execution skills), and explicit positioning as a prerequisite skill that other marketing skills reference. Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflow and validation checkpoints. Its main weakness is length—the comprehensive sections list and explanatory content could be trimmed or split into reference files. The skill effectively guides Claude through a complex information-gathering process with good decision branching.
Suggestions
Move the detailed 'Sections to Capture' content to a separate SECTIONS-REFERENCE.md file, keeping only a brief summary in the main skill
Remove explanatory phrases like 'exact phrases are more valuable than polished descriptions because...' - Claude understands why verbatim language matters
Condense the Tips section into the workflow steps where they apply rather than listing separately at the end
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what verbatim customer language is valuable for, explaining the Four Forces concept). The sections list is comprehensive but could be more condensed since Claude understands marketing frameworks. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths, exact document structure with markdown template, clear questions to ask, and a complete output format. The workflow steps are specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit checkpoints: check existing → gather info → create document → confirm and save. Includes decision branches (exists vs. doesn't exist, auto-draft vs. scratch) and validation steps (summarize and confirm each section, show completed document before saving). | 3 / 3 |
Progressive Disclosure | The skill is a single monolithic file with all 12 sections detailed inline. While well-organized with clear headers, the extensive sections list (Problems, Personas, Switching Dynamics, etc.) could be split into a separate reference file, keeping SKILL.md as a leaner overview. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
9d4d29a
- 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.