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 domain (ASO for mobile apps) but lacks the concrete action details and explicit trigger guidance needed for Claude to reliably select it. The high-level framing ('researching, optimizing, and tracking') is too abstract, and the absence of a 'Use when...' clause is a significant gap.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about app store rankings, keyword optimization, app metadata, app listing improvements, or mobile app visibility.'
List specific concrete actions such as 'keyword research, metadata optimization, competitor analysis, review monitoring, screenshot/creative guidance, and ranking tracking' instead of the generic 'researching, optimizing, and tracking'.
Include additional natural trigger terms users might say, such as 'app keywords', 'app ranking', 'app reviews', 'app listing', 'Play Store optimization', or 'iOS app visibility'.
| 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, placing this at 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-facing variations like 'app keywords', 'app ranking', 'app metadata', 'app reviews', or 'app listing'. | 2 / 3 |
Distinctiveness Conflict Risk | ASO is a clearly defined niche with distinct terminology (App Store, Google Play, mobile app performance). It is unlikely to conflict with other skills given the specificity of the domain. | 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 shallow catalog of ASO topics that reads more like a marketing brochure or course syllabus than actionable instructions for Claude. It references numerous Python scripts that don't exist in the bundle, provides no executable code, and explains many concepts Claude already knows. The extreme verbosity (~400+ lines) delivers very little unique, actionable value.
Suggestions
Remove all generic ASO knowledge Claude already knows (best practices, what reviews are, basic marketing concepts) and focus only on specific, novel instructions or decision frameworks.
Either include the referenced Python scripts (keyword_analyzer.py, metadata_optimizer.py, etc.) in the bundle or remove references to them entirely—phantom references destroy trust in the skill.
Replace the abstract JSON input/output schemas with a concrete end-to-end workflow: e.g., 'Given an app name and category, follow these 5 steps to produce optimized metadata' with actual executable examples.
Split the content: keep SKILL.md as a concise overview (<80 lines) with clear pointers to separate files for platform-specific requirements, best practices, and detailed templates.
| 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 or commands are provided—everything is abstract description. | 1 / 3 |
Workflow Clarity | There is no clear multi-step workflow with sequencing or validation checkpoints. The skill reads as a reference catalog of ASO topics rather than a process to follow. No feedback loops, no error handling, no verification steps. The 'How to Use' section provides isolated prompt examples but no connected workflow for accomplishing ASO tasks. | 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 for detailed content. The skill references scripts (keyword_analyzer.py, metadata_optimizer.py, etc.) that don't exist in the bundle. No meaningful content splitting or navigation structure. | 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
431bfad
- 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.