Back to Skills

asc-metadata-sync

Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.

817stars44forksUpdated 5/26/2026

Security Assessment

Safe(100/100)
Security Score100/100

About asc-metadata-sync

The asc-metadata-sync skill helps teams keep App Store metadata aligned with App Store Connect using the current canonical metadata workflow. It is designed for syncing, validating, and applying metadata changes across app-level and version-level localization content while reducing manual update errors. This skill is especially useful when updating App Store listing content such as names, subtitles, descriptions, keywords, promotional text, or support links, and also supports teams migrating from legacy fastlane metadata into the newer canonical structure. By organizing metadata into local files and validating changes before upload, it creates a repeatable workflow for maintaining consistency between source-controlled metadata and App Store Connect.

Its core capabilities include pulling canonical metadata into a local directory, editing localized JSON files, validating metadata before upload, previewing changes through dry runs, and applying updates back to App Store Connect. It also supports a keyword-focused workflow for comparing, importing, and syncing keywords independently when only keyword metadata needs updating. For targeted changes, the skill includes quick field update workflows for editing version-localization content or app-info fields without running a full metadata sync. Lower-level localization and migration commands remain available when `.strings` files or legacy fastlane-format metadata are specifically required.

This skill is intended for developers, release engineers, App Store operations teams, and product or marketing contributors responsible for App Store metadata management. It is particularly valuable for teams managing localized metadata across multiple versions, maintaining metadata as part of a release workflow, or migrating existing metadata pipelines to the current asc canonical metadata structure. It works well in environments where metadata is reviewed locally before validation and deployment.

FAQ

When should I use asc-metadata-sync?

Use this skill when you need to sync App Store metadata with App Store Connect, update localization content, manage keywords, or migrate legacy fastlane metadata into the canonical metadata workflow.

Can I update only keywords without applying all metadata?

Yes. The skill includes a keyword-only workflow for diffing, importing, and applying changes specifically to the version-localization keywords field.

Does this support both app-level and version-level metadata?

Yes. The workflow distinguishes between app-info fields such as name or subtitle and version-localization fields such as description, keywords, promotional text, support URL, and what's new.

Do I need to validate metadata before pushing changes?

Validation is part of the recommended workflow. The skill supports validating metadata before upload so changes can be reviewed before being applied.

Are legacy metadata formats supported?

Yes, but only for specific cases. Lower-level migration commands are intended for `.strings` files or legacy fastlane-format metadata when those formats are explicitly needed.

Install asc-metadata-sync

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill