app-store-optimizer
Expert app store marketing specialist focused on App Store Optimization (ASO), conversion rate optimization, and app discoverability
28
11%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./marketing-app-store-optimizer/skills/SKILL.mdQuality
Discovery
22%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 description reads more like a job title or role description than a functional skill description. It lacks concrete actions, has no 'Use when...' trigger clause, and uses first-person framing ('Expert... specialist') rather than describing what the skill does. While the ASO domain is somewhat distinctive, the description needs significant improvement to be useful for skill selection.
Suggestions
Replace the role-based framing with specific concrete actions, e.g., 'Generates optimized app store titles, descriptions, and keyword sets. Analyzes competitor listings and suggests screenshot strategies.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs help with app store listings, ASO, app keywords, App Store or Google Play optimization, or improving app download rates.'
Remove the 'Expert... specialist' phrasing and use third-person action verbs to describe capabilities directly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain (app store marketing) and mentions broad concepts like ASO, conversion rate optimization, and discoverability, but does not list any concrete actions (e.g., 'write app descriptions', 'generate keyword lists', 'optimize screenshots'). These are abstract categories, not specific capabilities. | 1 / 3 |
Completeness | The description partially addresses 'what' (though vaguely) but completely lacks any 'when' guidance — there is no 'Use when...' clause or equivalent explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also weak, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'App Store Optimization', 'ASO', 'app discoverability', and 'conversion rate optimization' that users might mention. However, it misses common natural variations like 'app store listing', 'app keywords', 'app description', 'Google Play', 'App Store screenshots', or 'app ranking'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on app store marketing and ASO is a reasonably specific niche, but the broad terms like 'conversion rate optimization' could overlap with general marketing or analytics skills. The lack of concrete actions makes it harder to distinguish from other marketing-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill file is a persona/role-play prompt rather than an actionable skill document. It is extremely verbose, filled with placeholder templates and abstract marketing concepts that Claude already understands, while providing zero concrete tools, APIs, commands, or executable examples. The content would need a fundamental restructuring to serve as a useful skill—replacing persona framing with specific instructions, adding real examples, and breaking templates into separate referenced files.
Suggestions
Replace the persona/identity framing with direct, actionable instructions—Claude doesn't need to be told it's 'data-driven' or 'results-obsessed'; instead specify exact steps and tools to use for ASO tasks.
Add concrete, executable examples: show a completed keyword research output with real data, a fully written app store description, or specific tool commands (e.g., using App Annie, Sensor Tower APIs) rather than bracketed placeholders.
Extract the large template blocks (ASO Strategy Framework, Visual Asset Strategy, Deliverable Template) into separate referenced files to reduce the main skill file to a concise overview with clear navigation.
Define a concrete workflow with validation checkpoints—e.g., 'After generating keywords, verify search volume using [specific method], then validate relevance by checking top 10 results for each term.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with content Claude already knows. The file is essentially a persona definition with extensive template scaffolding that explains basic marketing concepts (what A/B testing is, what keywords are, etc.). Most sections are placeholder templates with bracketed fields rather than actionable content, and the 'personality' framing adds significant token overhead without value. | 1 / 3 |
Actionability | Almost entirely abstract and descriptive rather than instructive. The 'workflow' steps are vague directives like 'Research app store landscape' with no concrete tools, commands, APIs, or executable examples. Templates contain only placeholder brackets like '[Primary Keyword 1]' with no real examples of completed optimizations. The bash code block contains only comments. | 1 / 3 |
Workflow Clarity | The 4-step workflow is extremely high-level with no validation checkpoints, no concrete sequencing of actual tasks, and no feedback loops. Steps like 'Execute metadata optimization across all app store elements' provide no guidance on how to actually perform the work or verify results. There are no error recovery paths or decision points. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Everything is inlined in a single massive document including multiple large template blocks that could be separate files. The final line references 'core training' which is vague and unhelpful. No clear navigation structure or content hierarchy that aids discovery. | 1 / 3 |
Total | 4 / 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
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.