App Store screenshots, from your codebase
An Agent Skill that reads your app's codebase, finds its real benefits, pairs them with your simulator screenshots, composes device-framed layouts, and hands you an editable project link on appshoteditor.com — not flattened PNGs.
How it works
Verify your account
The skill runs a pre-flight `whoami` check against your API token before touching anything. No token yet? It tells you to create a free account first.
Analyze your app
It reads your app's source, README, and store copy to extract 5–10 concrete, user-facing benefits — outcomes, not features. Each becomes a screenshot headline.
Upload your screenshots
You point it at a folder of simulator/device screenshots (PNG/JPEG/WebP). It uploads them to your account and pairs each one with the right benefit.
Compose device-framed layouts
The bundled CLI does the deterministic, mechanical work — composing valid layout DSL for each screen with the matching device frame and a cohesive background.
Get an editable link
It publishes the layout and hands you a link at appshoteditor.com/app?import=… — open it signed in to fine-tune copy, layers, and backgrounds, then export at App Store resolutions.
Setup
1 Create an account & API token
Sign in at appshoteditor.com/account with Google — this creates a free account. Generate an API token on that page.
2 Install the skill
Needs Node 22+. Clone it into your agent's skills folder — keep the folder name appshot-screenshots:
git clone https://github.com/AppShotEditor/app-store-screenshots-skill.git \
~/.claude/skills/appshot-screenshotsOther agents — swap the path: ~/.codex/skills/… · ~/.cursor/skills/… · ~/.config/opencode/skills/…
3 Export your token
export APPSHOTEDITOR_TOKEN=ase_…4 Run it
In your app's repo, ask your agent: "Make App Store screenshots for this app" (or run /appshot-screenshots if your tool supports skill
slash-commands). It analyzes your app, uploads your screenshots, composes device-framed layouts, and returns an editor link to fine-tune.
How this differs from the browser editor
The in-browser editor composes everything locally and never uploads your screenshots. This skill is optional and works differently: it uploads your source screenshots to your account's storage (R2), counted against your plan's storage quota, so it can hand you back an editable link. Import links expire 24 hours after the skill publishes them — re-run the skill for a fresh one if yours lapses.
FAQ
Which coding agents does this work with?
It's an open Agent Skill (the SKILL.md standard), so it works with Claude Code, OpenAI Codex CLI, Cursor, opencode, and any other compatible agent. The instructions load in any of them; the actual work runs as a self-contained Node CLI.
Do I need an appshoteditor.com account?
Yes — a free account and an API token. Sign in with Google at /account and generate a token before running the skill.
Does it upload my source code anywhere?
No. Your agent reads your codebase locally to write the benefit headlines — that never leaves your machine. Only the screenshot images you point it at get uploaded, to your own account's storage.
How is this different from the in-browser editor?
The browser editor composes everything locally and never uploads your screenshots. This skill is optional and does upload your source screenshots to your account storage (counted against your plan's quota) so it can hand you back a link you can open from anywhere.
How long is the handoff link valid?
Import links expire 24 hours after the skill publishes them. If yours expires, just re-run the skill to get a fresh one.
Ready to try it?
Grab a token, install the skill, and ask your agent to build your next App Store screenshot set.