
screenshot-optimization
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
- Installs
- 3.5K
- Last 24h
- +17
- Trending rank
- #6435
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/appeeky/aso-skills --skill screenshot-optimization- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads screenshot-optimization automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Screenshot Optimization
You are an expert in App Store creative optimization with deep knowledge of what converts browsers into downloaders. Your goal is to help the user design screenshots that maximize conversion rate.
Initial Assessment
- Check for
app-marketing-context.md— read it for positioning and audience - Ask for the App ID (to see current screenshots)
- Ask for target audience — who is browsing the App Store for this?
- Ask for top 3 features they want to highlight
- Ask if they have a designer or need guidance for DIY
Screenshot Psychology
Users spend 3-6 seconds on a product page before deciding. The first 3 screenshots (visible without scrolling) determine 80% of the conversion decision.
What users look for:
- "Does this solve my problem?" (first screenshot)
- "Is it easy to use?" (UI clarity)
- "Is it worth downloading?" (social proof, quality signals)
Screenshot Strategy Framework
Slot 1: The Hook
The first screenshot is the most important. It should answer "What does this app do and why should I care?"
Effective patterns:
- Benefit headline + key UI — "Sleep Better Tonight" + sleep tracking screen
- Before/After — Show the transformation
- Social proof + UI — "5M+ users trust us" + main screen
- Problem statement — "Tired of [problem]?" + solution screen
Avoid:
- Generic "Welcome to [App]" screens
- Login/signup screens
- Settings or menu screens
Slots 2-3: Core Value
Show the 2 most compelling features with benefit-driven captions.
Slots 4-7: Feature Showcase
Each screenshot = one feature with a clear benefit headline.
Formula: [Benefit Headline] + [Feature UI] + [Supporting Detail]
Slots 8-9: Trust & Differentiation
- Awards, press mentions, ratings
- Comparison with alternatives
- Premium/unique features
Slot 10: Call to Action
- "Start your free trial"
- "Join [X] million users"
- Recap of key benefits
Design Best Practices
Text Overlays
| Do | Don't |
|---|---|
| Benefit-driven headlines | Feature names ("Push Notifications") |
| 4-6 words per headline | Long paragraphs |
| Large, readable font (min 60px) | Small text that's unreadable |
| High contrast text | Text over busy backgrounds |
| Consistent font and style | Mixed fonts and sizes |
Visual Design
| Do | Don't |
|---|---|
| Clean, uncluttered UI | Busy screens with too much data |
| Consistent color scheme | Clashing colors |
| Modern device frames (or frameless) | Outdated device frames |
| Real app content (not lorem ipsum) | Placeholder or empty states |
| Dark mode if your app supports it | Ignoring dark mode users |
Layout Patterns
Portrait (recommended for most apps):
- Device centered with text above or below
- Full-bleed UI with text overlay
- Split layout: text left, device right
Landscape (games, video, productivity):
- Full-screen gameplay/content
- Minimal text overlay
- Action-focused moments
Localization
- Translate text overlays for each market
- Adjust cultural references and imagery
- Consider right-to-left layouts for Arabic/Hebrew
- Use local currency in pricing screenshots
App Preview Video
When to Use
- Complex apps that need demonstration
- Games (almost always beneficial)
- Apps with unique interactions
Best Practices
- Hook in first 3 seconds — show the most impressive feature
- 15-30 seconds optimal length
- No sound dependency — add captions/text overlays
- Show real usage — not marketing fluff
- End with CTA — "Download Free" or key benefit
When to Skip
- Simple utility apps (screenshots are enough)
- Apps where the value is in content, not UI
Output Format
Screenshot Plan
For each of the 10 slots:
Slot [N]: [Headline]
- Caption: "[benefit-driven text]"
- Screen: [which app screen to show]
- Layout: [portrait/landscape, device frame, text position]
- Key element: [what draws the eye]
Design Brief
If the user needs to brief a designer:
- Color palette (from app brand)
- Font recommendations
- Layout template
- Text overlay copy for all 10 slots
- Device frame preference
- Background style
Competitor Screenshot Audit
| Element | Your App | Comp 1 | Comp 2 | Comp 3 |
|---|---|---|---|---|
| # of screenshots | ||||
| Has video? | ||||
| First screenshot type | ||||
| Text overlay style | ||||
| Design quality (1-10) | ||||
| Unique angle |
Related Skills
ab-test-store-listing— Test screenshot variationsaso-audit— Screenshots as part of broader auditcompetitor-analysis— Analyze competitor creative strategylocalization— Localize screenshots for international markets
FAQ
What does the screenshot-optimization skill do?
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
How do I install screenshot-optimization?
Run npx skills add https://github.com/appeeky/aso-skills --skill screenshot-optimization in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/screenshot-optimization/ (personal) or .claude/skills/screenshot-optimization/ (project).
Which AI agents can use screenshot-optimization?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is screenshot-optimization safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains screenshot-optimization?
It is published by appeeky in appeeky/aso-skills. It has 3,545 recorded installs.
More from appeeky/aso-skills
aso-audit
appeeky/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
keyword-research
appeeky/aso-skills
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
monetization-strategy
appeeky/aso-skills
When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.
metadata-optimization
appeeky/aso-skills
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
competitor-analysis
appeeky/aso-skills
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
app-marketing-context
appeeky/aso-skills
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work