competitive-analysis-process

Orchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/competitive-analysis-process/SKILL.md

Quality

Content

77%

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

A well-sequenced, highly actionable orchestration workflow with concrete delegation, decision checkpoints, and evidence-discipline validation; its main gaps are occasional editorial verbosity and referenced bundle files that are not actually present.

Suggestions

Provide the referenced bundle files (template.md, examples/sample.md, examples/sample-industrial.md) or remove the links, so the one-level-deep navigation resolves to real files and progressive disclosure is complete.

Trim editorial flourishes in Purpose, Key Concepts, and the Watch-for callouts to tighten conciseness without losing the actionable substance.

Dimension	Reasoning	Score
Conciseness	The body is information-dense per step (frameworks, run, watch-for, decision point) and avoids explaining basic concepts, but editorial flourishes like "companies lie less where lying is a felony" and "permission to skip" add tokens that could be tightened, falling short of 'every token earns its place'.	2 / 3
Actionability	Each step names a specific delegated skill and the artifact it produces, lists named frameworks with brief glosses, gives decision points and watch-fors, and Step 7 maps outputs to builder skills; as an instruction-only orchestrator the guidance is concrete and actionable, so absence of code is not penalized.	3 / 3
Workflow Clarity	Steps 0-7 are clearly sequenced with explicit decision-point checkpoints, evidence discipline acts as validation ("Stack before you brief", Fact/Inference/Assumption labels), and a referenced engagement tracker serves as a checklist; checkpoints are explicit rather than implicit, above the score-2 anchor.	3 / 3
Progressive Disclosure	The overview-to-delegated-skills structure is well designed with clearly signaled one-level-deep links, but the referenced bundle files (template.md, examples/sample.md, examples/sample-industrial.md) are not present in the workspace and no bundle files exist, so navigation is incomplete and unverified against the actual bundle structure.	2 / 3
	Total	10 / 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 and when, and carves a distinct niche against sibling skills, but it stays at the orchestration-summary level rather than listing concrete actions and omits common trigger-term variations.

Suggestions

Add one or two concrete actions or outputs (e.g., battle cards, comparison matrices, threat briefs) to lift specificity from a domain summary to a multi-action list.

Broaden trigger terms to include natural variations users say, such as "competitor analysis", "competitive landscape", or "competitive intelligence".

Dimension	Reasoning	Score
Specificity	"Orchestrate a complete competitive analysis across six steps, from landscape to strategic direction" names the domain and an overarching action but does not enumerate multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action list of a 3.	2 / 3
Completeness	It states what ("Orchestrate a complete competitive analysis across six steps") and when ("Use when you need the full picture, not a single scan or card"), explicitly answering both with an explicit trigger clause.	3 / 3
Trigger Term Quality	"competitive analysis", "full picture", "scan", and "card" are relevant, but common user variations like "competitor analysis", "competitive landscape", and "competitive/market intelligence" are absent, so it has some keywords with missing common variations rather than broad coverage.	2 / 3
Distinctiveness Conflict Risk	"not a single scan or card" explicitly distinguishes the umbrella from sibling scan/card skills, giving it a clear niche with distinct triggers unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 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, 21 suspicious	Warning

	Total	14 / 16 Passed

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