app-store-optimization
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
94
92%
Does it follow best practices?
Impact
95%
1.18xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete capabilities, includes a comprehensive 'Use when...' clause with natural trigger terms, and occupies a clearly distinct niche. The description is thorough without being unnecessarily verbose, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: researching keywords, analyzing competitor rankings, generating metadata suggestions, keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes. | 3 / 3 |
Completeness | Clearly answers both 'what' (ASO toolkit for researching keywords, analyzing competitors, generating metadata, etc.) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, mobile app marketing, iOS, Android, Apple App Store, Google Play Store, keyword research, competitor analysis. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche around App Store Optimization specifically. The domain-specific terminology (ASO, app store rankings, app metadata, Google Play Store, Apple App Store) makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, comprehensive ASO skill with strong actionability through concrete examples, platform-specific data, and executable script references. The workflow clarity is excellent with explicit validation steps at each stage. The main weakness is verbosity—some tables and sections contain general marketing knowledge that Claude already knows, and the overall length could be reduced by 20-30% without losing value.
Suggestions
Trim general marketing knowledge that Claude already knows (e.g., 'Launch Timing Considerations' table, 'Keyword Evaluation Criteria' weights) to reduce token usage while keeping platform-specific details.
Consolidate the before/after examples section—keep the keyword field optimization example (highly specific) but consider moving the more general title/description examples to a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite lengthy (~350+ lines) with some content that could be tightened. Tables like 'Keyword Evaluation Criteria' weights and 'Launch Timing Considerations' contain general marketing knowledge Claude already possesses. However, platform-specific details (character limits, iOS keyword field rules) earn their place. The before/after examples are valuable but could be more compact. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific character limits per platform, exact keyword field optimization rules (no spaces after commas, remove plurals), title formulas, before/after examples with analysis, sample size tables, script commands with arguments, and structured templates. The before/after keyword field example is particularly executable. | 3 / 3 |
Workflow Clarity | Each workflow has clearly numbered sequential steps with explicit validation checkpoints at the end (marked with **Validation:**). The A/B testing workflow includes statistical significance requirements, the metadata workflow includes character count validation, and the launch workflow has timeline-based milestones. Feedback loops are present (e.g., 'If errors: fix and re-validate' equivalent in the test workflow). | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear one-level-deep references to detailed materials (references/keyword-research-guide.md, references/platform-requirements.md, references/aso-best-practices.md). Scripts are listed with purpose and usage. Related skills are linked. Content is appropriately split between the main file and reference documents. | 3 / 3 |
Total | 11 / 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
- alirezarezvani/claude-skills
- Commit
967fe01
- 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.