competitive-landscape

This skill should be used when the user asks to \\\"analyze competitors", "assess competitive landscape", "identify differentiation", "evaluate market positioning", "apply Porter's Five Forces",...

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill competitive-landscape

What are skills?

1.16x

Quality

29%

Does it follow best practices?

Impact

97%

1.16x

Average score across 3 eval scenarios

Optimize this skill with Tessl

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

SKILL.md

Review

Evals

Discovery

37%

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 is fundamentally incomplete - it only provides trigger phrases without any explanation of what the skill actually does. While the trigger terms are well-chosen and natural, the complete absence of capability description makes it impossible for Claude to understand what actions this skill enables or what outputs it produces.

Suggestions

Add a capability statement before the trigger phrases describing what the skill does (e.g., 'Conducts comprehensive competitive analysis including market positioning assessment, competitor profiling, and strategic recommendations')

Describe the outputs or deliverables the skill produces (e.g., 'generates competitor comparison matrices, SWOT analyses, and differentiation strategies')

Restructure to follow the pattern: '[What it does]. Use when [triggers]' rather than starting with 'This skill should be used when...'

Dimension	Reasoning	Score
Specificity	The description only lists trigger phrases without describing any concrete actions or capabilities. It says nothing about what the skill actually does - no verbs describing actions like 'analyzes', 'generates reports', 'compares', etc.	1 / 3
Completeness	The description only addresses 'when' (trigger phrases) but completely omits 'what' - there is no explanation of what the skill actually does or what outputs it produces. The 'what' component is entirely missing.	1 / 3
Trigger Term Quality	Contains good natural keywords users would say: 'analyze competitors', 'competitive landscape', 'differentiation', 'market positioning', 'Porter's Five Forces'. These are terms users would naturally use when requesting competitive analysis.	3 / 3
Distinctiveness Conflict Risk	The trigger terms are fairly specific to competitive analysis domain, but without describing actual capabilities, it's unclear how this would be distinguished from other business analysis or strategy skills that might exist.	2 / 3
	Total	7 / 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 template that provides no actual guidance on competitive landscape analysis. It mentions Porter's Five Forces in the description but contains zero frameworks, methodologies, or concrete examples. The instructions are generic meta-advice that could apply to any domain, making this skill essentially useless without the referenced playbook.

Suggestions

Add concrete competitive analysis frameworks (e.g., Porter's Five Forces template, competitor matrix structure, SWOT format) with specific examples

Replace generic instructions with actionable steps like 'Identify 3-5 direct competitors by [specific criteria]' or 'Score competitors on these dimensions: [list]'

Include at least one worked example showing input (company/market context) and expected output (analysis structure)

Provide specific deliverable formats or templates for competitive analysis outputs

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes generic boilerplate sections ('Use this skill when', 'Do not use this skill when') that add little value. The instructions are vague filler rather than substantive guidance.	2 / 3
Actionability	The instructions are entirely abstract ('Clarify goals', 'Apply relevant best practices', 'Provide actionable steps') with no concrete frameworks, specific analysis methods, code, commands, or executable examples for competitive analysis.	1 / 3
Workflow Clarity	No clear workflow or sequence is provided. The four bullet points are generic meta-instructions that could apply to any skill, not a structured process for competitive landscape analysis.	1 / 3
Progressive Disclosure	References an external resource file appropriately, but the main skill content is so thin that it's unclear what value the overview provides. The reference is present but the skill itself lacks substantive overview content.	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

Reviewed: about 18 hours 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.