App Store Optimization Basics — Keywords, Screenshots & Ratings

Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/aso-playbook.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit Gingiris-1031/gingiris-skills/skills/aso-playbook#main ~/.claude/skills/aso-playbook

For one project only, change the path to .claude/skills/aso-playbook.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of App Store Optimization Basics — Keywords, Screenshots & Ratings

Show the full text77 lines
namedescriptionsourcetags
aso-playbook| Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/aso-playbook - aso - app-store-optimization - mobile-growth - keyword-research - app-marketing - app-store - ios - android - app-ranking - organic-growth - claude-code - ai-agent-skill - indie-developer - conversion-optimization - latest

📦 Install

clawhub install aso-playbook

What you get after installing:

  • Keyword research methodology for finding low-competition, high-intent terms
  • Screenshot hypothesis and message-hierarchy framework
  • A/B testing and evidence-capture framework for iOS and Android

App Store Optimization Basics — Keywords, Screenshots & Ratings

🌍 Language / 语言: 中文 | English | 日本語 | 한국어

The fundamentals of ASO for developers who'd rather build than market — but need downloads.

  • Keyword research: Finding low-competition, high-intent keywords for your category
  • Screenshot optimization: Turn user intent into testable screenshot hypotheses
  • Rating strategy: How to ask for reviews without annoying users
  • Localization basics: Which markets to target first and how to test
  • A/B testing: What to test, how long to run, and interpreting results

Minimum viable ASO workflow

  1. Export the last 28 days by country and traffic source: impressions, product-page views, first-time downloads, conversion rate, proceeds, D1/D7/D30 retention.
  2. Build a keyword sheet with relevance, current rank, search popularity, competition, destination locale and target page.
  3. Change one variable family at a time: metadata, icon, first three screenshots, preview video, rating prompt or localization.
  4. Record the exact before/after version, release date, storefront and external UA activity.
  5. Keep a test only when conversion improves without a material decline in retained users, rating quality or revenue.
Evidence gate

Do not claim an ASO win from downloads alone. A valid case needs, at minimum:

  • keyword rank or search-impression change;
  • impression → product-page-view rate;
  • product-page-view → first-time-download rate;
  • D7 or D30 retained-user outcome;
  • dates, storefronts, app version and paid-campaign overlap.

No controlled Gingiris App Store before/after dataset is bundled with this skill yet. The workflow is executable; any uplift claim must come from the user's own App Store Connect or Play Console export.

Compliance gate

Never recommend bought ratings/reviews, artificial searches or installs, device/account farms, chart manipulation, or packages intended to evade enforcement. Use official storefront experiments, authentic-user review prompts and transparent paid acquisition. Historical notes that mention black-hat tactics are research records, not execution guidance.

1---
2name: aso-playbook
3description: |
4 Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.
5source: https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/aso-playbook
6tags:
7 - aso
8 - app-store-optimization
9 - mobile-growth
10 - keyword-research
11 - app-marketing
12 - app-store
13 - ios
14 - android
15 - app-ranking
16 - organic-growth
17 - claude-code
18 - ai-agent-skill
19 - indie-developer
20 - conversion-optimization
21 - latest
22---
23 
24## 📦 Install
25 
26```bash
27clawhub install aso-playbook
28```
29 
30**What you get after installing:**
31- Keyword research methodology for finding low-competition, high-intent terms
32- Screenshot hypothesis and message-hierarchy framework
33- A/B testing and evidence-capture framework for iOS and Android
34 
35---
36 
37# App Store Optimization Basics — Keywords, Screenshots & Ratings
38 
39> 🌍 **Language / 语言**: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md)
40 
41The fundamentals of ASO for developers who'd rather build than market — but need downloads.
42 
43- **Keyword research**: Finding low-competition, high-intent keywords for your category
44- **Screenshot optimization**: Turn user intent into testable screenshot hypotheses
45- **Rating strategy**: How to ask for reviews without annoying users
46- **Localization basics**: Which markets to target first and how to test
47- **A/B testing**: What to test, how long to run, and interpreting results
48 
49## Minimum viable ASO workflow
50 
511. Export the last 28 days by country and traffic source: impressions, product-page views, first-time downloads, conversion rate, proceeds, D1/D7/D30 retention.
522. Build a keyword sheet with relevance, current rank, search popularity, competition, destination locale and target page.
533. Change one variable family at a time: metadata, icon, first three screenshots, preview video, rating prompt or localization.
544. Record the exact before/after version, release date, storefront and external UA activity.
555. Keep a test only when conversion improves without a material decline in retained users, rating quality or revenue.
56 
57### Evidence gate
58 
59Do not claim an ASO win from downloads alone. A valid case needs, at minimum:
60 
61- keyword rank or search-impression change;
62- impression → product-page-view rate;
63- product-page-view → first-time-download rate;
64- D7 or D30 retained-user outcome;
65- dates, storefronts, app version and paid-campaign overlap.
66 
67No controlled Gingiris App Store before/after dataset is bundled with this skill yet. The workflow is executable; any uplift claim must come from the user's own App Store Connect or Play Console export.
68 
69### Compliance gate
70 
71Never recommend bought ratings/reviews, artificial searches or installs, device/account farms, chart manipulation, or packages intended to evade enforcement. Use official storefront experiments, authentic-user review prompts and transparent paid acquisition. Historical notes that mention black-hat tactics are research records, not execution guidance.
72 
73## Related Gingiris Skills
74- Full version: https://clawhub.ai/gingiris-1031/skills/gingiris-aso-growth
75- All skills: https://clawhub.ai/gingiris-1031
76- Follow: [@WeiYipei on X](https://x.com/WeiYipei)
77 

Discussion

Alternatives

Also in App store (ASO)See all 364 in Marketing →