MagicScreenshots

Research real App Store marketing images and preview videos from a library refreshed daily. Choose a reference, then generate or localize screenshots for the user's own app.

Installation

Install this skill with pnpm dlx skills add Humanleap/agent-skills --skill magicscreenshots. Connect remote MCP to https://www.magicscreenshots.com/api/mcp.

CLI alternative (Node 18+):

pnpm dlx magic-screenshots search --category finance --chart grossing
pnpm dlx magic-screenshots app duolingo
pnpm dlx magic-screenshots screens duolingo --out ./reference

Four Hard Rules — Read First

1. Reference real results. Do not invent apps, chart ranks, screenshot styles or history.
2. Use third-party assets as references. Their developers own them. Never ship another app's screenshots or preview footage as the user's work.
3. Approve spending before starting. Confirm the paid operation and the human’s spending limit before create_restyle or create_localize; do not start chargeable work without approval. Show the overview afterward and call approve_restyle only after the human approves that design.
4. Keep output truthful. Generated screenshots must represent the user's actual app; a pending job is unfinished.

Authentication

Public library search/read tools need no key. For authenticated features, the human sets up a supported connection or secure CLI configuration using the official agent setup page. Never request, print, save or transmit API keys, passwords or authentication codes in conversation or tool arguments. Do not create credentials on the human’s behalf. If the assistant platform cannot provide secure authentication, use public library reads and hand the requested paid workflow to the official website. The human completes sign-in and payment there.

Core Workflow

1. Define the brief. Identify the app category, audience and desired feel. Read list_directory_categories or list_directory_tags when needed.
2. Search references. Use list_directory_apps by query, category, chart (free or grossing) and style tag, setting platform: "ios" for App Store research. Select relevant apps from actual results.
3. Inspect the images. Read get_directory_app and get_directory_screens for a few candidates. Compare headline, colour, device treatment and order of benefits; cite the apps you inspected.
4. Prepare the user's generation. After secure authentication and spending approval, use get_screenshots to identify the user's app, then create_restyle with its source_app and chosen inspiration_slug.
5. Review and finish. Poll get_job_group for overview_url, show it, and call approve_restyle only after approval. Poll again for final output URLs.

Essential Tools

Common Patterns

• Design inspiration: compare 3–6 relevant apps and explain patterns visible in their actual screenshot sequences.
• Restyle: use the chosen reference slug, for example {"source_app":{"query":"My App"},"inspiration_slug":"duolingo","limit":5}, after confirming the user's app identity.
• Localization: use create_localize with the user's selected target_locales, such as ["JPN","DEU","FRA"], and poll for each locale's output.
• Preview reference: search with has_video: true; compare opening seconds, pacing, captions and closing message. Do not reuse footage. Pro mp4 links expire after an hour.

Supporting Resources

• Agent setup: https://www.magicscreenshots.com/agents
• Library: https://www.magicscreenshots.com/apps
• Charts: https://www.magicscreenshots.com/top
• Pricing: https://www.magicscreenshots.com/pricing

Common Gotchas

• The library contains App Store listing marketing screenshots, rather than arbitrary in-app UI captures.
• A library reference is not evidence that the user's app offers the same features.
• Show the returned claim/payment URL when a tool asks for access; do not guess entitlement or pay automatically.
• An overview is a review stage, not the final rendered screenshot set.

Quick Reference

Search → inspect real references → identify user's app → create → show overview → human approves → retrieve completed output.