competitive-landscape

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

Quality

47%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/competitive-landscape/SKILL.md

The canonical home for this skill is competitive-landscape in rmyndharis/antigravity-skills

Quality

Content

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

The content is a generic boilerplate template with no domain-specific guidance, abstract non-executable instructions, and a broken reference to a non-existent resources file, making it largely non-actionable for competitive landscape work.

Suggestions

Replace the generic instruction bullets with concrete competitive-analysis procedures (e.g., build a competitor feature matrix, map positioning on a 2x2 axis, run a SWOT) with specific steps.

Create the referenced `resources/implementation-playbook.md` (or remove the broken reference) so progressive disclosure points to real material.

Add validation/verification checkpoints for the analysis outputs (e.g., cross-check competitor data against multiple sources before finalizing positioning).

Dimension	Reasoning	Score
Conciseness	The body is brief and does not pad or explain concepts Claude already knows; it assumes competence, matching the 'efficient; minor instances of over-explanation' anchor; not 5 because the terseness comes at the cost of substantive guidance.	4 / 5
Actionability	Instructions are abstract ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no concrete code, commands, or specifics — only high-level hints missing executable steps, fitting the 'minimal concrete guidance' anchor.	2 / 5
Workflow Clarity	The bullets ('Clarify goals...', 'Apply...', 'Provide...') form only a rough, generic list with no validation checkpoints or concrete sequencing; fits the 'rough sequence, steps poorly defined, validation absent' anchor.	2 / 5
Progressive Disclosure	The body references `resources/implementation-playbook.md` as the detailed material, but no such bundle file exists, so the single one-level-deep reference is broken and navigation fails; fits the 'minimal structure; references buried/broken' anchor.	2 / 5
	Total	10 / 20 Passed

Description

55%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.

The description clearly states what the skill does with several concrete actions, but omits any 'when to use it' trigger guidance and lacks natural keyword synonyms, leaving trigger activation underspecified.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when analyzing competitors, building a competitive matrix, or developing market positioning').

Broaden trigger terms with synonyms and concrete artifacts users mention (e.g., 'competitor analysis', 'market research', 'SWOT', 'differentiation').

Sharpen distinctiveness by tying triggers to specific deliverables (competitive matrices, positioning statements) to reduce overlap with generic strategy skills.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions ('analyzing competition', 'identifying differentiation opportunities', 'developing winning market positioning strategies'), matching the 'several specific actions; minor gaps' anchor; not 5 because coverage is moderate without synonyms or extensions.	4 / 5
Completeness	Has a clear 'what' (frameworks for analyzing competition and positioning) but no 'when'/Use-when clause at all; the missing trigger guidance caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Contains relevant domain terms ('competition', 'differentiation', 'market positioning') but misses common natural variations and synonyms a user would say ('competitor analysis', 'market research', 'competitors'); fits the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Competitive landscape' and 'market positioning' are a somewhat specific niche, but overlap with general strategy and marketing-research skills is non-trivial; fits the 'somewhat specific but could overlap' anchor.	3 / 5
	Total	13 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/competitive-landscape/SKILL.md
Commit: 57c135b

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