App Store and Google Play screenshot creation with exact platform specs. Covers iOS/Android dimensions, gallery ordering, device mockups, and preview videos.
SkillScore92Maintained
Automatic
◆Marketing & Content pack
Last verified 8/27/2026
What it changes
Passed 23 of 25 test cases with the skill, and 15 of 25 without it.
Without skill60%
With skill92%
Checks it passed that the model alone missed
Target 3 to 5 words per line for slide headline copy.
Insert a 300 millisecond delay between consecutive slide image captures.
Set package manager selection priority to bun, followed by pnpm, yarn, and npm.
and 5 more in the full report
8 fixed15 passed either way2 still failing0 broke
Pass-rate lift
+32 pp
Tokens
+75%
Agent turns
0%
Response time
-50%
Model gemini-3.6-flashMeasured 8/27/2026v323 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
I am drafting headline text for an App Store promotional slide. How many words per line should be targeted for readable thumbnail typography, and what HTML element should be used to control exact line breaks?
What was checked, without and with the skill
Checked
Without skill
With skill
Target 3 to 5 words per line for slide headline copy.
Missed
Passed
Insert explicit HTML line break tags to control copy line breaks.
Passed
Passed
case-13 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md329 linessingle file
App Store Screenshots Generator
Overview
Build a Next.js page that renders iOS App Store screenshots as advertisements (not UI showcases) and exports them via html-to-image at Apple's required resolutions. Screenshots are the single most important conversion asset on the App Store.
Core Principle
Screenshots are advertisements, not documentation. Every screenshot sells one idea. If you're showing UI, you're doing it wrong — you're selling a feeling, an outcome, or killing a pain point.
Step 1: Ask the User These Questions
Before writing ANY code, ask the user all of these. Do not proceed until you have answers:
Required
App screenshots — "Where are your app screenshots? (PNG files of actual device captures)"
App icon — "Where is your app icon PNG?"
Brand colors — "What are your brand colors? (accent color, text color, background preference)"
Font — "What font does your app use? (or what font do you want for the screenshots?)"
Feature list — "List your app's features in priority order. What's the #1 thing your app does?"
Number of slides — "How many screenshots do you want? (Apple allows up to 10)"
Style direction — "What style do you want? Examples: warm/organic, dark/moody, clean/minimal, bold/colorful, gradient-heavy, flat. Share App Store screenshot references if you have any."
Optional
Component assets — "Do you have any UI element PNGs (cards, widgets, etc.) you want as floating decorations? If not, that's fine — we'll skip them."
Additional instructions — "Any specific requirements, constraints, or preferences?"
Derived from answers (do NOT ask — decide yourself)
Based on the user's style direction, brand colors, and app aesthetic, decide:
Background style: gradient direction, colors, whether light or dark base
Decorative elements: blobs, glows, geometric shapes, or none — match the style
Dark vs light slides: how many of each, which features suit dark treatment
Typography treatment: weight, tracking, line height — match the brand personality
Color palette: derive text colors, secondary colors, shadow tints from the brand colors
IMPORTANT: If the user gives additional instructions at any point during the process, follow them. User instructions always override skill defaults.