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.
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 well-constructed description with excellent trigger terms and clear 'when to use' guidance. Its main weakness is that it could be more specific about what concrete actions or content the skill produces beyond just creating/updating the context file. Overall it performs strongly on completeness and distinctiveness.
Suggestions
Add specific concrete actions describing what the context document contains, e.g., 'Captures target audience, value propositions, competitive positioning, and brand voice guidelines into a structured context document.'
| 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
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 a clear multi-step workflow and good validation checkpoints. Its main weakness is length—the 12 detailed sections and full markdown template make it a large context window consumer, and some explanatory content (competitor type definitions, JTBD framework explanation) could be trimmed since Claude knows these concepts. The monolithic structure would benefit from splitting the template or section definitions into a referenced file.
Suggestions
Move the full markdown template (Step 3) into a separate reference file like `.claude/templates/product-marketing-context-template.md` and reference it from the main skill
Trim explanatory parentheticals that Claude already knows, such as '(what "shelf" you sit on—how customers search for you)' and the competitor type examples like '(e.g., Calendly vs SavvyCal)'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~200 lines) with some sections that could be tightened. The 12 sections to capture are thorough but verbose—many subsections explain concepts Claude already understands (e.g., explaining what direct vs secondary vs indirect competitors mean with examples). The tips section at the end restates good practices Claude would naturally follow. However, most content is structural/template rather than explanatory padding. | 2 / 3 |
Actionability | The skill provides a fully concrete workflow: check for existing file, two clear paths (auto-draft vs scratch), specific questions to ask per section, and a complete markdown template to output. The document template is copy-paste ready with exact field names and table structures. Claude knows exactly what to produce. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 1-4) with explicit branching logic (exists vs doesn't exist, auto-draft vs scratch). Each step has clear validation checkpoints—confirm accuracy per section, show completed document, ask for adjustments before saving. The iterative 'present draft → ask what needs correcting → iterate' loop is a good feedback mechanism. | 3 / 3 |
Progressive Disclosure | The content is entirely monolithic—all 12 sections with their details, the full template, and the workflow are in a single file. The template alone is ~80 lines that could be in a separate reference file. For a skill this long, splitting the section definitions or template into a referenced file would improve scannability. However, the internal structure with clear headers is decent. | 2 / 3 |
Total | 10 / 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
05d40bb
- 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.