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
Quality
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-crafted description that excels at trigger term coverage and completeness, clearly stating when to use the skill and what it produces. The main weakness is limited specificity about concrete actions beyond creating/updating the document - it could benefit from listing what the context document contains or what actions are involved in creating it.
Suggestions
Add 2-3 specific actions describing what the skill does when creating the context document (e.g., 'Captures target audience, value propositions, competitive positioning, and brand voice guidelines')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (product marketing context) and one specific action (creates `.claude/product-marketing-context.md`), but doesn't list multiple concrete actions beyond 'create or update' the document. | 2 / 3 |
Completeness | Clearly answers both what (creates/updates product marketing context document at specific path) and when (explicit 'Use when' equivalent at the start plus quoted trigger terms and use case scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'product context,' 'marketing context,' 'set up context,' 'positioning,' and the use case of avoiding repeated foundational information. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - focuses on a particular file (`.claude/product-marketing-context.md`) for marketing context setup, with distinct triggers like 'positioning' and 'foundational information.' 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, actionable skill with clear workflow and validation steps. Its main weakness is length—the detailed 12-section framework makes it verbose when Claude already understands marketing concepts. The content would benefit from splitting the section definitions into a separate reference file.
Suggestions
Move the detailed 'Sections to Capture' content to a separate SECTIONS.md file, keeping only a brief list in the main skill
Remove explanatory phrases like 'This captures foundational positioning and messaging information' that explain concepts Claude already knows
Condense the Tips section—these are behaviors Claude would naturally exhibit when gathering information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what each section captures, tips that Claude would naturally follow). The 12-section framework is comprehensive but could be more condensed given Claude's understanding of marketing concepts. | 2 / 3 |
Actionability | Provides concrete, executable guidance with a complete markdown template, specific questions to ask, exact file path, and clear output format. The workflow steps are specific and the document structure is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow with explicit decision points (exists vs. doesn't exist, auto-draft vs. scratch), validation steps (confirm accuracy, ask what needs correcting), and a feedback loop (iterate until satisfied). Each step has clear sequencing. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic at ~200 lines. The 12 detailed sections could be split into a separate reference file, with SKILL.md containing just the workflow and pointing to a SECTIONS.md for the detailed capture framework. | 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
355d067
- 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.