abdullah4ai/asc-metadata-sync
swiftship/internal/skills/data/features/asc-metadata-sync/SKILL.md
Sync, validate, and translate App Store metadata and localizations with asc CLI, including LLM-powered translation and legacy metadata format migration. Use when updating metadata, translations, or adding new languages.
$ install --global
skillsauthnpx skillsauth add abdullah4ai/apple-dev-docs asc-metadata-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 4:37 AM36.6s2 files scanned
SKILL.md
- name:
- asc-metadata-sync
- description:
- Sync, validate, and translate App Store metadata and localizations with asc CLI, including LLM-powered translation and legacy metadata format migration. Use when updating metadata, translations, or adding new languages.
asc metadata sync and localization
Use this skill to keep local metadata in sync with App Store Connect, and to translate metadata to multiple languages.
Command discovery
- Always confirm flags with
--helpfor the exactascversion. - Prefer explicit long flags (
--app,--version,--version-id,--type,--app-info). - Default output is JSON; use
--output tableonly for human verification steps. - Prefer deterministic ID-based operations.
Two Types of Localizations
1. Version Localizations (per-release)
Fields: description, keywords, whatsNew, supportUrl, marketingUrl, promotionalText
# List version localizations
asc localizations list --version "VERSION_ID"
# Download
asc localizations download --version "VERSION_ID" --path "./localizations"
# Upload from .strings files
asc localizations upload --version "VERSION_ID" --path "./localizations"
2. App Info Localizations (app-level)
Fields: name, subtitle, privacyPolicyUrl, privacyChoicesUrl, privacyPolicyText
# First, find the app info ID
asc app-infos list --app "APP_ID"
# List app info localizations
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID"
# Upload app info localizations
asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"
Note: If you get "multiple app infos found", you must specify --app-info with the correct ID.
Legacy Metadata Format Workflow
Export current state
asc migrate export --app "APP_ID" --output "./metadata"
Validate local files
asc migrate validate --help
Import updates
asc migrate import --help
Quick Field Updates
Version-specific fields
asc app-info set --app "APP_ID" --locale "en-US" --whats-new "Bug fixes"
asc app-info set --app "APP_ID" --locale "en-US" --description "Your description"
asc app-info set --app "APP_ID" --locale "en-US" --keywords "keyword1,keyword2"
asc app-info set --app "APP_ID" --locale "en-US" --support-url "https://support.example.com"
Version metadata
asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"
asc versions update --version-id "VERSION_ID" --release-type AFTER_APPROVAL
TestFlight notes
asc build-localizations create --build "BUILD_ID" --locale "en-US" --whats-new "TestFlight notes"
.strings File Format
Version localizations:
"description" = "Your app description";
"keywords" = "keyword1,keyword2,keyword3";
"whatsNew" = "What's new in this version";
"supportUrl" = "https://support.example.com";
App-info localizations:
"name" = "Your App Name";
"subtitle" = "Your subtitle";
"privacyPolicyUrl" = "https://example.com/privacy";
Translation Workflow (LLM-powered)
Step 1: Resolve IDs
asc apps list --output table
asc versions list --app "APP_ID" --state PREPARE_FOR_SUBMISSION --output table
asc app-infos list --app "APP_ID" --output table
Step 2: Download source locale
asc localizations download --version "VERSION_ID" --path "./localizations"
asc localizations download --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"
Step 3: Translate with LLM
See references/translation-guidelines.md for detailed translation rules, prompt template, and locale list.
Step 4: Upload translations
# Version localizations
asc localizations upload --version "VERSION_ID" --path "./localizations"
# App-info localizations
asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"
Step 5: Verify
asc localizations list --version "VERSION_ID" --output table
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --output table
Character Limits
| Field | Limit | |-------|-------| | Name | 30 | | Subtitle | 30 | | Keywords | 100 (comma-separated) | | Description | 4000 | | What's New | 4000 | | Promotional Text | 170 |
Always validate translated text fits within limits before uploading. Use asc migrate validate to check.
Agent Behavior
- Always read the source locale first — never translate from memory.
- Check existing localizations before overwriting.
- Version vs app-info is different — use the right
--typeflag. - Prefer deterministic IDs — don't auto-pick via
head -1. - Validate character limits before uploading.
- Keywords: do NOT literally translate — research locale-appropriate search terms.
- Show translations to the user before uploading for approval.
- Process one locale at a time for easier review.
- If upload fails for a locale, continue with others and report all failures at the end.
Notes
- Version localizations are tied to a specific version.
promotionalTextcan be updated anytime without a new version submission.whatsNewis only relevant for updates, not the first version.- Privacy Policy URL is in app info localizations, not version localizations.
- For subscription/IAP display name localization, use
asc-subscription-localizationskill.
Related Skills
abdullah4ai/apple-developer-toolkit
tools
VerifiedTrustedCommunity
Apple platform skill for docs, WWDC lookup, App Store Connect work, and SwiftUI app generation. Use repo-local `node cli.js` for Apple docs and WWDC search, `appledev store` for App Store Connect workflows, and `appledev build` for app scaffolding or fix loops on macOS. USE WHEN: Apple APIs, WWDC sessions, TestFlight/App Store tasks, or building/fixing Apple-platform apps. DON'T USE WHEN: non-Apple platforms, generic backend work, or general web research. EDGE CASES: docs-only queries use `node cli.js` in this repo, not `appledev`; release workflows use `appledev store`; app scaffolding uses `appledev build`; rules-only requests can read `references/ios-rules/` or `references/swiftui-guides/` progressively without invoking binaries.
8SKILL.mdUpdated Mar 27, 2026
abdullah4ai/apple-developer-toolkit
tools
VerifiedTrustedCommunity
All-in-one Apple developer skill with three integrated tools shipped as a single unified binary. (1) Documentation search across Apple frameworks, symbols, and 1,267 WWDC sessions from 2014-2025. No credentials needed. (2) App Store Connect CLI with 120+ commands covering builds (find/wait/upload), TestFlight, pre-submission validate, submissions, signing, subscriptions (family-sharable), IAP, analytics, Xcode Cloud, metadata workflows, release pipeline dashboard, insights, win-back offers, promoted purchases, product pages, nominations, accessibility declarations, pre-orders, pricing filters, localizations update, diff, webhooks with local receiver, workflow automation, and more. Requires App Store Connect API key. (3) Multi-platform app builder (iOS/watchOS/tvOS/iPad/macOS/visionOS) that generates complete Swift/SwiftUI apps from natural language with auto-fix, simulator launch, interactive chat mode, and open-in-Xcode. Requires an LLM API key and Xcode. Includes 38 iOS development rules and 12 SwiftUI best practice guides for Liquid Glass, navigation, state management, and modern APIs. All three tools ship as one binary (appledev). USE WHEN: Apple API docs, App Store Connect management, WWDC lookup, or building iOS/watchOS/tvOS/macOS/visionOS apps from scratch. DON'T USE WHEN: non-Apple platforms or general coding.
7SKILL.mdUpdated Mar 27, 2026
abdullah4ai/widgets
testing
VerifiedTrustedCommunity
watchOS complications: WidgetKit complication families, accessory sizes, timeline providers for watch face. Use when implementing watchOS-specific patterns related to widgets.
5SKILL.mdUpdated Mar 27, 2026
abdullah4ai/haptics
development
VerifiedTrustedCommunity
watchOS haptic feedback: WKInterfaceDevice preset haptic types for wrist-based feedback. Use when implementing watchOS-specific patterns related to haptics.
5SKILL.mdUpdated Mar 27, 2026