asc-metadata-sync

Sync, validate, and apply App Store Connect metadata using the asc CLI canonical workflow.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-metadata-sync-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-metadata-sync
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/asc-metadata-sync
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-metadata-sync-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping App Store metadata (names, subtitles, descriptions, keywords, localizations) in sync with App Store Connect is error-prone when done manually through the web UI or legacy fastlane files. This Skill provides a canonical pull-edit-validate-push workflow via the asc CLI so metadata changes are reviewed, validated against character limits, and applied safely. ## Core Features & Use Cases - Canonical metadata sync: Pull app-info and version localization JSON files, edit locally, validate, dry-run, and push back to App Store Connect. - Keyword management: Diff, import, and apply keyword-only updates from CSV research files without touching other fields. - Review-gated apply: Generate review artifacts with asc metadata plan, approve selectively, and apply with confirmation for auditable changes. - Legacy migration: Export, validate, and import fastlane-format metadata trees, plus .strings localization import/export when needed. - Use Case: Before releasing version 1.2.3, pull the current metadata, update the en-US description and keywords, validate against App Store character limits, preview the diff with a dry run, then push the approved changes. ## Quick Start Ask the agent to pull the App Store metadata for your app and version into a local metadata directory, then validate and dry-run a push of your edits.

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 metadata with App Store Connect from the command line?▼

Use the asc metadata workflow: run asc metadata pull with your app ID, version, and platform to download canonical JSON files, edit them locally, run asc metadata validate, then preview with asc metadata push --dry-run before applying.

How do I update App Store keywords without changing other metadata?▼

Use the keyword-only workflow: asc metadata keywords diff to preview changes and asc metadata keywords apply --confirm to push. You can also import keyword research from CSV with asc metadata keywords import and sync it.

Can I migrate legacy fastlane metadata to App Store Connect?▼

Yes. Use asc migrate export to generate a fastlane-format tree, asc migrate validate to check it, and asc migrate import with --dry-run then --confirm to push it. This path is intended only for existing fastlane-format metadata.

What are the App Store character limits for metadata fields?▼

Name and subtitle are limited to 30 characters, keywords to 100 comma-separated characters, description and What's New to 4000 characters, and promotional text to 170 characters. Run asc metadata validate to check files before uploading.

How do I review metadata changes before applying them?▼

Use the review workflow from asc 2.6.1: asc metadata plan creates a review artifact, asc metadata approve marks changes approved (all, by key, or by scope), asc metadata status shows progress, and asc metadata apply --confirm pushes only approved changes.