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.

Quality

76%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/product-marketing-context/SKILL.md

Quality

Content

62%

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 and workflow clarity—it provides a complete, well-sequenced process with a concrete output template and good validation checkpoints. However, it is significantly over-verbose, spending many tokens explaining marketing frameworks (JTBD Four Forces, competitive landscape categories, persona types) that Claude already knows. The content would benefit from being split into a concise SKILL.md overview and a separate reference file for the detailed section definitions and template.

Suggestions

Cut explanatory descriptions of marketing concepts Claude already knows (e.g., what JTBD Four Forces are, what direct vs. indirect competitors means) and reduce section descriptions to just the field names and any non-obvious guidance.

Extract the full markdown template and detailed section definitions into a separate reference file (e.g., TEMPLATE.md or SECTIONS.md) and reference it from the main SKILL.md to improve progressive disclosure.

Consolidate the 'Tips' section into the workflow steps where they apply rather than listing them separately at the end.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~200+ lines. Much of the content explains concepts Claude already understands (what competitive landscape categories are, what JTBD Four Forces are, what personas are). The detailed section descriptions and question prompts could be dramatically condensed. The full markdown template at the end is useful but the surrounding explanatory text is padded.	1 / 3
Actionability	The skill provides a clear, concrete workflow with specific steps, exact file paths, a complete markdown template that's copy-paste ready, and specific conversational guidance (e.g., exact questions to ask, what to look for in the codebase). The output format is fully specified.	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, show completed document before saving), and feedback loops (iterate until satisfied, ask what needs correcting).	3 / 3
Progressive Disclosure	The content is a monolithic document with no references to external files despite being long enough to benefit from splitting. The 12 detailed sections and the full template could be in a separate reference file, with the SKILL.md serving as a concise overview. However, the internal structure with clear headers is reasonable.	2 / 3
	Total	9 / 12 Passed

Description

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 describing what the context document contains, e.g., 'Captures target audience, value propositions, competitive positioning, and key messaging into a structured context file.'

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 content creation skills.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

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: ef5ffa0

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.