competitive-landscape
Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies.
24
14%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/competitive-landscape/SKILL.mdQuality
Discovery
22%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 relies heavily on business buzzwords and abstract language without specifying concrete actions or deliverables. It lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The description would benefit significantly from listing specific outputs and adding explicit trigger conditions.
Suggestions
Add a 'Use when...' clause with specific trigger terms like 'Use when the user asks about competitor analysis, competitive landscape, SWOT analysis, market positioning, or differentiation strategy.'
Replace vague phrases like 'comprehensive frameworks' with concrete actions such as 'Creates competitor comparison matrices, performs SWOT analyses, maps competitive positioning, and generates differentiation strategies.'
Include common user-facing terms and file/output types, e.g., 'competitive benchmarking, market share analysis, positioning maps, competitor profiles.'
| 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—no specific deliverables or methods are named. | 1 / 3 |
Completeness | The description loosely addresses 'what' (analyzing competition, developing positioning strategies) but has no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'competition,' 'differentiation,' and 'market positioning' that users might naturally use, but misses common variations like 'competitor analysis,' 'SWOT,' 'competitive landscape,' 'market research,' or 'competitive advantage.' | 2 / 3 |
Distinctiveness Conflict Risk | While 'competitive analysis' and 'market positioning' provide some domain specificity, the broad framing ('comprehensive frameworks') could easily overlap with general strategy, marketing, or business analysis skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
7%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 generic template with no substantive content about competitive landscape analysis. It contains no frameworks, no analytical methodologies, no examples, and no actionable guidance — just boilerplate instructions that could apply to any topic. The referenced implementation playbook is not provided, leaving the skill essentially empty.
Suggestions
Add concrete competitive analysis frameworks (e.g., Porter's Five Forces, SWOT, perceptual mapping) with specific step-by-step instructions and example outputs for each.
Include at least one worked example showing a competitive landscape analysis from inputs (e.g., competitor list, market data) to a structured output (e.g., positioning map, differentiation matrix).
Replace generic instructions like 'Apply relevant best practices' with specific, actionable steps such as 'Identify 3-5 direct competitors, map their positioning on price vs. feature axes, identify underserved quadrants.'
Provide the referenced `resources/implementation-playbook.md` bundle file with detailed patterns, or inline the most critical content directly in the SKILL.md.
| 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, code, templates, or examples for competitive analysis. Every instruction is vague and abstract (e.g., 'Apply relevant best practices and validate outcomes'), providing no executable guidance whatsoever. | 1 / 3 |
Workflow Clarity | There is no meaningful workflow defined. The four bullet points under Instructions are generic platitudes with no sequencing, no validation checkpoints, and no specificity to 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 SKILL.md itself contains almost no substantive overview content to serve as a useful entry point. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
90%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
f5dc9e3
- Reviewed
Table of Contents
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.