competitive-landscape

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

Quality

18%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/competitive-landscape/SKILL.md

Quality

Discovery

14%

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 marketing copy rather than a functional skill description. It relies on vague buzzwords ('comprehensive frameworks', 'winning strategies') without specifying concrete actions or when the skill should be triggered. It would be difficult for Claude to distinguish this skill from other strategy or business analysis skills.

Suggestions

Add a 'Use when...' clause with specific trigger terms like 'competitor analysis', 'SWOT analysis', 'competitive landscape', 'market positioning', or 'competitive benchmarking'.

Replace vague language with concrete actions, e.g., 'Creates competitor comparison matrices, performs SWOT analyses, maps competitive landscapes, and develops positioning statements'.

Differentiate from adjacent skills by specifying the exact frameworks or outputs produced, such as 'Porter's Five Forces analysis', 'perceptual maps', or 'competitive battlecards'.

Dimension	Reasoning	Score
Specificity	The description uses vague, buzzword-heavy language like 'comprehensive frameworks', 'differentiation opportunities', and 'winning market positioning strategies' without listing any concrete actions. No specific deliverables or operations are mentioned.	1 / 3
Completeness	The 'what' is vaguely described with abstract language, and there is no 'when' clause or explicit trigger guidance at all. The absence of a 'Use when...' clause caps this at 2, but the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'competition', 'differentiation', 'market positioning' that users might mention, but lacks common natural variations such as 'competitor analysis', 'SWOT', 'competitive landscape', 'market research', or 'competitive advantage'.	2 / 3
Distinctiveness Conflict Risk	The description is very generic and could easily overlap with skills related to business strategy, market research, SWOT analysis, or general strategic planning. Nothing clearly carves out a distinct niche.	1 / 3
	Total	5 / 12 Passed

Implementation

22%

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 shell — it has the structural scaffolding of a skill file but contains no substantive domain knowledge about competitive landscape analysis. The instructions are entirely generic boilerplate that could apply to any topic, offering no frameworks, methodologies, examples, or concrete guidance. All meaningful content is presumably deferred to the referenced playbook, but the skill itself provides nothing actionable.

Suggestions

Add concrete competitive analysis frameworks (e.g., Porter's Five Forces, SWOT, perceptual mapping) with specific steps and example outputs directly in the skill body.

Replace generic instructions like 'Apply relevant best practices' with specific, actionable steps such as 'Identify direct competitors by market segment, then map each on price vs. feature axes.'

Include at least one worked example showing input (e.g., a company/product) and expected output (e.g., a competitive positioning matrix or differentiation summary).

Add a clear multi-step workflow with validation checkpoints, e.g., '1. Define market boundaries → 2. Identify competitors → 3. Gather data → 4. Analyze positioning → 5. Identify gaps → 6. Validate findings with user.'

Dimension	Reasoning	Score
Conciseness	The content is relatively short but much of it is generic boilerplate ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') that adds no domain-specific value. The 'Use this skill when' and 'Do not use this skill when' sections are tautological.	2 / 3
Actionability	The instructions are entirely vague and abstract — 'Apply relevant best practices and validate outcomes' and 'Provide actionable steps and verification' give no concrete guidance on how to actually perform competitive landscape analysis. There are no frameworks, no specific steps, no examples, no templates.	1 / 3
Workflow Clarity	There is no clear workflow or sequence of steps for conducting a competitive analysis. The four bullet points under Instructions are generic platitudes with no sequencing, validation checkpoints, or concrete process.	1 / 3
Progressive Disclosure	There is a reference to `resources/implementation-playbook.md` which is one level deep and clearly signaled, but the SKILL.md itself provides essentially zero substantive overview content to serve as a useful entry point. The reference is the only content of value.	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: sickn33/antigravity-awesome-skills
Commit: 93c57b2

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