asc-screenshots

Uploads and replaces App Store Connect screenshots and previews with staged locale and display-type mapping.

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill asc-screenshots-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-screenshots
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/asc-screenshots
Command: npx skills add https://github.com/mintuz/.dotfiles --skill asc-screenshots-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Uploading App Store screenshots and previews through App Store Connect involves locale code mapping, display-type grouping, sandbox file-access constraints, and destructive replace semantics that are easy to get wrong. This Skill encodes the staging layout, locale mapping, sandbox path rules, and dry-run-first upload procedure so uploads land correctly on the first attempt. ## Core Features & Use Cases - Staging Layout Enforcement: Stages files as <stage-root>/<locale>/<displayType>/NN_filename.ext, mapping repository folder names like de and es to App Store Connect codes like de-DE and es-ES. - Dry-Run-First Uploads: Runs helm-asc version <version-id> screenshots upload --dry-run first, compares per-group counts against staged files, and only applies after every count matches. - Safe Replace Semantics: Guards against accidental deletion by requiring explicit user intent before adding --replace, and verifies final state by checking locale, displayType, fileName stamps, and complete states. - Use Case: You exported new 6.9-inch screenshots for German and Dutch locales from a design tool. Stage them under the Helm uploads inbox, dry-run the upload to confirm both locale groups count correctly, then apply and verify every screenshot reaches the complete state. ## Quick Start Upload my staged App Store screenshots for version 1.2.3 in the de-DE and nl-NL locales using a dry run first, then apply and verify the results.

Frequently Asked Questions about asc-screenshots

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload App Store screenshots with helm-asc?

Stage files as <stage-root>/<locale>/<displayType>/NN_filename.ext under the Helm uploads inbox, then run helm-asc version <version-id> screenshots upload --path <stage-root> --dry-run --agent. Verify per-group counts match your staged files before running the same command without --dry-run.

How do I replace existing App Store screenshots instead of adding to them?

Add --replace to the upload command only when the user explicitly wants replacement. --replace deletes every existing screenshot in each matching locale and display-type set before uploading, so it must never be used for add or append requests.

Why does helm-asc return a FILE_ACCESS error on upload?

FILE_ACCESS usually means the staging write into the Helm sandbox directory silently failed due to missing escalated permission. List the staged tree with find; if it is empty or partial, re-stage with escalated permission and repeat the dry run.

How are screenshot folder names mapped to App Store Connect locales?

Folders named de, es, and nl map to de-DE, es-ES, and nl-NL respectively. Folders named da, el, fi, fr-CA, hi, hr, it, pl, sv, tr, and en-GB pass through unchanged as locale codes.

Why does a locale show the wrong screenshots after upload?

A locale with a store localisation but no screenshots of its own falls back to the primary locale, which is standard App Store behaviour, not an upload failure. To give it its own screenshots, stage images for that locale, add it to the --locale list, and dry-run before applying.

What are the limits for App Store screenshots and previews per display type?

App Store Connect accepts up to 10 screenshots and up to 3 previews per display type. Preview display-type folders omit the APP_ prefix, so the 6.9-inch preview set stages under IPHONE_67 rather than APP_IPHONE_67.