asc-metadata-sync

Synchronize App Store metadata and localization files with the asc command-line tool.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-metadata-sync-curtislmartin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-metadata-sync
Source: https://github.com/curtislmartin/daily-ascent-engineering/tree/main/skills_repo/asc-metadata-sync
Command: npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-metadata-sync-curtislmartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and product teams spend excessive time manually syncing App Store Connect metadata, handling version‑specific and app‑info localizations, and migrating legacy metadata formats, which leads to errors and delays.

Core Features & Use Cases

  • Version Localizations Management: List, download, and upload .strings files for each app version.
  • App Info Localizations: Manage app‑level fields such as name, subtitle, and privacy URLs across locales.
  • Legacy Migration Workflow: Export, validate, and import metadata using asc migrate commands.
  • Quick Field Updates: Update description, keywords, support URL, and other fields with simple asc commands.
  • Multi‑Language Batch Processing: Download all localizations, translate them, and upload the updated files for multiple languages in one step.

Quick Start

Run the asc‑metadata‑sync skill to download current localizations, translate them, and upload the updated .strings files for the target version.

Frequently Asked Questions about asc-metadata-sync

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

FAQPage Schema
How do I sync App Store Connect metadata and localization files for multiple languages?

App Store Connect metadata synchronization is handled by downloading current version localizations, translating the .strings files, and uploading the updated files across multiple languages in one batch process using the asc command-line tool.

What is the best way to migrate legacy App Store metadata formats for iOS apps?

Legacy App Store metadata migration is performed by exporting, validating, and importing metadata using the asc migrate commands, ensuring version-specific fields and character limits are correctly validated for iOS and watchOS apps.

Can I update app-level fields like name and subtitle across different locales?

App info localizations allow you to manage app-level fields such as name, subtitle, and privacy URLs across locales, validating required fields and ensuring character limits are met before uploading to App Store Connect.

Does this metadata sync workflow support batch .strings uploads for all app versions?

Batch .strings uploads are supported for version-specific localizations, allowing you to download all localizations for a target version, translate them, and upload the updated files for multiple languages in a single step.

Why does uploading app metadata fail due to character limits or missing required fields?

App Store metadata uploads fail when required fields are missing or character limits are exceeded, which this tool prevents by validating version-specific fields and app-info localizations before submitting updates to App Store Connect.