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
46
20%
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 identifies a clear and distinct niche (ASO for Apple App Store and Google Play Store), which helps with distinctiveness. However, it lacks specific concrete actions beyond high-level verbs ('researching, optimizing, tracking') and critically omits any 'Use when...' guidance, making it harder for Claude to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about app store rankings, app keywords, app listing optimization, or improving app visibility on app stores.'
List specific concrete actions such as 'keyword research, metadata optimization, competitor analysis, review monitoring, screenshot/creative guidance, and ranking tracking' to improve specificity.
Include additional natural trigger terms users might say, such as 'app ranking', 'app keywords', 'app listing', 'app downloads', 'app visibility', or 'Play Store optimization'.
| Dimension | Reasoning | Score |
|---|---|---|
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 the skill does 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 only moderately detailed, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'App Store Optimization', 'ASO', 'Apple App Store', 'Google Play Store', and 'mobile app', but misses common user variations like 'app keywords', 'app ranking', 'app metadata', 'app listing', or 'app reviews'. | 2 / 3 |
Distinctiveness Conflict Risk | ASO is a clearly defined niche with specific platform references (Apple App Store, Google Play Store). This is unlikely to conflict with other skills given the distinct domain focus on mobile app store optimization. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
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. It suffers from extreme verbosity, explaining many things Claude already knows while failing to provide any executable code or concrete workflows. The referenced scripts list function signatures without implementations, and the overall structure is a monolithic document that would be far more effective if condensed to essential, novel information with proper progressive disclosure.
Suggestions
Replace the capabilities catalog with a concise overview (under 30 lines) and move detailed guidance into separate referenced files (e.g., KEYWORDS.md, METADATA.md, REVIEWS.md)
Provide actual executable code for the referenced scripts instead of just listing function names and descriptions—at minimum include the core functions for metadata_optimizer.py and keyword_analyzer.py
Define clear step-by-step workflows for the 2-3 most common ASO tasks (e.g., 'Optimize a new app listing') with explicit validation checkpoints (e.g., character limit validation, keyword density check)
Remove sections that explain general knowledge Claude already has (best practices like 'respond to reviews within 24-48 hours', limitations about store algorithms being proprietary, integration suggestions) and focus only on novel, specific instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Extensively explains concepts Claude already knows (what ASO is, what reviews are, basic best practices like 'respond quickly to reviews'). The capabilities section is a massive bullet-point catalog that describes rather than instructs. Much of the content (best practices, limitations, integration sections) is general knowledge padding. | 1 / 3 |
Actionability | Despite listing many script files and functions, none contain actual executable code—only function signatures and descriptions. The 'How to Use' section is just example prompts, not actionable instructions. The JSON input/output schemas describe structure but provide no working implementation. The skill describes what could be done rather than providing concrete, executable guidance. | 1 / 3 |
Workflow Clarity | No clear multi-step workflow is defined. The skill is organized as a reference catalog of capabilities rather than a sequenced process. There are no validation checkpoints, no feedback loops, and no clear ordering of steps for any ASO task. The 'How to Use' section just shows example prompts without any workflow structure. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files despite mentioning 8 separate Python scripts that presumably exist elsewhere. All content is inline in one massive document with no clear navigation hierarchy. The document would benefit enormously from splitting into focused sub-documents with a concise overview. | 1 / 3 |
Total | 4 / 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 | |
- Repository
- boisenoise/skills-collections
- Commit
636b862
- 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.