apple-aso
Optimize Apple App Store metadata in store.config.json for ASO (App Store Optimization). Use when working with store.config.json, App Store keywords, titles, subtitles, descriptions, or localizing app metadata. Helps maximize app visibility and downloads.
84
77%
Does it follow best practices?
Impact
96%
1.33xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/apple-aso/SKILL.mdQuality
Discovery
89%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 a solid skill description with excellent trigger terms and completeness. It clearly identifies its niche (Apple App Store metadata optimization via store.config.json) and provides explicit 'Use when' guidance. The main weakness is that the specific actions could be more concrete—listing discrete operations like 'generate keyword lists, write titles and subtitles within character limits, craft promotional text' rather than the general 'optimize' and the fluffy 'helps maximize visibility and downloads'.
Suggestions
Replace the vague 'Helps maximize app visibility and downloads' with concrete actions like 'generates keyword lists, writes titles/subtitles within character limits, crafts promotional text, and validates metadata constraints'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (App Store metadata optimization) and mentions specific fields like keywords, titles, subtitles, descriptions, and localization, but doesn't list multiple concrete actions beyond 'optimize' and 'localize'. 'Helps maximize app visibility and downloads' is somewhat vague/fluffy. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize Apple App Store metadata in store.config.json for ASO) and 'when' (explicit 'Use when...' clause listing specific triggers like working with store.config.json, App Store keywords, titles, subtitles, descriptions, or localizing app metadata). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'store.config.json', 'App Store keywords', 'titles', 'subtitles', 'descriptions', 'ASO', 'App Store Optimization', 'localizing app metadata'. These cover a good range of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Apple App Store metadata optimization specifically in store.config.json. The combination of ASO, store.config.json, and App Store-specific terms makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, domain-specific skill with genuinely useful ASO knowledge that Claude wouldn't inherently possess—character limits, cross-localization tricks, keyword formatting rules. The before/after example is excellent and highly actionable. Main weaknesses are the monolithic structure (language code tables and full schema could be in reference files) and the validation workflow lacking explicit feedback loops or tooling for error recovery.
Suggestions
Add explicit validation feedback loops in Step 4, e.g., 'If keywords exceed 100 chars: remove lowest-priority terms from the end and re-count' with a concrete character-counting approach.
Move the language codes table and full store.config.json schema into separate reference files (e.g., LANGUAGE_CODES.md, SCHEMA.md) and link to them from the main skill to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and contains domain-specific knowledge Claude wouldn't inherently know (character limits, cross-localization rules, keyword formatting). However, some sections are verbose—the 'When to Use' section restates the obvious, the localization language codes table is lengthy reference material that could be linked, and some explanations like 'Does it describe your app?' are unnecessary padding. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready examples including the store.config.json schema, before/after keyword optimization examples with specific JSON, exact character limits, precise formatting rules (no spaces after commas), and executable CLI commands (eas metadata:push/pull). The guidance is specific and directly usable. | 3 / 3 |
Workflow Clarity | The 4-step optimization workflow is clearly sequenced with checklists, but the validation step (Step 4) is just a checklist without explicit tooling or feedback loops. There's no 'if validation fails, do X' recovery path. The workflow describes what to check but not how to programmatically validate or recover from issues. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and tables, but it's a long monolithic file (~180 lines) with reference material (language codes table, full schema) that could be split into separate files. The Resources section links to external docs but the inline content itself could benefit from being split into a quick-start overview and detailed reference files. | 2 / 3 |
Total | 9 / 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
- vabole/apple-skills
- Commit
ad0c7a7
- 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.