competitive-analysis
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
60
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/competitive-analysis/SKILL.mdQuality
Discovery
40%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 focuses almost entirely on when to use the skill but fails to specify what concrete actions or outputs it provides. It uses moderately relevant trigger terms but lacks specificity about capabilities, making it hard to distinguish from general market research or strategy skills. Adding concrete actions and more natural trigger keywords would significantly improve it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates competitive comparison matrices, generates SWOT analyses, builds feature-by-feature battlecards, and identifies market positioning gaps.'
Expand trigger terms to include natural user phrases like 'competitor analysis', 'competitive intel', 'battlecard', 'market comparison', 'how do we compare to X', 'differentiation'.
Restructure to lead with 'what it does' before the 'when to use' clause, e.g., 'Analyzes competitors, builds comparison matrices, and creates positioning strategies. Use when the user asks about competitor analysis, competitive landscape, or product differentiation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'evaluate competitors', 'understand the competitive landscape', and 'position their product against alternatives' without listing any concrete actions (e.g., create comparison matrices, analyze pricing strategies, generate SWOT analyses). | 1 / 3 |
Completeness | The description addresses 'when' (when the user needs to evaluate competitors, understand landscape, or position product) but lacks a clear 'what' — it never explains what concrete outputs or actions the skill performs. The 'when' clause is present but the 'what' is essentially absent. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'competitors', 'competitive landscape', and 'position...against alternatives' that users might naturally say, but misses common variations like 'competitor analysis', 'market comparison', 'competitive intel', 'battlecard', or 'differentiation'. | 2 / 3 |
Distinctiveness Conflict Risk | The competitive analysis domain is somewhat specific, but terms like 'position their product' and 'understand the competitive landscape' could overlap with market research, product strategy, or marketing skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid instructional skill for competitive analysis with a well-structured workflow and clear output format. Its main weaknesses are moderate verbosity (explaining concepts Claude likely knows, like what direct vs adjacent competitors are) and limited concrete actionability — the examples describe good outputs rather than showing them, and there are no templates or filled-out examples that Claude could directly adapt. The workflow sequencing is strong for a strategic analysis task.
Suggestions
Include at least one fully worked-out example showing a complete competitor profile table filled with realistic data, rather than just describing what good output looks like.
Trim the 'When to Use' trigger phrases and the 'Frameworks & Best Practices' explanations of concepts Claude already understands (e.g., the definition of direct vs adjacent competitors) to reduce token usage by ~25%.
Consider moving the detailed 'Frameworks & Best Practices' section to a separate referenced file to improve progressive disclosure and keep the main skill focused on the workflow and output format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity. The 'When to Use' section lists many trigger phrases that Claude could infer, and the 'Frameworks & Best Practices' section, while valuable, contains some advice that's general business knowledge Claude already possesses (e.g., explaining what direct vs adjacent competitors are). The content could be tightened by ~30%. | 2 / 3 |
Actionability | The workflow provides a clear sequence of steps and the output format is well-specified with table structures. However, the guidance remains at a strategic/conceptual level without concrete executable examples — no actual code, specific tool commands, or copy-paste-ready templates. The examples section describes what good output looks like rather than showing it, which reduces actionability. | 2 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced and logically ordered from scoping through synthesis. Each step has a clear purpose and specific sub-tasks. For a non-destructive analytical task like competitive analysis, explicit validation checkpoints are less critical, and the workflow includes implicit quality checks like 'validate insights across multiple sources' and 'distinguish direct from adjacent.' | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom (market-research, prd-writing, user-research-synthesis) which is good navigation. However, the content is quite long and monolithic — the Frameworks & Best Practices section and the detailed Output Format could potentially be split into referenced files. Everything is inline in one document when some sections could benefit from separation. | 2 / 3 |
Total | 9 / 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
- shawnpang/startup-founder-skills
- Commit
4ad31b4
- 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.