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,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/product-marketing-context/SKILL.mdQuality
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 well-constructed description with excellent trigger terms and completeness, clearly stating both what the skill does and when to use it. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., what information is gathered, what structure the document follows). Overall it would perform well in a multi-skill selection scenario.
Suggestions
Add specific concrete actions like 'Gathers product name, target audience, value propositions, competitive positioning, and tone guidelines' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (product marketing context) and mentions creating/updating a specific file (`.claude/product-marketing-context.md`), but doesn't list the concrete actions or content involved—e.g., what fields are captured, what structure is produced, or what information is gathered. | 2 / 3 |
Completeness | Clearly answers both 'what' (creates/updates `.claude/product-marketing-context.md` that other marketing skills reference) and 'when' (explicit 'Use when' triggers including specific phrases and the scenario of avoiding repeated foundational info). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'product context,' 'marketing context,' 'set up context,' 'positioning,' and 'foundational information across marketing tasks.' These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—targets a very specific niche of creating a product marketing context document at a specific file path, with clear trigger terms that distinguish it from general marketing or copywriting skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with a concrete output template and clear workflow sequencing with validation steps. However, it is far too verbose—explaining marketing concepts Claude already knows, inlining a massive template, and providing basic interviewing tips. The content would benefit enormously from splitting the detailed section definitions and output template into separate referenced files.
Suggestions
Move the 12 'Sections to Capture' definitions into a separate reference file (e.g., SECTIONS.md) and link to it, keeping only a brief list of section names in the main skill.
Move the full markdown output template into a separate TEMPLATE.md file and reference it, reducing the main skill by ~60 lines.
Remove the 'Tips' section entirely—Claude already knows how to ask specific questions, capture verbatim language, and validate as it goes.
Cut explanatory phrases like 'what "shelf" you sit on—how customers search for you' and 'The JTBD Four Forces'—Claude knows these concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. Much of the content explains concepts Claude already understands (what competitive landscape means, what JTBD Four Forces are, what B2B personas are). The sections listing could be a compact template rather than lengthy explanations. The tips section tells Claude basic interviewing techniques it already knows. | 1 / 3 |
Actionability | The skill provides a fully concrete, copy-paste-ready markdown template for the output document, clear file paths (.claude/product-marketing-context.md), specific questions to ask, and explicit steps for both auto-draft and from-scratch workflows. Claude knows exactly what to produce. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (check existing → gather info → create document → confirm and save) with explicit branching logic (exists vs. doesn't exist, auto-draft vs. scratch), validation checkpoints (confirm each section, review draft, ask for adjustments before saving), and a feedback loop for iteration. | 3 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files. The 12 detailed sections and the full output template are all inline, making this extremely long. The sections-to-capture details and the full markdown template could easily be split into referenced files to keep the main skill lean. | 1 / 3 |
Total | 8 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
3974caa
- 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.