CtrlK
BlogDocsLog inGet started
Tessl Logo

category-positioning

When the user wants to choose, change, or evaluate their App Store / Google Play category and subcategory — including primary vs secondary category trade-offs, chart-rank competitive analysis, category-driven discoverability, and how category choice affects featuring eligibility. Use when the user mentions "which category", "App Store category", "primary category", "secondary category", "change my category", "Health & Fitness vs Lifestyle", "Productivity vs Utilities", "rank higher in a smaller category", "category chart", "subcategory", "Play Store category", or "should I switch categories". For full ASO health beyond category, see aso-audit. For competitor analysis within the chosen category, see competitor-analysis. For chart movements within categories, see market-movers.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

An actionable, domain-rich strategy skill with concrete frameworks and a copy-paste template. Its main gaps are the absence of an explicit validation/rollback checkpoint in the risky switch workflow and a lack of file-level progressive disclosure for reference material.

Suggestions

Add an explicit validation/rollback checkpoint to the switch workflow — e.g., a pre-switch go/no-go gate confirming the new category's top-100 floor via get_downloads_to_top, and a post-switch rollback trigger if chart rank drops below a defined threshold within the re-index window.

Move the full category enumeration and Category-Specific Notes table into a references/ file (e.g. references/categories.md) and link to it from SKILL.md, keeping the body as overview + framework.

Add a short 'Verify' step in the Mechanics of Switching table (e.g., confirm the category change took effect in App Store Connect / Play Console before starting monitoring) to give the workflow an explicit feedback loop.

DimensionReasoningScore

Conciseness

The body is dense with app-store-specific domain knowledge (category lists, trade-off tables, switch mechanics, Appeeky tool reference) and contains no filler explaining concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Concrete, executable guidance throughout: a weighted scoring framework, decision tables with default answers, exact App Store Connect/Play Console paths, a named tool call (get_downloads_to_top), and a copy-paste output template.

3 / 3

Workflow Clarity

The process is sequenced (assess → score candidates → decide → switch plan) with decision criteria, but a category switch resets chart position and carries a 4–8 week re-indexing cost, and there is no explicit validation/rollback checkpoint — only an implicit post-switch monitoring mention.

2 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a single monolithic file with no bundle references, and reference-style content (the full category enumeration and Category-Specific Notes) is inline rather than split into a separate reference file.

2 / 3

Total

10

/

12

Passed

Description

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.

A strong, third-person description that concretely states capabilities, gives rich natural trigger phrases, and cleanly separates its niche from adjacent skills. It fully answers both 'what' and 'when' with no padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'choose, change, or evaluate their App Store / Google Play category and subcategory' plus 'primary vs secondary category trade-offs, chart-rank competitive analysis, category-driven discoverability, and how category choice affects featuring eligibility' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (choose/change/evaluate category and the trade-off analyses) and when via an explicit 'Use when the user mentions...' clause, matching the top anchor.

3 / 3

Trigger Term Quality

Provides extensive natural phrases a user would actually say ('which category', 'change my category', 'Health & Fitness vs Lifestyle', 'rank higher in a smaller category', 'should I switch categories'), giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

A clear niche (App Store/Play category positioning) with distinct triggers, and it explicitly differentiates from sibling skills (aso-audit, competitor-analysis, market-movers), making conflicts unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
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.