
Asc Screenshot Resize
Resize and validate iPhone and iPad App Store screenshots using live asc CLI size data and macOS sips before Connect upload.
Overview
asc screenshot resize is an agent skill for the Launch phase that prepares and validates App Store Connect screenshots using current asc screenshot-size data and macOS sips.
Install
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-screenshot-resizeWhat is this skill?
- Treats asc screenshots sizes as the source of truth—no stale hard-coded dimension tables in the skill
- Batch resize with macOS sips after sanitizing Unicode spaces in screenshot filenames
- Pre-upload validation via asc screenshots validate for device types like IPHONE_65 and IPAD_PRO_3GEN_129
- Documents workflow for extended sets: 6.9-inch iPhone, Apple TV, Mac, Vision Pro, iMessage, Watch via sizes --all
- Pairs discovery (sizes --output table) with local folder validation before upload
- Common anchor device types documented: IPHONE_65 and IPAD_PRO_3GEN_129
Adoption & trust: 653 installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your screenshots are the wrong size or fail validation because dimension tables in blog posts are outdated and macOS filenames hide breaking Unicode spaces.
Who is it for?
Indie iOS/macOS developers already using the asc CLI who batch-prepare iPhone and iPad screenshot sets on a Mac.
Skip if: Teams on Linux-only CI without sips, builders who need marketing creative direction rather than dimension compliance, or Android Play Store asset prep.
When should I use this skill?
Preparing or fixing screenshots for App Store Connect submission; user mentions asc screenshot resize, screenshot validation, or accepted sizes for iPhone/iPad store listings.
What do I get? / Deliverables
You have per-device-type folders of correctly sized screenshots that pass asc screenshots validate before you upload to App Store Connect.
- Device-type folders of resized screenshots matching asc-reported dimensions
- Successful asc screenshots validate output per target device type
Recommended Skills
Journey fit
Screenshot dimensions and device-type sets are enforced at App Store Connect submission, which maps directly to the Launch phase ASO shelf. ASO subphase covers store listing assets; incorrect screenshot geometry is a common rejection cause, so canonical placement is launch → aso.
How it compares
Use this asc-driven resize workflow instead of memorizing screenshot pixels from old blog posts or manual Preview exports without CLI validation.
Common Questions / FAQ
Who is asc-screenshot-resize for?
Solo and indie mobile developers shipping to the App Store who use the asc CLI and need compliant screenshot dimensions per device type.
When should I use asc-screenshot-resize?
In Launch (ASO) when preparing or fixing screenshots for App Store Connect submission—after you have captures and before upload—especially when targeting IPHONE_65, iPad Pro sets, or less common display types via asc screenshots sizes --all.
Is asc-screenshot-resize safe to install?
The skill documents local file renames, sips transforms, and asc API calls; review the Security Audits panel on this Prism page and keep App Store Connect credentials out of agent logs.
SKILL.md
READMESKILL.md - Asc Screenshot Resize
# asc screenshot resize Use this skill to prepare screenshots for App Store Connect. Do not rely on a hard-coded dimension table in this skill; the CLI owns the current size matrix. ## Source of truth Always discover current accepted sizes from `asc` first: ```bash asc screenshots sizes --output table asc screenshots sizes --all --output table ``` For local validation before upload: ```bash asc screenshots validate --path "./screenshots/iphone" --device-type "IPHONE_65" --output table asc screenshots validate --path "./screenshots/ipad" --device-type "IPAD_PRO_3GEN_129" --output table ``` Common current device-type anchors: - `IPHONE_65` for the common 6.5-inch iPhone screenshot set. - `IPAD_PRO_3GEN_129` for the common 12.9/13-inch iPad screenshot set. Run `asc screenshots sizes --all` when targeting other display types such as 6.9-inch iPhone, Apple TV, Mac, Vision Pro, iMessage, or Watch. ## Workflow ### 1. Sanitize filenames macOS screenshots can contain hidden Unicode spaces that make tools fail with "not a valid file". Sanitize before batch work: ```bash python3 -c " import os for f in os.listdir('.'): clean = f.replace('\u202f', ' ') if f != clean: os.rename(f, clean) print(f'Renamed: {clean}') " ``` ### 2. Inspect dimensions and metadata ```bash sips -g pixelWidth -g pixelHeight screenshot.png sips -g hasAlpha -g space screenshot.png ``` App Store Connect rejects screenshots with alpha transparency. Strip alpha by round-tripping through JPEG: ```bash sips -s format jpeg input.png --out /tmp/asc-screenshot-no-alpha.jpg sips -s format png /tmp/asc-screenshot-no-alpha.jpg --out output.png rm /tmp/asc-screenshot-no-alpha.jpg ``` Batch-strip alpha from PNGs: ```bash for f in *.png; do if sips -g hasAlpha "$f" | grep -q "yes"; then sips -s format jpeg "$f" --out /tmp/asc-screenshot-no-alpha.jpg sips -s format png /tmp/asc-screenshot-no-alpha.jpg --out "$f" rm /tmp/asc-screenshot-no-alpha.jpg echo "Stripped alpha: $f" fi done ``` ### 3. Resize only after choosing a target from asc Pick a width and height from `asc screenshots sizes --all`. `sips -z` takes height first, then width: ```bash # Example: portrait IPHONE_65 1284 x 2778 sips -z 2778 1284 input.png --out output.png ``` Batch resize to a chosen target: ```bash mkdir -p resized for f in *.png; do sips -z 2778 1284 "$f" --out "resized/$f" done ``` ### 4. Validate outputs with asc ```bash sips -g pixelWidth -g pixelHeight -g hasAlpha resized/*.png asc screenshots validate --path "./resized" --device-type "IPHONE_65" --output table ``` ### 5. Upload only after validation ```bash asc screenshots upload --version-localization "LOC_ID" --path "./resized" --device-type "IPHONE_65" --dry-run --output table asc screenshots upload --version-localization "LOC_ID" --path "./resized" --device-type "IPHONE_65" ``` ## Guardrails - Treat `asc screenshots sizes --all` as authoritative; Apple size requirements change. - Do not stretch screenshots across incompatible aspect ratios unless the user accepts the visual tradeoff. - Always output to a separate file or directory to preserve originals. - Screenshots must be PNG or JPEG and must not include alpha transparency. - Convert Display P3 or other color spaces to sRGB when needed: ```bash sips -m "/System/Library/ColorSync/Profiles/sRGB IEC61966-2.1.icc" input.png --out output.png ``` - Prefer `asc screenshots validate` over visual inspection before upload.