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

80%

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

77%Weight 40%Scale 1-5

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

A well-structured, actionable workflow skill with clear sequencing and built-in validation discipline; its main defect is three dangling references to bundle files (template.md, examples/) that are absent from the package.

Suggestions

Add the missing bundle files (template.md, examples/sample.md, examples/sample-industrial.md) referenced in the body, or remove/soften the references so navigation links resolve.

Consolidate the repeated 'snapshot as baseline / diff against prior run' point into one location (Purpose or Key Concepts) to tighten conciseness.

Consider moving the full output schema into template.md and keeping only a compact summary inline, so progressive disclosure is consistent with the referenced file structure.

Dimension	Reasoning	Score
Conciseness	Dense and substantive with no padding of concepts Claude already knows; every section earns its place, though the baseline/diff idea is restated across Purpose, Key Concepts, and Common Pitfalls and could be tightened.	4 / 5
Actionability	Provides a concrete 5-step procedure, a copy-paste output schema, a fully labeled example snapshot, and exact accepted final-step inputs, but references template.md and examples/sample.md that are not present in the bundle.	4 / 5
Workflow Clarity	A clearly sequenced 5-step workflow with explicit gates (≤3-question budget, search-plan gate, proceed-on-assumptions) and Fact/Inference/Assumption labels plus the Evidence-quality row acting as validation checkpoints and a feedback loop for weak evidence.	5 / 5
Progressive Disclosure	Section headers and inline one-level-deep sibling-skill references are well organized, but the body cites template.md, examples/sample.md, and examples/sample-industrial.md that do not exist in the bundle, breaking navigation.	3 / 5
	Total	16 / 20 Passed

Description

83%Weight 40%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.

A strong, well-targeted description that explicitly pairs what-it-does with a concrete when-to-use trigger and a negative boundary that reduces conflict. Minor room to add common synonyms (competitor analysis, benchmarking) and tighten action framing.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete deliverables — 'cited snapshots', 'a comparison matrix', and 'so-what implications' — giving specific, comprehensive output coverage, though framed as deliverables rather than executable file actions.	4 / 5
Completeness	Explicitly answers both what ('Research a competitive landscape with cited snapshots, a comparison matrix, and so-what implications') and when ('Use when a product decision needs competitive grounding') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural terms a decision-maker would say ('competitive landscape', 'product decision', 'competitive grounding') are present with a useful negative boundary ('not a market report'), but common synonyms like 'competitor analysis', 'battle card', or 'benchmarking' are missing.	4 / 5
Distinctiveness Conflict Risk	The 'competitive grounding, not a market report' carve-out establishes a clear niche and disambiguates from market reports, with only minor overlap risk against sibling single-company and market-sizing skills.	4 / 5
	Total	17 / 20 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: a03af68

Reviewed: 20 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.