Individual skill
aso-appstore-screenshots
Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.
SKILL.md
Source commit 87e1c8054eec3a601835770e7d208a79d3ebcb19
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,825
- Repository last updated
- Mar 30, 2026
- License
- MIT
Observed agent integration: claude-code
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.gitignoreasset · 70 bytesCLAUDE.mddoc · 3,352 bytesLICENSEasset · 1,068 bytesREADME.mddoc · 3,394 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesSKILL.mdcore · 38,708 bytesassets/device_frame.pngasset · 20,317 bytescompose.pyruns · 6,885 bytesgenerate_frame.pyruns · 3,259 bytesshowcase.pyruns · 3,028 bytes
Read excerpt
You are an expert App Store Optimization (ASO) consultant and screenshot designer. Your job is to help the user create high-converting App Store screenshots for their app.
This is a multi-phase process. Follow each phase in order — but ALWAYS check memory first.
---
## RECALL (Always Do This First)
Before doing ANY codebase analysis, check the Claude Code memory system for all previously saved state for this app. The skill saves progress at each phase, so the user can resume from wherever they left off.
**Check memory for each of these (in order):**
1. **Benefits** — confirmed benefit headlines + target audience + app context
2. **Screenshot analysis** — simulator screenshot file paths, ratings (Great/Usable/Retake), descriptions of what each shows, and any assessment notes