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
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-code-skill-factory --skill app-store-optimization47
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 identifies a clear, distinctive domain (ASO for mobile apps) with good trigger terms that users would naturally use. However, it lacks specific concrete actions beyond generic verbs and critically omits any 'Use when...' guidance, making it harder for Claude to know exactly when to select this skill over others.
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'
Replace generic verbs with specific actions like 'analyze keyword rankings, optimize app titles and descriptions, track competitor apps, generate ASO reports'
| 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 but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all. | 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 ASO for mobile app stores. The combination of 'App Store Optimization', 'Apple App Store', and 'Google Play Store' creates distinct triggers unlikely to conflict with other 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 excessively verbose, treating Claude like a novice who needs extensive background on ASO concepts. It describes capabilities and scripts without providing executable code or clear workflows. The content would benefit from dramatic reduction, actual code examples, and splitting into multiple focused files.
Suggestions
Reduce content by 70%+ by removing explanations of basic ASO concepts Claude already knows (what keywords are, why ratings matter, etc.)
Provide actual executable Python code for the scripts instead of just listing function names and descriptions
Add a clear workflow with validation steps, e.g., '1. Run keyword research → 2. Validate relevance → 3. Optimize metadata → 4. Verify character limits → 5. Test with A/B framework'
Split into multiple files: keep SKILL.md as a concise overview, move scripts to SCRIPTS.md, best practices to BEST_PRACTICES.md, and platform requirements to PLATFORM_SPECS.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with extensive explanations of concepts Claude already knows (what ASO is, basic marketing principles). Lists capabilities, best practices, and limitations that are general knowledge rather than actionable specifics. | 1 / 3 |
Actionability | Provides JSON input schemas and example prompts, but the 'Scripts' section only describes functions without providing actual executable code. The guidance is more descriptive than instructive—tells what scripts do rather than showing how to use them. | 2 / 3 |
Workflow Clarity | No clear multi-step workflows with validation checkpoints. The 'How to Use' section provides isolated example prompts but no sequenced process for conducting ASO. Missing feedback loops for iterative optimization processes. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite being far too long. Could easily split scripts documentation, best practices, and platform requirements into separate reference files. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.