Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
54
Quality
31%
Does it follow best practices?
Impact
94%
1.22xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-app-store-optimization/SKILL.mdQuality
Discovery
40%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 establishes a clear domain (ASO for mobile apps) with good distinctiveness, but suffers from lack of explicit trigger guidance and insufficiently specific actions. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about app store rankings, app keywords, app metadata optimization, or improving app visibility on Apple App Store or Google Play'
Replace generic verbs ('researching, optimizing, tracking') with specific actions like 'analyze keyword rankings, generate optimized app titles and descriptions, track competitor apps, audit app store listings'
Include additional natural trigger terms users might say: 'app keywords', 'app rankings', 'app store listing', 'app visibility', 'app downloads'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ASO, App Store, Google Play) and mentions general actions ('researching, optimizing, and tracking'), but doesn't list specific concrete actions like 'analyze keyword rankings', 'generate metadata', or 'compare competitor apps'. | 2 / 3 |
Completeness | Describes what the skill does (ASO toolkit for researching/optimizing/tracking) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'App Store Optimization', 'ASO', 'Apple App Store', 'Google Play Store', and 'mobile app', but misses common user variations like 'app keywords', 'app rankings', 'app metadata', 'app store listing', or 'play store optimization'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on mobile app store optimization with distinct platform mentions (Apple App Store, Google Play Store). Unlikely to conflict with general marketing, SEO, or other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a comprehensive ASO guide or documentation than an actionable skill for Claude. It's extremely verbose, explaining concepts Claude already understands, while lacking executable code or clear step-by-step workflows. The script descriptions list functions without implementations, making them unusable.
Suggestions
Remove explanatory content about what ASO is and basic concepts - focus only on specific instructions Claude needs to execute tasks
Provide actual executable Python code for the scripts instead of just listing function names and descriptions
Create clear numbered workflows with validation steps for key processes like 'Optimize App Listing' or 'Conduct Keyword Research'
Split into multiple files: keep SKILL.md as a concise overview (<100 lines) with links to detailed references for platform requirements, best practices, and script implementations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already knows (what ASO is, what keywords are, basic marketing concepts). The document is over 400 lines with significant padding that doesn't add actionable value. | 1 / 3 |
Actionability | Provides JSON input schemas and lists script functions, but no actual executable code. Scripts are described with function signatures but no implementation. The 'How to Use' section shows prompts rather than concrete steps Claude should take. | 2 / 3 |
Workflow Clarity | No clear multi-step workflows with validation checkpoints. Lists capabilities and best practices but doesn't sequence them into actionable processes. Missing feedback loops for iterative optimization tasks. | 1 / 3 |
Progressive Disclosure | Content is organized into sections but everything is in one massive file. References scripts that don't exist or aren't linked. Could benefit from splitting detailed sections (platform requirements, best practices) into separate reference files. | 2 / 3 |
Total | 6 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
5c5ae21
Table of Contents
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.