competitive-research-snapshot

Research a competitive landscape with cited snapshots, a comparison matrix, and so-what implications. Use when a product decision needs competitive grounding, not a market report.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered workflow skill: dense, actionable, with a clear sequenced process and validation checkpoints. Its only real defect is progressive disclosure — the body points to bundle files (template.md, examples/*) that are not actually present.

Suggestions

Bundle the referenced files so links resolve: add template.md (the fill-in schema with quality checks) and examples/sample.md and examples/sample-industrial.md, or remove the dangling references.

If the example snapshots are kept inline only, move the 'Evidence quality row doing its job' worked illustration into examples/sample.md to keep the main body focused on the schema and discipline.

Confirm the cross-skill references (e.g. ../autonomous-investigation/SKILL.md, ../competitive-intel-watch/SKILL.md) resolve in the deployed plugin layout, since broken sibling links would undermine the same navigation pattern.

Dimension	Reasoning	Score
Conciseness	Every section earns its place with domain-specific discipline and assumes Claude's competence; it never explains concepts Claude already knows (unlike the bad PDF-formatting example), so it sits at the lean/efficient anchor rather than the could-be-tightened anchor at 2.	3 / 3
Actionability	Concrete, copy-paste-ready guidance: numbered Application steps, an exact 'do not reorder' output schema, and a Final Step with four options plus accepted inputs ('1', '2', 'Verbose Mode') — fully executable for an instruction skill.	3 / 3
Workflow Clarity	A clear search-plan -> selection -> research -> emit-schema -> final-step sequence with explicit checkpoints (search-plan gate, proceed on labeled assumptions, a 'validate the assumptions' option), matching the explicit-validation anchor rather than the checkpoint-gap anchor at 2.	3 / 3
Progressive Disclosure	References are well-signaled and one level deep (template.md, examples/sample.md, examples/sample-industrial.md), but those files are absent from the bundle, so the disclosure is incompletely realized and cannot reach the fully-resolved anchor at 3.	2 / 3
	Total	11 / 12 Passed

Description

100%

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

A strong description: third-person, concrete outputs, an explicit 'Use when' trigger, and a negative discriminator that sets it apart from generic market reporting. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions/outputs — 'cited snapshots, a comparison matrix, and so-what implications' — matching the anchor for multiple specific concrete actions rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers what ('Research a competitive landscape with cited snapshots...') and when ('Use when a product decision needs competitive grounding'), satisfying the both-what-and-when anchor at 3 rather than the implied-when anchor at 2.	3 / 3
Trigger Term Quality	'competitive landscape', 'competitive grounding', and 'product decision' are natural terms a user would say, and 'not a market report' sharpens triggering; coverage exceeds the single-keyword anchor at 2.	3 / 3
Distinctiveness Conflict Risk	A clear niche (cited competitive snapshots for product decisions) explicitly distinguished from a 'market report', giving distinct triggers unlikely to conflict with adjacent skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing, 14 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/competitive-research-snapshot/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.