aso

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 14a43c1c0c04 · 20 Oct 2026Report an issue or request a re-scan

• Publisherarnabbagxd GitHub userOwner of the repository this skill is read from
• Source folderarnabbagxd/brand-building-skills/skills/asoThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict14a43c1c0c04A new audit runs when the source changes
• Repository statusNot archivedLast push 129 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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)…

---
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
- Note which keywords they rank for that you don't
- Identify gaps — keywords they're not using that you could own

**Step 3 — Keyword scoring:**
Rate each keyword on:
- **Volume**: How many people search for this? (high/medium/low)
- **Competition**: How hard is it to rank? (high/medium/low)
- **Relevance**: How closely does it match the app?

**Priority**: Medium volume + low competition + high relevance (the sweet spot)

**Keyword placement — where they count:**
- **App name/title**: Highest weight — put primary keyword here
- **Subtitle** (iOS) / **Short description** (Android): Second highest — secondary keywords
- **Keyword field** (iOS only, 100 chars): Additional keywords — no spaces, use commas
- **Long description**: Helps on Google Play (more like SEO); lesser on iOS

---

### 02 — TITLE AND SUBTITLE OPTIMIZATION

**App title formula:**
`[Brand Name] — [Primary Keyword + Value Proposition]`

Examples:
- "Calm — Sleep & Meditation" (brand + primary keyword + secondary use)
- "YNAB — Budget & Finance" (brand + category keyword)
- "Headspace: Mindful Meditation" (brand + adjective + keyword)

**Rules:**
- iOS: Max 30 characters
- Android: Max 30 characters (title) + 80 characters (short description)
- Include the single most important keyword in the title
- Don't keyword stuff — it hurts ranking and looks spammy

**Subtitle (iOS) / Short description (Android):**
- Expand on the primary value proposition
- Include secondary keywords naturally
- 30 characters (iOS) / 80 characters (Android)
- This is the first text users read — make it clear and benefit-focused

---

### 03 — DESCRIPTION OPTIMIZATION

**Structure for maximum conversion:**

**First 2 lines (above "More" fold):**
The most important — most users don't tap "more." Must communicate:
- What the app does in plain language
- The primary benefit (not feature)

**Body copy (below fold):**
- 3–5 key features as short paragraphs
- Social proof (ratings, awards, press mentions)
- Use case examples ("perfect for runners who...")
- Call to action at the end

**Description rules:**
- iOS: The App Store description does NOT directly affect search ranking (keywords here don't count for iOS ASO). Focus on conversion.
- Google Play: Description DOES affect ranking. Include keywords naturally throughout.
- Use line breaks and emoji to aid scannability
- Keep paragraphs to 2–3 sentences max

---

### 04 — SCREENSHOTS AND PREVIEW VIDEO

Screenshots are the #1 conversion driver. Users decide to download (or not) based on screenshots more than any other element.

**Screenshot strategy:**

**Screenshot 1 (hero):**
The most important. Many users only see this one.
- Feature the app's core value proposition visually
- Include a short headline (3–6 words)
- Show the best-looking screen of the app

**Screenshots 2–8:**
Tell a story. Each screenshot = one benefit or feature.
- Screenshot 2: Second most important feature
- Screenshot 3–5: Supporting features/use cases
- Screenshot 6–8: Social proof, awards, or final CTA

**Screenshot best practices:**
- Portrait orientation performs better on most apps (matches phone use)
- Dark mode versions often perform better — test both
- Include device frame or go frameless (test this)
- Use consistent color system that matches brand
- Text on screenshots: max 6–8 words, large enough to read on mobile

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/arnabbagxd/brand-building-skills
git -C brand-building-skills checkout 14a43c1c0c04

Works in

1. 2026-10-20
   ✓SAFE B 89 / 100

   first audit · source 14a43c1c0c04

Questions about aso

• github.com/arnabbagxd/brand-building-skills/tree/main/skills/aso — the audited source at commit 14a43c1c0c04 and every finding aboveObserved · 20 Oct 2026

Spotted something wrong? Report a correction · Methodology