⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

aso

alexszczurek@alexszczurek⭐ 28 stars· last commit 11d ago· 0 open issues

Write, audit, or improve an iOS App Store listing — app name, subtitle, keyword field, screenshots, app icon, preview video, creative assets, tags, ratings strategy, localization, and featuring nominations. Use when creating or reviewing App Store metadata, doing keyword research, planning a metadata update, or when the user mentions ASO, App Store Optimization, app store listing, keywords, subtitle, screenshot captions, preview video, app icon, Liquid Glass, creative assets, product page header, search results creative, Asset Library, featuring, ratings prompt, or Apple Ads.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 28 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

before skills

Agent skills from before.click, the App Store design gallery.

A skill is a set of instructions your coding agent loads when it recognises the task. Instead of improvising an answer about App Store listings, it follows a fixed process, with rules and reasoning written down in advance.

Install

npx skills add alexszczurek/before-skills

Works with Claude Code, Cursor, and any agent that reads SKILL.md files. The installer asks where to put the skill: globally, so it is available in every project, or in the current project only.

To install one skill from this repo:

npx skills add alexszczurek/before-skills --skill aso

Skills

aso

Writes and audits iOS App Store listings: app name, subtitle, keyword field, screenshots, icon, preview video, tags, ratings, localisation, and featuring nominations.

Distilled from the before.click ASO guide and checked against Apple's 2025–2026 documentation, so it covers what changed since most ASO advice was written: Apple-confirmed screenshot indexing, AI-generated App Store tags, Liquid Glass icons, the shift toward semantic search, the App Store Review Guideline that prohibits competitor names in the keyword field, and App Review's rule that more than half of the screenshots in every device and language set must show the app in use. It also knows the current screenshot sizes, including iPhone Duo.

How to use it

Ask for what you want in plain language. The skill loads on its own when your request mentions App Store metadata, keywords, screenshots, ratings, or ASO:

  • "Audit my App Store listing" — walks the audit checklist in order, cheapest fix first
  • "Write a title and subtitle for my caffeine tracking app" — runs the keyword research procedure, then distributes terms across fields
  • "Is my keyword field any good?" — checks character count, formatting, duplicate words, and prohibited terms
  • "Will these screenshots pass review?" — counts in-use screenshots for every device and language set, and flags the ones that fail
  • "Plan my next metadata update" — separates what needs an app release from what you can change today

In Claude Code you can also invoke it directly with /aso.

What it does differently

Ask an agent about ASO without a skill and you get a different answer each time, some of it out of date. The skill fixes the process, not the answer.

It follows a procedure instead of guessing. Keyword research runs in six steps: brainstorm, check App Store autocomplete, extract competitor terms, score for volume and relevance and difficulty, group by search intent, then distribute across fields. It cannot skip to writing metadata from intuition.

Every rule carries its reason. "Singular forms only, because Apple matches plurals automatically, so the plural wastes characters." The reasoning lets the agent extend a rule to situations the skill never described.

Constraints are numbers, not adjectives. Fill at least 95 of 100 keyword characters. Three system rating prompts per year, total. Submit featuring nominations three weeks ahead. Judge a metadata change at two to four weeks, never the next day.

It knows what it cannot prove. Claims are marked as Apple-confirmed or industry inference, so the agent does not present a guess as documentation.

Contributing

Open an issue with the source, and the rule and its reasoning. Rules need evidence: Apple documentation, or data from a reputable ASO source.

License

MIT

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/aso/SKILL.md7.9 KBupstream ↗
    ---
    name: aso
    description: Write, audit, or improve an iOS App Store listing — app name, subtitle, keyword field, screenshots, app icon, preview video, creative assets, tags, ratings strategy, localization, and featuring nominations. Use when creating or reviewing App Store metadata, doing keyword research, planning a metadata update, or when the user mentions ASO, App Store Optimization, app store listing, keywords, subtitle, screenshot captions, preview video, app icon, Liquid Glass, creative assets, product page header, search results creative, Asset Library, featuring, ratings prompt, or Apple Ads.
    ---
    
    # App Store Optimization
    
    You are optimizing an iOS App Store listing. 70% of App Store visitors find apps through search and 65% of downloads happen immediately after a search — the listing does more selling than the landing page. Every rule below exists because the search algorithm indexes a small, known set of surfaces, and everything else is a conversion tool, not a discovery tool.
    
    ## The only fields that rank
    
    Apple indexes exactly 160 characters of owned keyword surface. Never spend effort "optimizing the description for keywords" — the description and promotional text (170 chars, updatable without a new version) are NOT indexed. They affect conversion, not discovery. The description still matters for one discovery mechanism: Apple's LLM generates App Store *tags* from the description and screenshots, so it must name the app's category and core use cases in plain words — for the tag generator, not for keyword rankings. Google also indexes the description on the web App Store (apps.apple.com), a second discovery channel Apple's own search ignores.
    
    | Field | Limit | Keyword weight | Visible to users |
    |---|---|---|---|
    | App Name | 30 chars | Highest | Yes |
    | Subtitle | 30 chars | Second | Yes |
    | Keyword Field | 100 chars | Third | No |
    
    Also indexed: category, screenshot content (Apple-confirmed at WWDC25 — extracted by AI analysis, not OCR), tags, and in-app event names (as reinforcement of existing keywords, see In-app events).
    
    Beyond text, Apple confirms downloads and ratings as ranking inputs (plus an unspecified "and more"). Retention and uninstall-rate demotion is officially documented only on Google Play, not iOS — treat it as likely, not confirmed. Either way, low retention starves download velocity, so the practical rule holds: ASO cannot fix a leaky product.
    
    **The zero-overlap rule:** never repeat a word across the name, subtitle, or keyword field. Apple combines tokens across all fields, so a duplicated word is a wasted slot that could have covered a new search query. When auditing a listing, check this first — it is the most common and cheapest-to-fix error.
    
    ## Ranking and conversion are separate jobs
    
    Every surface serves ranking (being found), conversion (being tapped and installed), or both. Optimizing the whole listing in one undifferentiated pass silently trades one against the other — the classic failure is packing keywords into a subtitle or screenshot caption, gaining rank and losing installs.
    
    | Surface | Ranking | Conversion |
    |---|---|---|
    | Keyword field | Yes | None — invisible to users |
    | App name | Highest weight | Yes |
    | Subtitle | Second weight | Yes |
    | Screenshots | Yes (AI-analyzed) | Primary driver |
    | Icon | None | Yes |
    | Preview video | None | Yes |
    | Product page header | None | Yes |
    | Search results creative | None | Yes |
    | Ratings | Yes | Yes |
    
    Rules that follow from this split:
    
    - **Diagnose before optimizing.** Low impressions = a ranking problem; high impressions with low conversion = a conversion problem. Never accept "optimize my listing" as one undifferentiated task — establish which axis is broken, and say so before changing anything.
    - **Spend pure-ranking effort in the keyword field first.** It is invisible, so it cannot cost conversion. Fill all 100 characters before pushing any keyword into a user-visible field.
    - **On dual-purpose surfaces (name, subtitle, screenshots), readability wins ties.** These are read by a human deciding whether to tap, and semantic search now penalizes stuffing directly — so a ranking gain bought with awkward copy loses twice.
    - **Name the trade.** When a change helps one axis and risks the other, state the cost instead of presenting the change as a pure win.
    
    ## Think in intent clusters, not keywords
    
    Apple's search increasingly interprets the semantic intent behind a query instead of matching literal tokens — it evaluates whether an app *satisfies* the query, and can rank you for terms you never targeted. Keyword-stuffed metadata now loses to natural-language metadata that clearly states what the app does. Consequences:
    
    - Group keyword candidates into intent clusters (what the user is trying to accomplish) and make metadata answer the intent in plain language, not enumerate tokens.
    - Prefer long-tail, high-intent queries over head terms: "remove background from photo" converts better than "photo editor" because the searcher already knows what they need — and head terms are also losing traffic to AI assistants (users ask ChatGPT or Gemini for app recommendations before ever opening the store), while in-store long-tail holds its value.
    - Rich structured signals (in-app events, ratings) feed semantic ranking — they are not just conversion decoration.
    
    ## App Name
    
    Formula: `Brand — Primary Keyword` or `Brand: Keyword Phrase`.
    
    - Always use all 30 characters. Every unused character is keyword real estate thrown away.
    - Put the single highest-value keyword in the name — it carries the highest ranking weight of any placement.
    - Never use only the brand name unless the brand already has search volume. If nobody knows the name, nobody searches for it, and the app is banking entirely on browse traffic and press.
    - Never include "app", "the", "free", or "best". Apple indexes common terms automatically; these eat character budget and add nothing.
    
    Reference pattern: "Gentler Streak Workout Tracker" — the brand IS the keyword phrase. "Arc Search — Find it, Faster" — brand + primary keyword + value prop in one line.
    
    ## Subtitle
    
    The subtitle is coverage expansion, not a tagline. It appears directly under the name in search results, so it must do two jobs at once: rank for new terms and read naturally at a glance.
    
    - Never duplicate any word from the App Name (zero-overlap rule).
    - Cover adjacent search territory the name doesn't: if the name handles "workout tracker", the subtitle covers "Health, Steps & Recovery".
    - Use `&` and `,` to pack more terms into 30 characters.
    - It must read as a sentence fragment a human would write. A keyword-stuffed subtitle tanks tap-through rate because users see it before they tap — a ranking gain that kills conversion is a net loss, and semantic search now penalizes stuffing directly.
    
    ## Keyword Field
    
    Invisible to users; exists solely for the algorithm. Formatting rules are absolute:
    
    - Comma-separated, NO spaces after commas — spaces consume characters that could hold keywords.
    - Singular forms only — Apple auto-matches plurals, so "timer" covers "timers" and the plural form is pure waste.
    - Never repeat any word from the name or subtitle.
    - Never include the app name, developer name, or category name — Apple indexes these automatically.
    - Fill all 100 characters. Count them. Under 95 used = the field is not done.
    - Never include trademarked terms or competitor brand names — App Store Review Guideline 2.3.7 prohibits them and metadata rejections delay every release. Target competitor *keywords* (the terms they rank for), not their names.
    
    What belongs here: synonyms of main keywords, common misspellings, long-tail variations, translated terms from secondary locales, competitor keywords (not names).
    
    Example for "Deepwork — Focus Timer" / "Pomodoro & Concentration":
    ```
    study,productivity,flow,block,distraction,adhd,work,session,interval,music,noise,task,habit,routine
    ```
    
    ## Keyword research procedure
    
    Walk these steps in or
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/alexszczurek-before-skills-skills-aso.md

// REPO STATS

28 stars
0 open issues
Last commit: 11d ago