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?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.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 file is essentially an empty table of contents with 43 unorganized, partially duplicated links to sub-skills that don't exist in the bundle. It provides no actionable content, no workflow guidance, and no concrete instructions. The main file fails on every dimension because it contains no substantive skill content whatsoever.

Suggestions

Add a concise quick-start section with concrete, actionable ASO steps (e.g., a keyword research workflow with specific commands or code examples) directly in the SKILL.md.

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

Include at least one complete executable workflow (e.g., 'Optimize an App Store Listing') with numbered steps and validation checkpoints directly in the main file.

Either provide the referenced sub-skill bundle files or consolidate the most critical content inline; currently all 43 references point to non-existent files.

DimensionReasoningScore

Conciseness

The file is almost entirely a list of 43 sub-skill links with no substantive content in the main file itself. Many entries 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 explains nothing Claude doesn't already know.

1 / 3

Actionability

There is zero actionable content in this file—no concrete instructions, no code, no commands, no examples, no specific guidance. It is purely a table of contents linking to 43 sub-skills, none of which are provided in the bundle.

1 / 3

Workflow Clarity

There is no workflow, no sequencing, no steps, and no validation checkpoints. The 43 links are presented as a flat, unstructured list with no indication of order, dependencies, or when to use which sub-skill.

1 / 3

Progressive Disclosure

While the skill attempts progressive disclosure by linking to sub-skills, the execution is poor: 43 links with no categorization, no overview content, duplicate entries, and no bundle files to back up any of the references. The links appear to be an unedited dump rather than a curated navigation structure.

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 for mobile app stores) with good natural trigger terms, but it lacks specific concrete actions and critically omits any 'Use when...' guidance. The high-level framing ('researching, optimizing, and tracking') would benefit from being broken down into specific capabilities to help Claude confidently select this skill.

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 on Apple App Store or Google Play.'

List specific concrete actions instead of generic verbs, e.g., 'Researches app store keywords, optimizes app titles and descriptions, analyzes competitor rankings, tracks download metrics, and improves store listing conversion rates.'

DimensionReasoningScore

Specificity

Names the domain (ASO) and mentions high-level actions ('researching, optimizing, and tracking mobile app performance'), but does not list specific concrete actions like keyword research, metadata editing, screenshot optimization, or review analysis.

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 not very detailed, warranting a 1.

1 / 3

Trigger Term Quality

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

3 / 3

Distinctiveness Conflict Risk

ASO is a clearly defined niche. The explicit mention of Apple App Store and Google Play Store, combined with the ASO acronym, makes this highly distinctive and unlikely to conflict with other skills.

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.