AGENT SKILL

app-store-optimization

Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.

License 许可
MIT
所属仓库
siddu1004/SFP
最近更新
2026-11-09
Stars
★ 5
Forks
0

01 前言 Front Matter

name
app-store-optimization
description
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.

02 资源文件 1

03 SKILL.md 正文

App store optimization

Two levers, and they are separate problems: being found, and being installed once found. Diagnose which is failing before changing anything.

Being found

The stores index different fields, so the same metadata does not work on both.

  • App name / title — the single heaviest field. Brand plus the primary descriptive term. Do not spend it on brand alone.
  • Subtitle and keyword field — no repetition across fields; duplicated terms are wasted characters, not reinforcement.
  • Long description — indexed on one store, effectively not on the other. Write it for the store that indexes it and for humans on the store that does not.
  • Category — pick where you can rank, not where you technically belong.

Target terms with real intent. Ranking first for a term nobody searches is a vanity result.

Being installed

Most visitors decide from the first screenshot and the rating, without scrolling or reading.

  • Screenshots — the first two carry the decision. Lead with the outcome or the core screen, with a caption stating the benefit. Never lead with an onboarding or login screen.
  • Icon — recognizable at actual size, distinct from category conventions. Test at real scale on a device.
  • Rating — the strongest single conversion factor. Prompt for review after a success moment, never on launch or mid-task.
  • Video — only if it demonstrates something a screenshot cannot. A weak one costs installs.

Reviews

Respond to negative reviews specifically and without defensiveness, naming the fix and its version where there is one. Prospects read the responses as much as the complaints, and a pattern of real answers converts.

Watch review text for recurring themes — it is the cheapest continuous product research available.

Testing

Change one element at a time and let it run a full weekly cycle; app traffic is strongly day-of-week seasonal. Attributing a lift to the wrong change is worse than not testing.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

The consoles are the source of truth: App Store Connect and Google Play Console, including their own experiment features — product page optimization and store listing experiments — which test on real store traffic rather than a simulation.

Keyword and competitor research: AppTweak, Sensor Tower, data.ai, AppFollow, and similar. Treat their volume estimates as directional; the stores do not publish the underlying numbers.

Review management and reply workflows live in the consoles or in the same tools, and replying is the part most teams skip.

Never

  • Chase a keyword the app does not deliver on. Installs from a mismatched query become one-star reviews and a worse ranking than you started with.
  • Change metadata, screenshots, and the icon in the same release. Nothing that moves afterward can be attributed.
  • Solicit ratings from a user mid-task. The prompt lands where frustration is highest and the score reflects that.
  • Ignore reviews on the version you just shipped. They are the fastest signal you will get that a release broke something.

04 同仓库更多 Skills

siddu1004
siddu1004/SFP

scientific-schematics

Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.

★ 5
siddu1004
siddu1004/SFP

polyhaven-texture-apply

Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal/wood/marble, or change object surface.

★ 5
siddu1004
siddu1004/SFP

polyhaven-studio-setup

Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.

★ 5
siddu1004
siddu1004/SFP

polyhaven-scene-builder

Build complete product scenes using PolyHaven assets — HDRI environment, textured ground/pedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.

★ 5
siddu1004
siddu1004/SFP

polyhaven-material-swap

Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color/finish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.

★ 5
siddu1004
siddu1004/SFP

polyhaven-hdri-showcase

Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.

★ 5