app-store-optimization
tessl i github:alirezarezvani/claude-skills --skill app-store-optimizationComplete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
Validation
81%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Implementation
27%This skill is extremely verbose and reads more like a comprehensive ASO guide or documentation than an actionable skill for Claude. It explains many concepts Claude already knows, describes scripts without providing implementations, and dumps all content into a single massive file. The content would benefit from dramatic reduction, actual executable code, and splitting detailed references into separate files.
Suggestions
Reduce content by 80%+ by removing explanations of basic concepts (what ASO is, what keywords are) and keeping only project-specific configurations and actionable instructions
Provide actual executable Python code for the described scripts instead of just listing function names and descriptions
Split detailed content (best practices, platform requirements, input/output schemas) into separate reference files and link to them from a concise SKILL.md overview
Add explicit workflow sequences with validation checkpoints, e.g., 'After generating metadata, validate character counts -> if over limit, truncate -> verify keyword inclusion -> output final version'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with extensive explanations of concepts Claude already knows (what ASO is, what keywords are, basic marketing concepts). Lists capabilities, best practices, and limitations that are general knowledge rather than actionable specifics. | 1 / 3 |
Actionability | Provides JSON input schemas and describes script functions, but no actual executable code is shown. Scripts are described with function signatures but no implementation. The 'How to Use' section shows prompts rather than concrete steps Claude should take. | 2 / 3 |
Workflow Clarity | Best practices sections list steps but lack explicit validation checkpoints or feedback loops. No clear sequence for multi-step ASO processes like 'research -> optimize -> test -> iterate' with verification at each stage. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. No references to external files for detailed content. The entire skill dumps all information (capabilities, inputs, outputs, scripts, best practices, limitations) into one massive document instead of organizing into separate reference files. | 1 / 3 |
Total | 6 / 12 Passed |
Activation
55%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 mentioned 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 |
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.