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

51

1.22x
Quality

27%

Does it follow best practices?

Impact

94%

1.22x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-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 an extensive but largely non-actionable catalog of ASO concepts and best practices. It references numerous Python scripts that don't exist in the bundle, provides no executable code, and reads more like a textbook chapter than an operational skill. The extreme verbosity (~400+ lines) wastes token budget on information Claude already knows while failing to provide the concrete, executable guidance that would make it useful.

Suggestions

Replace the descriptive capability lists with concrete, executable workflows—either provide the actual Python scripts referenced or remove the script section entirely and focus on step-by-step instructions Claude can follow directly.

Reduce the SKILL.md to a concise overview (~50-80 lines) covering the core workflow steps, and split detailed content (best practices, platform requirements, input/output schemas) into separate bundle files with clear references.

Add explicit multi-step workflows with validation checkpoints, e.g., 'Step 1: Gather current metadata → Step 2: Run keyword analysis → Step 3: Validate character limits → Step 4: Generate optimized metadata → Step 5: Verify keyword density targets are met.'

Remove generic best practices Claude already knows (e.g., 'respond to reviews within 24-48 hours', 'always be courteous') and focus on platform-specific constraints and non-obvious tactical guidance that adds unique value.

DimensionReasoningScore

Conciseness

Extremely verbose at ~400+ lines. Explains concepts Claude already knows (what ASO is, what reviews are, basic best practices like 'respond quickly to reviews'). Massive bullet-point lists describe capabilities rather than instruct. The 'Scripts' section lists function signatures for scripts that don't exist in the bundle. Much of this content is generic marketing/ASO knowledge that adds no unique value.

1 / 3

Actionability

Despite listing many script functions (keyword_analyzer.py, metadata_optimizer.py, etc.), none of these scripts exist in the bundle. The JSON input schemas are illustrative but not connected to any executable workflow. The 'How to Use' section just shows example prompts to Claude rather than concrete steps. No actual executable code or commands are provided—everything is descriptive.

1 / 3

Workflow Clarity

There is no clear multi-step workflow with sequencing or validation checkpoints. The skill reads as a reference document/catalog of ASO topics rather than a procedural guide. The 'How to Use' section provides example prompts but no actual workflow steps. No feedback loops or verification steps exist for any of the described processes.

1 / 3

Progressive Disclosure

Monolithic wall of text with no bundle files to reference. Everything is crammed into a single massive file with no external references to detailed guides. The content would benefit enormously from splitting into separate files (keyword research guide, metadata optimization guide, etc.) with the SKILL.md serving as a concise overview with pointers.

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 a 'Use when...' clause entirely and the capability descriptions remain at a high level ('researching, optimizing, tracking') without listing specific concrete actions, reducing its effectiveness for skill selection.

Suggestions

Add an explicit 'Use when...' clause, 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., 'Performs keyword research, optimizes app titles and descriptions, analyzes competitor listings, tracks ranking changes, and reviews store listing screenshots.'

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 optimization, review analysis, or screenshot 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, missing 'Use when' caps completeness at 2, and the 'what' is also not very detailed, 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 variations a user might mention.

3 / 3

Distinctiveness Conflict Risk

ASO is a clearly defined niche with distinct terminology (App Store, Google Play, ASO). It is 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
boisenoise/skills-collections
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.