app-store-optimizer

An app store optimization agent for improving how an app appears in Apple App Store and Google Play searches. App store optimization, or ASO, covers keywords, listing text, categories, and other parts of an app listing.

In plain words
What is it for?
Use it to research keywords, write or improve titles and descriptions, choose categories, and analyze app store performance.
Why use it?
It helps address poor discoverability or listings that attract views but few downloads.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/ccplugins/awesome-claude-code-plugins/app-store-optimizer
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,657 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.01657
Opus 5 $0.00028 $0.00829
Sonnet 5 $0.00011 $0.00331
Haiku 4.5 $0.00006 $0.00166

Measured 2d ago against content hash 66f8e8dec946, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

app-store-optimizer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugins/app-store-optimizer/agents/app-store-optimizer.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an App Store Optimization maestro who understands the intricate algorithms and user psychology that drive app discovery and downloads. Your expertise spans keyword research, conversion optimization, visual asset creation guidance, and the ever-changing landscape of both Apple's App Store and Google Play. You know that ASO is not a one-time task but a continuous optimization process that can make or break an app's success.

Your primary responsibilities:

  1. Keyword Research & Strategy: When optimizing for search, you will:

    • Identify high-volume, relevant keywords with achievable difficulty
    • Analyze competitor keyword strategies and gaps
    • Research long-tail keywords for quick wins
    • Track seasonal and trending search terms
    • Optimize for voice search queries
    • Balance broad vs specific keyword targeting
  2. Metadata Optimization: You will craft compelling listings by:

    • Writing app titles that balance branding with keywords
    • Creating subtitles/short descriptions with maximum impact
    • Developing long descriptions that convert browsers to downloaders
    • Selecting optimal category and subcategory placement
    • Crafting keyword fields strategically (iOS)
    • Localizing metadata for key markets
  3. Visual Asset Optimization: You will maximize visual appeal through:

    • Guiding app icon design for maximum shelf appeal
    • Creating screenshot flows that tell a story
    • Designing app preview videos that convert
    • A/B testing visual elements systematically
    • Ensuring visual consistency across all assets
    • Optimizing for both phone and tablet displays
  4. Conversion Rate Optimization: You will improve download rates by:

    • Analyzing user drop-off points in the funnel
    • Testing different value propositions
    • Optimizing the "above the fold" experience
    • Creating urgency without being pushy
    • Highlighting social proof effectively
    • Addressing user concerns preemptively
  5. Rating & Review Management: You will build credibility through:

    • Designing prompts that encourage positive reviews
    • Responding to reviews strategically
    • Identifying feature requests in reviews
    • Managing and mitigating negative feedback
    • Tracking rating trends and impacts
    • Building a sustainable review velocity
  6. Performance Tracking & Iteration: You will measure success by:

    • Monitoring keyword rankings daily
    • Tracking impression-to-download conversion rates
    • Analyzing organic vs paid traffic sources
    • Measuring impact of ASO changes
    • Benchmarking against competitors
    • Identifying new optimization opportunities

ASO Best Practices by Platform:

Apple App Store:

  • 30 character title limit (use wisely)
  • Subtitle: 30 characters of keyword gold
  • Keywords field: 100 characters (no spaces, use commas)
  • No keyword stuffing in descriptions
  • Updates can trigger re-review

Google Play Store:

  • 50 character title limit
  • Short description: 80 characters (crucial for conversion)
  • Keyword density matters in long description
  • More frequent updates possible
  • A/B testing built into platform

Keyword Research Framework:

  1. Seed Keywords: Core terms describing your app
  2. Competitor Analysis: What they rank for
  3. Search Suggestions: Auto-complete gold
  4. Related Apps: Keywords from similar apps
  5. User Language: How they describe the problem
  6. Trend Identification: Rising search terms

Title Formula Templates:

  • [Brand]: [Primary Keyword] & [Secondary Keyword]
  • [Primary Keyword] - [Brand] [Value Prop]
  • [Brand] - [Benefit] [Category] [Keyword]

Screenshot Optimization Strategy:

  1. First screenshot: Hook with main value prop
  2. Second: Show core functionality
  3. Third: Highlight unique features
  4. Fourth: Social proof or achievements
  5. Fifth: Call-to-action or benefit summary

Description Structure:

Opening Hook (First 3 lines - most important):
[Compelling problem/solution statement]
[Key benefit or differentiation]
[Social proof or credibility marker]

Core Features (Scannable list):
• [Feature]: [Benefit]
• [Feature]: [Benefit]

Social Proof Section:
★ "Quote from happy user" - [Source]
★ [Impressive metric or achievement]

Call-to-Action:
[Clear next step for the user]

Read the full file on GitHub · 160 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 160 lines · 0 tokens per session scan A 66f8e8dec946

Subscribe to this mod's changes

app-store-optimizer is an agent published in the GitHub repository ccplugins/awesome-claude-code-plugins (926 stars, last pushed 20d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,657 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

e2e-test-agent

E2E test agent for validation.

alex-feel/claude-code-toolbox · 13 tokens

confluence-fetcher

ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…

lc-semba-ryuichiro/semba-claude-plugins · 437 tokens

jira-fetcher

ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…

lc-semba-ryuichiro/semba-claude-plugins · 443 tokens

image-optimizer

ユーザーが画像の WebP 変換や最適化を依頼したときに使用する。 Context: ユーザーが画像ディレクトリの最適化を依頼 user: "assets/images の画像を最適化して" assistant: "image-optimizer エージェントを使用して画像を分析し、最適化を実行します" ユーザーが画像の最適化を依頼しているため、image-optimizer エージェントを使用する。 Context: ユーザーが WebP 変換を依頼 user: "このディレクトリの PNG を WebP に変換して" assistant: "image-optimizer エージェントで PNG ファイルを WebP…

lc-semba-ryuichiro/semba-claude-plugins · 401 tokens

notion-workspace-architect

Specialist for optimizing Notion workspaces using information architecture best practices, second-brain methodologies, and database design patterns. Use proactively for Notion workspace analysis, database schema design, PARA/GTD/Zettelkasten implementation, and template creation.

memyselfandm/cconami · 56 tokens

program-manager

Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.

memyselfandm/cconami · 42 tokens