asc-metadata-sync

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

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-metadata-sync-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-metadata-sync
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-metadata-sync
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-metadata-sync-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping App Store metadata consistent between local files and App Store Connect is error-prone, especially across multiple locales, app-info records, and version localizations. This Skill standardizes the pull-edit-validate-push cycle so metadata changes are reviewed and applied safely. ## Core Features & Use Cases - Canonical metadata workflow: Pull app-info and version localization JSON files, edit them locally, validate against App Store field limits, and push with dry-run previews. - Review-gated apply: Generate review artifacts with asc metadata plan, approve selectively by key or scope, and apply only after explicit confirmation. - Keyword and quick-edit flows: Diff and apply keyword-only updates, import keyword research from CSV, or make one-off field edits with explicit version selectors. - Use Case: You need to update the en-US description and keywords for version 1.2.3. Pull the canonical metadata, edit the JSON files, run validation, preview with a dry run, then push the changes to App Store Connect. ## Quick Start Ask the agent to pull the App Store metadata for your app and version, update the description and keywords, validate the changes, and push them after a dry-run preview.

Frequently Asked Questions about asc-metadata-sync

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

FAQPage Schema
How do I update App Store metadata from the command line?▼

Use the asc metadata workflow: pull canonical JSON files with asc metadata pull, edit them locally, run asc metadata validate, preview with asc metadata push --dry-run, then push without the flag to apply changes to App Store Connect.

How do I update App Store keywords for a specific version?▼

Use asc metadata keywords diff to preview keyword changes against the local metadata directory, then asc metadata keywords apply with --confirm to push them. You can also import keyword research from a CSV file with asc metadata keywords import.

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 fields before uploading.

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 trees.

How do I review metadata changes before applying them?▼

Use asc metadata plan to create a review artifact, then asc metadata approve to approve all changes or specific keys and scopes, and asc metadata status to inspect the review state. Apply with asc metadata apply --confirm once approved.