Turn your app captures into editable store screenshots. Your agent can write captions, build and preview the set, then export it or upload approved assets to your store.
Get the AppScreens Skills Pack
Install all the skills together, or download individual skills below.
Create app store screenshots
Turn real app captures into an editable screenshot story, refine it visually, then localize, export or upload the approved result.
Needs your AppScreens connection, which takes a sign-in. It works with the full set of 85 AppScreens tools.
Try asking
Turn the captures in ./screenshots into an iPhone screenshot set with benefit-led captions. Show me a preview.
Skill ZIP Read the instructions Connect AppScreens All tools
Match a screenshot reference
Rebuild a reference as editable layers, check an early render and complete the agreed set.
Needs an AppScreens connection to save and render the editable design.
Try asking
Rebuild these attached references in AppScreens for my iPhone app. Use my branding, check an early render and show me the finished set.
Tools your agent uses:get_design_contractget_inspiration_imagesplan_screenshot_requirementslist_render_targetslist_languageslist_library_imagesapply_project_changesset_project_settingsget_project_elementlist_project_elementsrender_project_previewwait_for_operationget_preview_imageadd_project_screenshotlist_project_screenshots
Find screenshot inspiration
See how top apps in your category open their screenshots, then get a short, sourced brief with two original directions.
Needs no sign-in. With AppScreens connected, your agent can also look at the screenshots themselves.
Try asking
Show me how the top finance apps on the US App Store open their first three screenshots.
Tools your agent uses:search_inspirationget_inspiration_imageslist_templates
Audit my store screenshots
Find out which screenshot to fix first, why and how, from a store link, an app name or your own images.
Reviews a public listing without an account, or inspects a saved project when AppScreens is connected.
Try asking
Review my App Store screenshots at apps.apple.com/app/id123456789 and tell me which one to fix first.
Tools your agent uses:get_projectlist_project_screenshotsget_project_textrender_project_previewwait_for_operationget_preview_image
A/B test my screenshots
Choose the one change worth testing and build the variant, then set up an Apple product page optimization test or custom product page.
Plans a test without an account. Building the variant, creating the Apple test or page and uploading to it need AppScreens connected.
Try asking
Set up an App Store test of a new first-screenshot headline against my current screenshots.
Tools your agent uses:get_account_capabilitiesduplicate_projectreplace_project_textapply_project_changesrender_project_previewwait_for_operationget_preview_imagestart_project_exportlist_store_listingspreview_store_listing_creationcreate_store_listingpreview_store_screenshot_deploymentdeploy_store_screenshotsget_deployment
Prepare my store listing for release
Draft release notes and listing copy, stage approved screenshots, and leave the store draft ready for your review.
Drafts copy from a changelog without an account. Applying approved changes needs AppScreens connected to your store.
Try asking
Use our 2.4 changelog to draft What’s New, update the subtitle, and show me what’s missing from the store draft.
Tools your agent uses:get_store_metadata_guidanceget_projectreplace_project_textassign_device_screenshotsstart_app_credential_setuplist_store_targetslist_store_localesget_store_metadatapreview_store_metadataapply_store_metadataprepare_store_metadata_copypreview_store_releasecreate_store_releasepreview_store_screenshot_deploymentdeploy_store_screenshotsget_deployment
Check that your agent can see previews
Before you ask your agent to match a reference design, check that it can see AppScreens previews. Replace the placeholder in this prompt with a link to a saved project. Use a completed preview if you have one. A new render uses your account’s render allowance.
For a close match, the agent checks a representative render early, reviews every finished page in contact sheets and opens individual details where text, crops or overlaps are unclear. Ask to see an early preview if you want to give feedback before it completes the set. The agent can keep generated artwork in separate layers and leave unfilled devices blank until you add captures.
Try asking
Open one completed preview for this AppScreens project: [paste project link]. Show me the image and describe two visible details. If you can’t see the image, say so and share the browser preview link. If there’s no completed preview you can open, ask me before starting a render.
Why AppScreens
Store screenshots look like an image task, but shipping them is a pipeline: ideas, design, every size each store requires, every language, preview, export, upload and testing. AppScreens carries supplied captures through that journey in one editable project, so the work goes into the app's story instead of rebuilding store rules. The agent proposes the copy and design; actual renders and customer review determine whether the result is ready.
- Ideas: Current screenshots of thousands of top apps, by category and market, to look at and compare.
- Starting point: 190+ designed templates, a blank project or an existing design.
- Sizes: Every App Store and Google Play screenshot size, Google Play feature graphics, Apple product page header and search artwork, and In-App Event media, checked before export.
- Design: Edits saved to a project that can be watched live, adjusted in the editor and restored from version history.
- Languages: 88 languages, including right-to-left, with automatic translation that uses the app's context, or translations you write.
- Preview: Rendered pages, and the listing as it looks in the App Store and Google Play.
- Export: One export of store-ready files.
- Store: Upload screenshots and listing text and create draft versions, each after a preview is approved; store keys stay in AppScreens.
- A/B tests: Create an Apple product page optimization test or custom product page and upload to it; Google Play experiments are finished in Play Console.
Install the skills
- If your client supports the AppScreens plugin, install it to get the MCP connection settings and skills together.
- Claude Code: unzip the pack into ~/.claude/skills, or into .claude/skills in a project. Each skill is a folder with a SKILL.md.
- Claude apps: upload one skill ZIP at a time where your workspace manages skills.
- Other agents that read SKILL.md skills: copy the skill folders to where your agent loads skills.
- Skills that make or change screenshots also need the AppScreens connection, which takes a sign-in.
Versions
The pack is version 0.8.9. Fixes to a skill's instructions raise the last number, a new skill or workflow raises the middle one, and a renamed or removed skill raises the first. Skill names stay the same between versions, so what you ask for keeps working.
