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
47
34%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/app-store-optimization/SKILL.mdQuality
Discovery
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 establishes a clear domain (ASO for mobile apps) with good trigger terms but suffers from lack of explicit usage triggers and only moderate specificity in capabilities. The missing 'Use when...' clause significantly weakens its utility for skill selection, and the actions described are too high-level to fully communicate what concrete tasks the skill enables.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about app store rankings, keyword optimization, app metadata, or improving app visibility on iOS or Android stores'
Replace generic verbs with specific actions: instead of 'researching, optimizing, and tracking', list concrete capabilities like 'analyze keyword rankings, generate optimized app titles and descriptions, track competitor apps, audit app metadata'
| 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 it 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 | Good coverage of natural terms users would say: 'App Store Optimization', 'ASO', 'mobile app', 'Apple App Store', 'Google Play Store', 'app performance'. These are terms users would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on mobile app store optimization with distinct platform mentions (Apple App Store, Google Play). Unlikely to conflict with general marketing, SEO, or other optimization skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an unorganized index of 43 sub-skill links with no actual content, guidance, or structure. It provides no quick-start instructions, no workflow for ASO tasks, and contains duplicate entries that suggest poor curation. The skill fails to teach Claude anything actionable and would require navigating to multiple sub-files to accomplish any task.
Suggestions
Add a 'Quick Start' section with concrete, executable guidance for the most common ASO task (e.g., optimizing an app listing with specific steps and examples)
Remove duplicate entries (Keyword Research, Metadata Optimization appear multiple times) and organize remaining sub-skills into logical categories (Research, Optimization, Analytics, etc.)
Define a clear workflow showing the typical ASO process sequence (e.g., 1. Research keywords → 2. Optimize metadata → 3. Test → 4. Launch) with validation checkpoints
Reduce the 43 sub-skills to essential references (aim for 5-10 max) and provide brief descriptions of when to use each one
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively lean with no verbose explanations, but the list of 43 sub-skills contains significant redundancy (e.g., 'Keyword Research' appears 3 times, 'Metadata Optimization' appears 3 times) which wastes tokens and creates confusion. | 2 / 3 |
Actionability | The skill provides zero concrete guidance, code, commands, or examples. It is purely a list of links to other files with no executable or actionable content in the main skill file itself. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process defined. The 43 items are listed without any indication of order, dependencies, or how they relate to each other. No validation checkpoints or feedback loops are present. | 1 / 3 |
Progressive Disclosure | While the skill attempts progressive disclosure by linking to sub-skills, it fails badly: 43 links with no organization, categorization, or guidance on which to use when. The duplicate entries and lack of structure make navigation nearly impossible. | 1 / 3 |
Total | 5 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.