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 ./plugins/antigravity-awesome-skills-claude/skills/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 distinctive niche (ASO for mobile apps) with relevant platform names, but it lacks specific concrete actions and critically omits any 'Use when...' trigger guidance. The high-level verbs 'researching, optimizing, and tracking' are too generic to help Claude understand the full scope of capabilities.
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 Apple App Store or Google Play.'
Replace generic verbs with specific actions, e.g., 'Researches app keywords, writes optimized app titles and descriptions, analyzes competitor listings, tracks keyword rankings and download metrics.'
Include common user-facing trigger terms like 'app keywords', 'app ranking', 'app listing', 'app metadata', 'app reviews', and 'app downloads'.
| Dimension | Reasoning | Score |
|---|---|---|
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 writing, screenshot optimization, or review analysis. | 2 / 3 |
Completeness | Describes what it 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, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes good terms like 'App Store Optimization', 'ASO', 'Apple App Store', 'Google Play Store', and 'mobile app', but misses common user phrases like 'app keywords', 'app ranking', 'app metadata', 'app listing', or 'app downloads'. | 2 / 3 |
Distinctiveness Conflict Risk | ASO is a clearly defined niche with distinct terminology (App Store, Google Play, mobile app performance). It's unlikely to conflict with other skills given the specific domain focus on 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 a comprehensive but entirely descriptive document that reads more like a marketing brochure or knowledge base article about ASO than an actionable skill for Claude. It references numerous Python scripts that don't exist in the bundle, provides no executable code, and lacks any clear workflow with validation steps. The extreme verbosity (~400+ lines) wastes token budget on information Claude already knows or could easily infer.
Suggestions
Replace the extensive capability listings with a concise workflow: define 2-3 core tasks (e.g., 'optimize metadata', 'analyze competitors') with clear step-by-step sequences and validation checkpoints.
Either include the referenced Python scripts in the bundle or remove the Scripts section entirely—listing function signatures for non-existent files provides no value.
Cut the content by 70%+ by removing generic ASO best practices Claude already knows (e.g., 'respond to reviews within 24-48 hours', 'write for humans first') and focus only on specific, non-obvious instructions.
Split remaining content into separate files (e.g., PLATFORM_REQUIREMENTS.md for character limits, INPUT_SCHEMAS.md for JSON formats) and keep SKILL.md as a brief overview with clear references.
| Dimension | Reasoning | Score |
|---|---|---|
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 descriptive 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, commands, or real tools are provided. | 1 / 3 |
Workflow Clarity | No clear multi-step workflow is defined. The skill lists capabilities and best practices but never sequences them into an actionable process with validation checkpoints. There's no 'do step 1, then step 2, validate, then step 3' structure. The 'How to Use' section is just example prompts, not a workflow. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files to reference. Everything is crammed into a single massive SKILL.md. The scripts section references files that don't exist. Content that could be split into separate reference files (platform requirements, best practices, input schemas) is all inline, making the document overwhelming. | 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
- sickn33/antigravity-awesome-skills
- Commit
43af20c
- 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.