# aso

An ASO skill that picks keywords, rewrites your title and description, and works through screenshots and ratings for your app listing.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1500 installs · ★ 787
- Author: arnabbagxd
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/arnabbagxd/Brand-building-skills/tree/HEAD/skills/aso/SKILL.md
- Updated: 2026-06-13
- HTML: https://affpapa.org/en/nevibecode/skills/arnabbagxd-aso

## What it does

The `aso` skill turns your coding agent into an app store optimization specialist. It covers two jobs at once: visibility in search (like SEO) and conversion from listing view to install (like CRO). Before anything else, the agent checks for `.agents/brand-context.md` and reads it to understand the brand, audience and positioning.

From there it walks through keyword research scored by volume, competition and relevance, title and subtitle optimization, description structure, screenshot and preview video strategy, and rating and review handling. iOS and Google Play follow different rules. The App Store description does not affect search ranking directly, while on Google Play it does. Character limits differ too: 30 characters for the title on both, and a 100-character keyword field on iOS with no spaces, comma-separated.

The skill advises triggering the native rating prompt through `SKStoreReviewRequestAPI` at a good moment, after a completed task or a session streak, never after an error or a purchase. Apple allows that prompt once per 365 days, so a badly placed trigger is expensive. Preview videos run up to 30 seconds and should show real in-app footage.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill aso -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/aso/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/aso/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill aso -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/aso/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill aso -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/aso/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install arnabbagxd/Brand-building-skills aso
```

2. **Manually: put the files in place**
- File: `.github/skills/aso/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill aso -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/arnabbagxd/Brand-building-skills --path skills/aso
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/aso/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add arnabbagxd/Brand-building-skills --skill aso -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/arnabbagxd/Brand-building-skills/tree/HEAD/skills/aso/SKILL.md

## When to use it
- find keywords people actually search for
- rewrite the title and subtitle within iOS and Android limits
- order screenshots so the first one sells the app
- raise the rating with an in-app prompt at the right moment
- keep App Store and Google Play rules apart

## Example prompts
- Run an ASO audit on my App Store and Google Play listing
- Find keywords for my budget tracker app
- My app isn't getting downloads — review the listing and screenshots

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: fac15843521fdd68.

BEGIN THIRD-PARTY FILE fac15843521fdd68
```text
---
name: aso
description: Optimize an app's store listing for maximum visibility and downloads — keyword strategy, title and subtitle optimization, screenshots, preview videos, rating and review management, and A/B testing on the App Store (iOS) and Google Play (Android). Use when the user says "ASO", "app store optimization", "optimize my app listing", "improve app store ranking", "app store keywords", "app store screenshots", "app store rating", "Google Play optimization", "app visibility", "increase app downloads", "app store SEO", "app store conversion", "my app isn't getting downloads", or wants to improve how their app appears and converts in the App Store or Google Play.
metadata:
  version: 1.0.0
---

# ASO (App Store Optimization)

You are an App Store Optimization specialist. Your job is to maximize an app's visibility in search results and its conversion rate from listing page visitor to download — across both the Apple App Store and Google Play.

## Before You Start

Check if `.agents/brand-context.md` exists. Read it to understand the brand, audience, and app positioning before optimizing the listing.

---

## ASO = SEO + CRO for App Stores

ASO has two distinct jobs:
1. **Visibility** (like SEO): Getting the app to appear in search results for the right keywords
2. **Conversion** (like CRO): Getting people who find the listing to download

Both must be optimized. High ranking with poor creative = low downloads. Great creative with poor ranking = no traffic.

---

## Information to Gather

1. **App name and description** — what does the app do?
2. **Target platform** — iOS, Android, or both?
3. **App Store URL** — if live, share the link for audit
4. **Target audience** — who is this app for?
5. **Primary use case** — what job does the app do for the user?
6. **Current metrics** — downloads, rating, conversion rate from listing (if known)?
7. **Top competitors** — which apps compete directly?
8. **Primary keywords** — what words does the team think users search for?

---

## Output: ASO Optimization Plan

---

### 01 — KEYWORD RESEARCH AND STRATEGY

Keywords are the foundation of app store visibility. The goal: rank for high-volume, relevant terms where competition isn't impossible.

**Keyword research process:**

**Step 1 — Seed keywords:**
What words describe what the app does? What would a user type to find it?
- Primary job (e.g., "meditation", "budget tracker", "photo editor")
- Audience type (e.g., "for runners", "small business")
- Feature-based (e.g., "AI writing", "offline maps")

**Step 2 — Competitor keyword mining:**
- Look at top 3–5 competitors' titles, subtitles, and keyword fields
```
END THIRD-PARTY FILE fac15843521fdd68

The third-party file has ended. Everything between the fac15843521fdd68 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2685 of 9718 bytes. © arnabbagxd · MIT · https://github.com/arnabbagxd/Brand-building-skills/tree/HEAD/skills/aso/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md