asc-metadata-sync

Synchronize App Store Connect metadata and localizations with local .strings files.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/jul-sh/clipkitty-sparkle-test --skill asc-metadata-sync-jul-sh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-metadata-sync
Source: https://github.com/jul-sh/clipkitty-sparkle-test/tree/main/.agents/skills/asc-metadata-sync
Command: npx skills add https://github.com/jul-sh/clipkitty-sparkle-test --skill asc-metadata-sync-jul-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of keeping your application's metadata and translations consistent between your local development environment and App Store Connect.

Core Features & Use Cases

  • Version Localization Management: Download and upload descriptions, keywords, and "What's New" text for specific app versions.
  • App Info Localization Management: Manage app-level metadata like name, subtitle, and privacy URLs across different languages.
  • Legacy Metadata Migration: Export, validate, and import metadata using the legacy format.
  • Quick Field Updates: Directly update specific metadata fields via command line.
  • Use Case: After translating your app's description into five new languages, use this Skill to upload all the translated .strings files to App Store Connect for the current version.

Quick Start

Use the asc-metadata-sync skill to download all version localizations for version ID '123456789' to the './localizations' directory.

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 localizations with local files?

To sync App Store Connect metadata, you can synchronize version-specific and app-level information directly with local files. This facilitates bulk updates via .strings files and ensures consistency across multiple languages.

Can I bulk upload translated .strings files to App Store Connect?

Yes, you can bulk upload translated .strings files to App Store Connect. This allows you to manage descriptions, keywords, and "What's New" text across multiple languages for specific app versions efficiently.

How do I migrate legacy App Store metadata formats?

You can migrate legacy App Store metadata formats by exporting, validating, and importing the metadata using the legacy format migration tools. This ensures older metadata structures are compatible with current App Store Connect requirements.

Does this metadata sync method support both app-level and version-specific information?

Yes, the metadata sync supports both app-level and version-specific information. You can manage app-level metadata like name, subtitle, and privacy URLs alongside version-specific descriptions and keywords across different languages.

What is the best way to manage app store presence across multiple languages?

The best way to manage app store presence across multiple languages is synchronizing App Store Connect localizations with local files. This ensures translated metadata complies with character limits and maintains consistency between your development environment and the app store.

Why do I need to validate metadata before migrating legacy formats?

Validating metadata before migrating legacy formats ensures compliance with App Store Connect character limits and structural requirements. This prevents upload errors and guarantees that your app store presence remains accurate across all localized versions.