product-marketing-context

Create or update a reusable product marketing context document with positioning, audience, ICP, use cases, and messaging. Use at the start of a project to avoid repeating core marketing context across tasks.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/product-marketing-context/SKILL.md

Quality

Content

63%Scale 1-5

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 instructional skill with a clear workflow and concrete output template. Its main weakness is length — the 12 detailed sections and full markdown template make it verbose for a single file, and some explanatory content (e.g., why verbatim language matters, what the Four Forces are) could be trimmed since Claude already knows these concepts. The workflow is solid with good branching logic and a confirmation step.

Suggestions

Extract the full markdown template and/or the 12 sections-to-capture into a separate reference file to reduce SKILL.md length and improve progressive disclosure.

Trim explanatory asides that Claude already knows — e.g., remove 'exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak' and similar justifications.

Remove or condense the Tips section, as Claude already knows how to ask good follow-up questions and validate information.

Dimension	Reasoning	Score
Conciseness	The skill is fairly long (~200+ lines) and includes some explanatory content that Claude doesn't need (e.g., explaining what JTBD Four Forces are, explaining why verbatim customer language matters). The sections-to-capture list is thorough but could be more compact. The tips section at the end tells Claude how to ask good questions, which is somewhat redundant for Claude's capabilities.	3 / 5
Actionability	The skill provides a concrete workflow with clear steps, a complete markdown template for the output document, and specific file paths. It gives actionable guidance on what to check in the codebase and how to structure conversations. Minor gap: no executable code, but this is an instruction-only skill where that's appropriate. The two-option approach (auto-draft vs scratch) is well-defined.	4 / 5
Workflow Clarity	The workflow has clear sequencing (check existing → gather info → create document → confirm and save) with branching logic for existing vs new contexts and auto-draft vs scratch approaches. There's a validation checkpoint at Step 4 (confirm and save). Minor gap: no explicit validation that the generated markdown is well-formed or that all sections are populated, though the 'show and confirm' step partially addresses this.	4 / 5
Progressive Disclosure	The content is entirely self-contained in one file with no bundle files. The 12 sections to capture plus the full output template make this quite long. The sections-to-capture detail and the full markdown template could reasonably be split into a referenced template file, keeping the SKILL.md as a workflow overview. As-is, it's a somewhat monolithic document, though it does use headers and structure well.	3 / 5
	Total	14 / 20 Passed

Description

83%Scale 1-5

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 skill description that clearly communicates both what the skill does and when to use it. It lists specific marketing elements (positioning, audience, ICP, use cases, messaging) and provides a clear trigger condition ('at the start of a project'). Minor improvements could include additional synonym coverage for trigger terms and slightly more detail on the output format.

Dimension	Reasoning	Score
Specificity	Lists several specific elements: positioning, audience, ICP, use cases, and messaging. Also specifies the concrete actions of 'create or update' a context document. Minor gaps in that it doesn't elaborate on what each element entails, but coverage is good.	4 / 5
Completeness	Clearly answers both 'what' (create or update a reusable product marketing context document with positioning, audience, ICP, use cases, and messaging) and 'when' (at the start of a project to avoid repeating core marketing context across tasks). Both are explicit and concrete.	5 / 5
Trigger Term Quality	Includes strong natural keywords like 'product marketing', 'positioning', 'audience', 'ICP', 'use cases', 'messaging', and 'context document'. Missing some synonyms like 'buyer persona', 'value proposition', 'target market', or 'brand messaging' that users might naturally say.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct with its focus on a reusable marketing context document specifically for product marketing. The 'start of a project' framing and the specific deliverable (context document) help distinguish it, though there could be minor overlap with general marketing strategy or messaging skills.	4 / 5
	Total	17 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/product-marketing-context/SKILL.md
Commit: 57c135b

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.