CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

45

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/competitive-landscape/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

The body is lean and well-sectioned but almost entirely generic boilerplate that adds no competitive-analysis-specific value, and its single detailed reference points to a file that is not present.

Suggestions

Replace the generic instruction bullets with concrete competitive-analysis guidance: the actual frameworks (e.g. Porter's Five Forces steps), a positioning/differentiation template, and a worked example.

Create the referenced `resources/implementation-playbook.md` (or point the reference at an existing file) so the detailed-materials link is not dangling, and reference it from only one section.

Add a sequenced workflow with explicit validation (e.g. gather competitor data -> apply framework -> cross-check positioning claims -> verify differentiation against evidence).

DimensionReasoningScore

Conciseness

The body is short and avoids over-explaining known concepts, but the generic instruction bullets ("Clarify goals, constraints, and required inputs", "Apply relevant best practices") are low-value filler that do not earn their place.

2 / 3

Actionability

Despite claiming "Comprehensive frameworks", the body gives no concrete framework, template, command, or example; instructions like "Apply relevant best practices and validate outcomes" are abstract and describe rather than instruct.

1 / 3

Workflow Clarity

The Instructions bullets are generic boilerplate with no real sequenced workflow for competitive analysis and no concrete validation checkpoints, only a vague "validate outcomes" mention.

1 / 3

Progressive Disclosure

Sections are reasonably organized, but the only referenced file (`resources/implementation-playbook.md`) does not exist in the bundle and is referenced redundantly in both Instructions and Resources, so navigation is broken.

2 / 3

Total

6

/

12

Passed

Description

72%

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 terms and a clear niche, but it over-rotates on the 'when' and never explicitly states what the skill does, leaving the 'what' only implied.

Suggestions

Lead with a concrete capability statement (e.g. 'Analyzes competitors, maps market positioning, and applies frameworks like Porter's Five Forces') before the use-when clause so 'what' is explicit.

Keep the existing trigger phrases but frame them as a 'Use when...' clause following the capability sentence to clearly answer both what and when.

DimensionReasoningScore

Specificity

Action verbs appear ("analyze competitors", "identify differentiation", "evaluate market positioning") but they are embedded inside quoted trigger phrases rather than stated as concrete capabilities, so it names the domain and some actions without a comprehensive capability statement.

2 / 3

Completeness

The 'when' is explicit (the entire description is a use-when clause), but 'what does this do' is only implied through the trigger verbs and never stated as a capability, so it does not clearly answer both.

2 / 3

Trigger Term Quality

It lists several natural phrases a user would actually say ("analyze competitors", "assess competitive landscape", "apply Porter's Five Forces"), giving good coverage of likely trigger language.

3 / 3

Distinctiveness Conflict Risk

Triggers like "Porter's Five Forces", "competitive landscape", and "market positioning" define a clear niche that is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.