Automate App Store Screenshots with This Agent Skill

Where this fits

You've just finished a feature release and need to update your App Store and Google Play listings. You have raw screenshots of the new UI, but they need device frames, branded backgrounds, and promotional copy — and they must match each store's exact pixel dimensions. Without a designer, this becomes a repetitive, error-prone task. The store-screenshots skill automates this pipeline directly inside your agent workflow.

Why agents benefit

• Generates store-compliant PNGs — automatically applies iPhone, iPad, Galaxy, Fold, and Flip frames and outputs at exact store sizes, eliminating manual resizing.
• Iterates on marketing copy — the agent can propose headline variations and render a preview slide for approval before committing to full renders.
• Maintains brand consistency — uses HTML/CSS to draw device frames and gradients, so no external assets are needed and the style stays uniform across all screenshots.
• Verifies output quality — checks pixel dimensions with sips or ImageMagick after rendering, catching errors before you upload.
• Works across agent environments — compatible with Claude Code and OpenAI Codex, adapting its interaction style to the available tools.

Practical scenarios

App Store update for a new release

After shipping a major update, you ask the agent: "Make App Store screenshots for the new onboarding flow." It takes your raw captures, wraps them in iPhone 15 frames, adds a gradient background with your brand color, and proposes three headline options. You approve one, and it renders all required sizes (6.7", 6.5", 5.5") in minutes.

Localizing marketing screenshots for multiple stores

You're launching in Japan and need Play Store screenshots with Japanese copy. The agent can swap the marketing text, keep the same visual layout, and output the correct dimensions for Google Play (various phone and tablet sizes). No need to redo the design from scratch.

A/B testing promotional text

You want to test two different value propositions on your listing. The agent generates two sets of screenshots with different headlines, using the same background and frames, so you can compare performance without manual design work.

Add it to your agent workflow

Install the skill with:

npx skills add LeeHueeng/store-screenshots --skill store-screenshots

Then invoke it by providing a folder path to your raw screenshots. For example, in Claude Code:

$ARGUMENTS /path/to/screenshots

The agent will ask for your preferred device frames and copy direction, show you a preview, and only after your approval render the full set.

Compare before adopting

Before committing, compare this skill against manual design tools or other automation scripts. Check the quality of the generated frames and backgrounds — are they visually comparable to what a designer would produce? Look at the maintenance freshness: is the skill actively updated to support new device models and store size changes? Also consider how well it fits your existing agent workflow — does it integrate cleanly with your codebase and asset pipeline? Finally, weigh the trade-off between using a pre-built skill and writing your own script if you need heavy customization.

Why it is worth tracking

The skill has 31 stars and is authored by LeeHueeng, indicating a small but engaged community. Its design as a pure HTML/CSS renderer avoids dependency on external image assets, which is a strong quality signal for reliability. As app stores update their requirements, you'll want to watch for commits that add new device frames or adjust dimensions. Evaluate this skill when you're about to refresh your store listings or when you want to automate a recurring marketing asset workflow. For more details, see the skill page.