press-release

Write an Amazon-style press release that defines customer value before building. Use when aligning stakeholders on a new product, feature, or strategic bet.

Quality

68%

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/press-release/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 delivers a well-sequenced, verifiable drafting workflow with concrete per-step templates and quality checks. Its main weaknesses are verbosity (repeated intent and general writing advice) and progressive-disclosure references to template.md and examples/sample.md that are not present in the bundle.

Suggestions

Add the referenced bundle files (template.md and examples/sample.md) or inline their full content so the progressive-disclosure pointers resolve to real artifacts.

Trim the repeated intent (the body restates the frontmatter description) and condense the 'Why This Works' / 'When to Use' sections to assume Claude's competence.

Move the five detailed pitfall breakdowns into a single concise checklist to reduce token weight while keeping the actionable fixes.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured but repeats the frontmatter intent nearly verbatim (lines 5-6 vs 12) and includes long 'Why This Works,' 'When to Use,' and five detailed pitfall breakdowns that restate general writing advice Claude already knows.	2 / 3
Actionability	Provides concrete fill-in templates per step, headline formats, and quality checks with examples, but the full template and complete example it points to ("Use template.md," "See examples/sample.md") live in files that are absent from the bundle, leaving a gap in copy-paste-ready guidance.	2 / 3
Workflow Clarity	Presents a clear nine-step sequence from context gathering through drafting to Step 9's test checklist, with an explicit feedback loop ("If any answer is 'no,' revise").	3 / 3
Progressive Disclosure	The body signals one-level-deep references ("Use template.md for the full fill-in structure," "See examples/sample.md for full press release examples") but those files do not exist in the bundle, so the full template and examples are inlined or missing rather than appropriately split and navigable.	2 / 3
	Total	9 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description cleanly answers both what the skill does and when to use it, with a distinctive Amazon Working Backwards niche and proper third-person voice. It is slightly held back by naming only one concrete action and by trigger terms that omit the most common phrasings users would say.

Suggestions

Add one or two more concrete actions (e.g., "draft, refine, and test a press release") to move specificity toward a list of specific actions.

Expand the 'Use when' clause to include the terms users actually say, such as "writing a press release," "Working Backwards," or "product vision / value proposition."

Dimension	Reasoning	Score
Specificity	States a concrete action and domain ("Write an Amazon-style press release that defines customer value before building") but lists a single primary action rather than multiple specific concrete actions, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	Explicitly answers both what ("Write an Amazon-style press release that defines customer value before building") and when ("Use when aligning stakeholders on a new product, feature, or strategic bet") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes relevant natural terms ("product, feature, or strategic bet") but misses common variations a user would actually say ("press release," "working backwards," "product vision"), fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The "Amazon-style press release" framing plus "defines customer value before building" carves a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/press-release/SKILL.md
Commit: 9971018

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.