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.
77
72%
Does it follow best practices?
Impact
Pending
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 is highly actionable with a clear, well-sequenced workflow including validation checkpoints and branching logic. However, it is excessively verbose—the 12 detailed sections, full markdown template, and conversational tips all inline create a massive document that wastes context window. The content would benefit enormously from splitting the template and section definitions into referenced files.
Suggestions
Move the full markdown template to a separate file (e.g., `product-marketing-context-template.md`) and reference it from SKILL.md
Move the detailed 12-section definitions to a separate reference file, keeping only a brief list of section names in SKILL.md
Remove tips that teach Claude things it already knows (e.g., 'Ask for examples unlocks better answers', 'Be specific') — these waste tokens on basic conversational skills
Condense the competitive landscape categories and switching dynamics explanations — Claude already understands JTBD frameworks and competitive analysis concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. It explains conversational techniques Claude already knows ('Ask for examples unlocks better answers'), describes basic concepts like competitive landscape categories at length, and includes extensive section-by-section detail that could be condensed significantly. The full markdown template alone is massive and could be a referenced file. | 1 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific file paths, exact document structure with a complete markdown template, clear step-by-step workflows for both auto-draft and from-scratch paths, and specific questions to ask for each section. | 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 accuracy per section, show completed document, ask for adjustments before saving), and iteration loops. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. The complete markdown template, all 12 section definitions with their sub-questions, and the workflow instructions are all inline. The template and section details should be in separate referenced files, keeping SKILL.md as a concise overview. | 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 | |
2c6f6e8
Table of Contents
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.