competitive-landscape

Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.

Quality

14%

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/competitive-landscape/SKILL.md

Quality

Content

7%Scale 1-3

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

This skill is a hollow template with no actual competitive analysis content. It consists entirely of generic boilerplate instructions that could apply to any domain, providing zero actionable guidance on frameworks like Porter's Five Forces, competitive positioning matrices, differentiation analysis, or market mapping. The referenced implementation playbook is not provided, leaving the skill with no usable substance.

Suggestions

Add concrete competitive analysis frameworks (e.g., Porter's Five Forces, SWOT, perceptual mapping) with specific steps and example outputs for each.

Replace generic instructions ('Apply relevant best practices') with actionable, domain-specific guidance such as structured templates for competitor profiles, differentiation matrices, or positioning statements.

Include at least one worked example showing input (e.g., a market scenario) and expected output (e.g., a completed competitive analysis summary).

Provide the referenced `resources/implementation-playbook.md` bundle file, or inline the essential patterns and examples directly in the skill body.

Dimension	Reasoning	Score
Conciseness	The content is almost entirely generic boilerplate with no domain-specific substance. Phrases like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' are vacuous filler that add zero value beyond what Claude already knows.	1 / 3
Actionability	There are no concrete frameworks, specific analytical steps, example outputs, or executable guidance. Every instruction is vague and abstract (e.g., 'Apply relevant best practices and validate outcomes') with no actual competitive analysis methodology provided.	1 / 3
Workflow Clarity	There is no meaningful workflow. The four bullet points under Instructions are generic platitudes with no sequencing, no validation checkpoints, and no concrete steps for performing competitive landscape analysis.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` which is a reasonable one-level-deep reference, but no bundle files are provided so the reference is unverifiable. The main file itself contains no substantive overview content to serve as a useful entry point.	2 / 3
	Total	5 / 12 Passed

Description

22%Scale 1-3

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 description reads like a marketing tagline rather than a functional skill description. It relies on vague buzzwords ('comprehensive frameworks,' 'winning strategies') without specifying concrete actions or outputs, and it completely lacks a 'Use when...' clause to guide skill selection. The description would benefit significantly from listing specific deliverables and adding explicit trigger conditions.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about competitor analysis, competitive landscape, market positioning, SWOT analysis, or differentiation strategy.'

Replace vague language with concrete actions, e.g., 'Creates competitor comparison matrices, generates SWOT analyses, develops positioning maps, and drafts value proposition statements.'

Remove fluff words like 'comprehensive' and 'winning' and instead specify the frameworks or outputs the skill produces.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'comprehensive frameworks,' 'analyzing competition,' 'identifying differentiation opportunities,' and 'developing winning market positioning strategies.' These are buzzwords rather than concrete actions—it doesn't specify what the skill actually does (e.g., create SWOT analyses, generate positioning maps, compare competitor pricing).	1 / 3
Completeness	The description only vaguely addresses 'what' (frameworks for analyzing competition and positioning) and completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent statement telling Claude when to select this skill.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'competition,' 'differentiation,' and 'market positioning' that users might naturally use. However, it misses common variations like 'competitor analysis,' 'competitive landscape,' 'market research,' 'SWOT,' 'value proposition,' or 'go-to-market strategy.'	2 / 3
Distinctiveness Conflict Risk	While 'competitive analysis' and 'market positioning' provide some specificity, terms like 'analyzing competition' and 'differentiation' could overlap with general business strategy, marketing strategy, or market research skills. It's somewhat specific but not clearly carved into a distinct niche.	2 / 3
	Total	6 / 12 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: popey/claude-code-skills
Path: skills/competitive-landscape/SKILL.md
Commit: a5a6601

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