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", or requests competitive strategy analysis.

Quality

36%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/competitive-landscape/SKILL.md

Quality

Content

25%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is template boilerplate with no real content: generic instructions, duplicated use/do-not-use sections, and references to files that do not exist at inconsistent paths. It provides almost no actionable guidance for competitive analysis.

Suggestions

Replace the generic Instructions with concrete guidance: name the actual frameworks (e.g., Porter's Five Forces, SWOT, positioning maps), the inputs to gather, and the structure of the expected output.

Fix the bundle references: create resources/implementation-playbook.md (or sub-skills/), and use one consistent path in both the Instructions and Resources sections.

Delete the 'Use this skill when' / 'Do not use this skill when' sections — they duplicate the frontmatter description and add no information to the body.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept over-explanation, but it contains unnecessary filler: the 'Use this skill when / Do not use this skill when' sections duplicate the frontmatter description, and 'The task is unrelated to competitive landscape analysis' is pure padding. Below anchor 4 because those boilerplate sections are tokens that earn nothing.	3 / 5
Actionability	The Instructions are entirely generic boilerplate — 'Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification' — that could apply to any skill and instruct nothing. No framework, command, example, or concrete step appears anywhere in the body; the only pointer ('open resources/implementation-playbook.md') targets a nonexistent file.	1 / 5
Workflow Clarity	A rough three-beat sequence exists (clarify → apply → validate) but each step is poorly defined and no domain-specific workflow, checkpoint, or validation method is given. Not anchor 1 because a rough sequence is present; not anchor 3 because the steps are template placeholders rather than an actual analysis workflow with checkpoints.	2 / 5
Progressive Disclosure	The body references 'resources/implementation-playbook.md' and './sub-skills/implementation-playbook.md', but no resources/ or sub-skills/ directory (or any bundle files) exist, and the two paths are inconsistent for what appears to be the same file. Navigation is effectively broken; the structure is minimal boilerplate rather than an overview with well-signaled, real references.	2 / 5
	Total	8 / 20 Passed

Description

47%Weight 40%Scale 1-5

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 has strong, natural trigger phrases but completely lacks a 'what' statement — it never says what the skill does, only when to invoke it. This caps completeness at the low end despite good keyword coverage.

Suggestions

Add a leading capability statement before the trigger clause, e.g., 'Analyzes competitors, maps market structure, and identifies differentiation opportunities using frameworks like Porter's Five Forces. Use when...'

Include a few more common variations in the trigger list, such as 'competitor analysis', 'who are my competitors', or 'benchmark against rivals'.

State the concrete outputs the skill produces (e.g., competitive matrices, positioning maps, differentiation checklists) so the 'what' is explicit rather than implied by trigger phrases.

Dimension	Reasoning	Score
Specificity	The description names the domain ("competitive strategy analysis") but states no concrete capabilities the skill performs — the quoted phrases ("analyze competitors", "evaluate market positioning") are user triggers, not actions the skill takes. It is above anchor 1 because the domain and frameworks ("apply Porter's Five Forces") are clearly named, but below anchor 3 because it never lists even 1-2 actions the skill actually does.	2 / 5
Completeness	Only a 'when' clause is present ("This skill should be used when the user asks to...") with no statement of what the skill does — matching the anchor-2 example 'Use when working with documents'. It cannot score 3 because anchor 3 requires a clear 'what', which is entirely absent.	2 / 5
Trigger Term Quality	Good natural-phrase coverage: "analyze competitors", "assess competitive landscape", "identify differentiation", "evaluate market positioning", "apply Porter's Five Forces" — phrases a user would plausibly say. Below anchor 5 because common variations like "competitor analysis", "who are my competitors", or "benchmark against rivals" are missing.	4 / 5
Distinctiveness Conflict Risk	The competitive-analysis niche is mostly distinct, with named frameworks like "apply Porter's Five Forces" giving clear triggers. Minor overlap risk with adjacent market-research or strategy skills keeps it below anchor 5.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI
Path: .agent/skills/competitive-landscape/SKILL.md
Commit: c4a059b

Reviewed: 1 hour 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.