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", or requests competitive strategy analysis.
Overall
score
41%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill competitive-landscapeActivation
37%This description is fundamentally incomplete - it functions as a trigger list rather than a skill description. While it excels at providing natural keywords users would say, it completely fails to explain what the skill actually does, what outputs it produces, or what specific analytical capabilities it provides. The description needs to be restructured to lead with concrete actions.
Suggestions
Add specific capabilities at the beginning: e.g., 'Conducts competitive analysis including market positioning maps, SWOT comparisons, Porter's Five Forces frameworks, and differentiation assessments.'
Describe concrete outputs: e.g., 'Generates competitor comparison matrices, identifies market gaps, and produces strategic recommendations.'
Restructure to follow the pattern: '[What it does]. Use when [triggers].' rather than leading with triggers alone.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only lists trigger phrases without explaining what the skill actually does. There are no specific capabilities like 'analyze market share', 'generate comparison matrices', or 'identify competitive advantages'. | 1 / 3 |
Completeness | The description only addresses 'when' (trigger conditions) but completely omits 'what' - there is no explanation of what the skill actually does or what outputs it produces. This is the inverse of the typical problem. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'analyze competitors', 'competitive landscape', 'identify differentiation', 'market positioning', 'Porter's Five Forces', 'competitive strategy analysis'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The trigger terms are fairly specific to competitive analysis, but without describing actual capabilities, it could overlap with general business analysis or strategy skills. Terms like 'market positioning' could trigger for marketing skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%This skill is a hollow shell that provides no actual competitive analysis guidance. It consists entirely of generic meta-instructions and boilerplate sections, deferring all substantive content to an external file. The skill fails to deliver on its promise of 'comprehensive frameworks' and provides nothing actionable about Porter's Five Forces, differentiation analysis, or market positioning.
Suggestions
Add concrete competitive analysis frameworks (e.g., Porter's Five Forces template with specific questions to answer for each force)
Include a quick-start workflow with specific steps: 1. Identify competitors, 2. Gather data points X/Y/Z, 3. Apply framework, 4. Synthesize findings
Provide at least one concrete example showing input (company/market context) and expected output (analysis structure/format)
Remove generic boilerplate sections and replace with domain-specific guidance that Claude doesn't already know
| 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 platitudes rather than domain-specific 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, or executable guidance for competitive analysis. Porter's Five Forces is mentioned in the description but not explained or operationalized. | 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 conducting competitive landscape analysis. | 1 / 3 |
Progressive Disclosure | References an external resource file appropriately, but the main skill provides almost no substantive content—it's essentially just a pointer to another file with no useful overview or quick-start guidance. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Reviewed
Table of Contents
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.