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.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A lean, well-structured analysis template that is concise and actionable with good progressive disclosure. Its main gap is workflow clarity: the sequence is clear but lacks explicit validation or feedback checkpoints.

Suggestions

Add an explicit validation/review checkpoint before producing the Output Format (e.g., "Confirm every framework table is filled before drafting the Executive Summary") to strengthen workflow clarity.

Note the data source or method for hard-to-obtain metrics (estimated downloads/mo, revenue/mo, Apple Search Ads presence) so the analysis is reproducible rather than assumed.

Consider trimming the opening role/goal sentence, which restates intent the description already conveys, for tighter token efficiency.

DimensionReasoningScore

Conciseness

The body is dense, template-driven tables and checklists with no concept over-explanation; the only mild fluff is the opening role preamble, and every other section earns its tokens.

3 / 3

Actionability

Provides concrete fill-in templates, specific metrics, defaults (target country US, /30 char limits, target 10 screenshots), and concrete competitor-identification methods; for an instruction-only analysis skill the guidance is actionable.

3 / 3

Workflow Clarity

A clear numbered sequence exists (Initial Assessment → Identification → 6-part Framework → Output Format) with implicit completeness checks via the tables, but there are no explicit validation checkpoints or feedback loops.

2 / 3

Progressive Disclosure

Well-organized single-file skill with clear section navigation; references are one level deep (Related Skills list, app-marketing-context.md) with no nested references and no bundle files to mis-signal.

3 / 3

Total

11

/

12

Passed

Description

100%

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, well-constructed description that names concrete actions, surfaces natural trigger terms, and explicitly distinguishes itself from sibling skills. It fully satisfies the what-and-when requirement.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("analyze competitors' App Store strategy", "find keyword gaps", "understand competitive positioning") rather than vague language; uses third-person voice with no first/second-person penalty.

3 / 3

Completeness

Explicitly answers both what (analyze strategy, find keyword gaps, understand positioning) and when ("Also use when the user mentions...") with an explicit trigger clause.

3 / 3

Trigger Term Quality

Strong coverage of natural phrases a user would actually say: "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", "compare my app to".

3 / 3

Distinctiveness Conflict Risk

Clear ASO/competitor-intelligence niche with distinct triggers, and explicit cross-refs to keyword-research and metadata-optimization reduce overlap with adjacent skills.

3 / 3

Total

12

/

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