CtrlK
BlogDocsLog inGet started
Tessl Logo

app-store-optimization

Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store

32

Quality

27%

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 ./.agent/skills/app-store-optimization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%

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

This skill is essentially an empty table of contents with 43 poorly organized, often duplicated links to sub-skill files that don't exist in the bundle. It contains no actionable content, no concrete guidance, no examples, and no workflow structure. The file fails on every dimension by providing neither useful overview content nor a well-organized navigation structure.

Suggestions

Deduplicate and categorize the sub-skill links into logical groups (e.g., Research, Optimization, Analytics, Launch) with brief 1-line descriptions of each.

Add a quick-start workflow section showing the typical ASO process sequence (e.g., 1. Research keywords → 2. Optimize metadata → 3. Prepare visual assets → 4. Launch → 5. Monitor & iterate).

Include at least one concrete, actionable example in the main SKILL.md (e.g., a keyword analysis template or metadata optimization checklist) so the file has standalone value.

Remove duplicate entries (Keyword Research, Metadata Optimization each appear 3 times) and ensure each linked file actually exists in the bundle.

DimensionReasoningScore

Conciseness

The file is almost entirely a list of 43 sub-skill links with no substantive content, many of which are duplicates (e.g., 'Keyword Research' appears 3 times, 'Metadata Optimization' appears 3 times). The introductory text is vague filler ('comprehensive skill provides complete ASO capabilities') that adds no value.

1 / 3

Actionability

There is zero actionable content—no concrete guidance, no code, no commands, no examples, no specific instructions. The entire file is just a list of links to sub-skills with no indication of what to do or how to use them.

1 / 3

Workflow Clarity

There is no workflow, no sequencing, no steps, and no validation checkpoints. The 43 links are presented as a flat, unnumbered list with no indication of order, dependencies, or process flow.

1 / 3

Progressive Disclosure

While the skill attempts progressive disclosure by linking to sub-skills, the execution is poor: 43 links with duplicates, no categorization or grouping, no brief descriptions of what each link contains, and no bundle files exist to support the references. This is a disorganized index, not well-structured progressive disclosure.

1 / 3

Total

4

/

12

Passed

Description

54%

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 identifies a clear niche (ASO) with good trigger terms for the domain, making it distinctive. However, it lacks specific concrete actions beyond high-level verbs and critically omits any 'Use when...' guidance, significantly weakening its ability to help Claude select it at the right time.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about app store rankings, keyword optimization, app metadata, store listings, or improving app visibility.'

List specific concrete actions instead of generic verbs, e.g., 'Researches keywords and competitors, optimizes app titles/descriptions/metadata, analyzes reviews and ratings, tracks keyword rankings and download metrics.'

DimensionReasoningScore

Specificity

Names the domain (ASO) and mentions high-level actions ('researching, optimizing, and tracking mobile app performance'), but doesn't list specific concrete actions like keyword research, metadata optimization, screenshot analysis, review monitoring, or A/B testing.

2 / 3

Completeness

Describes 'what' at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also vague, warranting a 1.

1 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'App Store Optimization', 'ASO', 'Apple App Store', 'Google Play Store', 'mobile app performance'. These cover the key terms a user would naturally use when seeking this skill.

3 / 3

Distinctiveness Conflict Risk

ASO is a clearly defined niche with distinct terminology (App Store, Google Play, ASO). It's unlikely to conflict with other skills due to the specificity of the mobile app store optimization domain.

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.