Name: app-store-optimization
Rating: 51.2 (1 reviews)
Author: sickn33

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

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/app-store-optimization/SKILL.md

Quality

Content

42%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is comprehensive and well-sectioned but verbose and largely instructional rather than executable, with no real bundle files despite referencing eight scripts. Workflows lack explicit validation checkpoints and the content is not split across reference files.

Suggestions

Trim generic best-practice and integration prose that restates common ASO knowledge, and consolidate the repeated 'Hey Claude' example prompts into a single representative pattern.

Either provide the eight referenced scripts in a ./scripts/ bundle with real implementations, or remove the script section and inline the concrete executable guidance directly.

Add an explicit sequenced workflow (e.g., research keywords -> optimize metadata -> validate character limits -> A/B test -> launch) with validation checkpoints for store-listing changes.

Dimension	Reasoning	Score
Conciseness	The ~400-line body is noticeably verbose, restating general ASO best practices Claude likely already knows and repeating the 'Hey Claude—I just added...' boilerplate seven times, with padded sections (Integration, Version & Updates, lengthy Best Practices lists).	2 / 5
Actionability	Concrete JSON input/output schemas and platform character limits are provided, but the eight referenced scripts are described only by function-name listings with no executable code or invocation commands, leaving guidance incomplete.	3 / 5
Workflow Clarity	Capabilities and outputs are organized by topic and a pre-launch checklist exists, but there is no sequenced multi-step workflow with explicit validation checkpoints or feedback loops for consequential store-listing changes.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but the entire reference material (capabilities, I/O formats, best practices) is inlined in one monolithic SKILL.md, and the eight referenced script files do not exist in any bundle directory.	3 / 5
	Total	11 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is specific and well-targeted to a distinct niche, with good natural keyword coverage. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when optimizing app store listings, researching app keywords, or improving app rankings on the Apple App Store or Google Play Store').

Add a few natural synonym trigger terms such as 'app ranking', 'app keywords', and 'store listing' to broaden trigger coverage.

Consider naming a couple of more specific actions (e.g., 'keyword research', 'metadata optimization', 'A/B testing') in place of the generic verbs.

Dimension	Reasoning	Score
Specificity	Names the ASO domain plus three concrete action verbs ('researching, optimizing, and tracking') and both target platforms, listing several specific actions with only minor gaps in coverage.	4 / 5
Completeness	Clearly states what the skill does, but lacks any 'Use when...' trigger clause; per the judging guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('App Store Optimization', 'ASO', 'Apple App Store', 'Google Play Store', 'mobile app'), but misses common variations like 'app ranking' or 'app keywords'.	4 / 5
Distinctiveness Conflict Risk	ASO on the Apple App Store and Google Play Store is a clear, distinct niche with specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/app-store-optimization/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.