CtrlK
BlogDocsLog inGet started
Tessl Logo

competitor-analysis

When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/competitor-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-structured, actionable analysis template that respects token budget and gives concrete tables and metrics to collect. The main gap is workflow clarity: the multi-step process lacks any validation or verification checkpoints to confirm inputs and data completeness before producing the final competitive assessment.

Suggestions

Add explicit validation checkpoints to the workflow — e.g., after Initial Assessment, 'Confirm all App IDs resolve to live App Store listings before proceeding' and after the Analysis Framework, 'Verify every table cell is populated; mark gaps explicitly rather than leaving blanks.'

Insert a feedback loop for fragile inputs: if a competitor App ID is unavailable or data is sparse, state the fallback (substitute a similar competitor or flag the gap in the output) before continuing.

Trim the opening motivational framing ('Your goal is to perform a thorough analysis... and identify actionable opportunities to outperform them') to a one-line role statement to lift conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is lean — mostly structured tables, pointed analysis questions, and templates — and it assumes Claude's ASO knowledge without explaining basics, but the opening role/goal sentence ('Your goal is to perform a thorough analysis... and identify actionable opportunities to outperform them') is mild motivational framing that could be trimmed, keeping it at 4 rather than 5.

4 / 5

Actionability

As an instruction-only skill it gives concrete, specific guidance — fill-in tables, exact metrics ('Char usage (title) /30', screenshot 'target: 10'), a competitor mix recommendation (2 direct, 1-2 aspirational, 1 emerging), and a defined output structure — which is mostly executable with only minor gaps, fitting the 4 anchor.

4 / 5

Workflow Clarity

A clear sequence exists (Initial Assessment → Competitor Identification → 6-part Analysis Framework → Output Format), but there are no validation checkpoints — e.g., no step to confirm App IDs, verify data was gathered for all competitors before analysis, or sanity-check estimates — so it matches the 3 anchor of 'sequence present but checkpoints missing or implicit.'

3 / 5

Progressive Disclosure

The content is well-organized under clear ## / ### headers with a Related Skills section for cross-skill navigation, and being a self-contained template it reasonably needs no external bundle files; it stays at 4 rather than 5 because nothing is split into one-level-deep references and the over-50-line simple-skill exception does not apply.

4 / 5

Total

15

/

20

Passed

Description

81%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.

A strong description with excellent natural trigger phrases and explicit boundary guidance distinguishing it from sibling skills. Its main weakness is structural: the capability statement is wrapped inside a 'when' clause rather than opening as a crisp third-person declarative, which slightly softens both specificity and completeness.

DimensionReasoningScore

Specificity

The description names the domain and three actions ('analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning'), but the verbs 'analyze' and 'understand' are abstract and the 'what' is embedded in a 'when' clause rather than stated declaratively, so it sits at the 3 anchor rather than 4.

3 / 5

Completeness

Both 'what' (analyze/find/understand) and 'when' (an explicit 'Also use when the user mentions...' clause with concrete triggers) are present, but the 'what' never opens as a clean declarative capability statement — it is folded into the leading 'When the user wants to...' clause, which is the minor gap that keeps it below 5.

4 / 5

Trigger Term Quality

It includes multiple natural phrases a user would actually say ('competitor analysis', 'competitive research', 'keyword gap', 'what are my competitors doing', 'compare my app to'), with synonyms, matching the comprehensive-coverage 5 anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (competitive intelligence for the App Store) with distinct triggers and adds explicit boundary guidance ('For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.'), matching the 5 anchor for minimal conflict risk.

5 / 5

Total

17

/

20

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
Eronred/aso-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.