asc-metadata-sync

Synchronize local App Store metadata with App Store Connect and validate localizations.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/barronlroth/Cubby --skill asc-metadata-sync-barronlroth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-metadata-sync
Source: https://github.com/barronlroth/Cubby/tree/main/.agents/skills/asc-metadata-sync
Command: npx skills add https://github.com/barronlroth/Cubby --skill asc-metadata-sync-barronlroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs and validates App Store metadata and localizations with asc, including migration of legacy metadata formats, to keep App Store Connect in sync during updates.

Core Features & Use Cases

  • Syncs version and app-info localizations with App Store Connect and validates field consistency.
  • Supports migration of legacy metadata formats and coordinated multi-language workflows.
  • Provides practical commands for exporting, validating, and importing metadata and localizations across versions.

Quick Start

Run the asc-metadata-sync skill to synchronize local App Store metadata with App Store Connect and apply migrations.

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 local App Store metadata with App Store Connect?

You can sync local App Store metadata with App Store Connect by running the asc-metadata-sync skill to validate field consistency and update version and app-info localizations across multiple languages.

How do I migrate legacy App Store metadata formats?

Migrating legacy App Store metadata involves running export, validate, and import steps provided by the asc-metadata-sync skill to transition outdated formats into current App Store Connect localization fields.

Can I validate App Store Connect localizations for multiple languages?

Yes, validating App Store Connect localizations for multi-language workflows is supported, ensuring consistency across version fields like description, keywords, whatsNew, and app-info fields like name and subtitle.

What fields are supported when syncing version and app-info localizations?

Syncing version localizations supports description, keywords, whatsNew, supportUrl, marketingUrl, and promotionalText, while app-info localizations cover name, subtitle, privacyPolicyUrl, privacyPolicyText, and privacyChoicesUrl.

What's the best way to keep App Store Connect metadata in sync during version updates?

The best way to keep App Store Connect metadata in sync during version updates is to run the asc-metadata-sync skill, which automates localization validation and applies coordinated multi-language workflows.

Do I need any dependencies to run App Store metadata migration and validation?

No external dependencies are required to run App Store metadata migration and validation, as the skill operates independently to export, validate, and import legacy formats and localizations.