Asc Metadata Sync
Pull, edit, validate, and push App Store Connect metadata and localizations with the canonical asc CLI workflow instead of stale fastlane-only paths.
Overview
asc metadata sync is an agent skill for the Launch phase that syncs, validates, and applies App Store Connect metadata and localizations via the asc canonical metadata workflow.
Install
npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-metadata-syncWhat is this skill?
- Canonical `asc metadata pull` workflow for app-info and version localizations
- Structured paths: `metadata/app-info/<locale>.json` and `metadata/version/<version>/<locale>.json`
- Explicit app-info ID resolution via `asc apps info list` for multi-record apps
- Copyright managed via `asc versions update`, separate from localization JSON
- Legacy `.strings` and fastlane migrate paths only when explicitly requested
- Canonical locale files under metadata/app-info and metadata/version paths
- Separates copyright updates via asc versions update from localization JSON
Adoption & trust: 1.1k installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your App Store copy lives only in Connect or legacy fastlane folders, so localization updates are error-prone and hard for an agent to review in git.
Who is it for?
Indie iOS developers using asc who want versioned, locale-aware metadata in the repo before App Store submission or ASO tweaks.
Skip if: Android Play Console workflows, teams with no App Store Connect API or asc access, or one-off copy edits with no repeat release cadence.
When should I use this skill?
When updating App Store metadata, localizations, keywords, or migrating legacy fastlane metadata with the current asc canonical metadata workflow.
What do I get? / Deliverables
After the skill runs, canonical locale JSON is pulled and edited locally, validated, and ready to apply back to App Store Connect with explicit version and app-info targeting.
- Pulled metadata JSON per locale
- Validated and applied store listing updates
Recommended Skills
Journey fit
Store listing copy, keywords, and version fields are updated when preparing launch and store visibility, not during initial codebase scaffolding. Keywords, descriptions, and localized JSON map directly to app-store optimization and ASO listing maintenance.
How it compares
CLI-first App Store Connect metadata sync—not a generic SEO content skill or Xcode UI localization export alone.
Common Questions / FAQ
Who is asc-metadata-sync for?
Solo and indie iOS builders managing App Store listings with the asc tool who want metadata versioned alongside code and release tags.
When should I use asc-metadata-sync?
During Launch ASO when updating keywords and descriptions, before a version submission, or when migrating legacy fastlane metadata to the canonical asc JSON layout.
Is asc-metadata-sync safe to install?
It drives real App Store Connect changes when apply commands run; review the Security Audits panel on this Prism page and use staging app IDs where possible.
SKILL.md
READMESKILL.md - Asc Metadata Sync
# asc metadata sync Use this skill to keep App Store metadata in sync with App Store Connect. Prefer the canonical `asc metadata` workflow for app-info and version localization fields. Use the lower-level `asc localizations` and `asc migrate` commands only when the user specifically needs `.strings` files or legacy fastlane-format metadata. ## Current canonical workflow ### 1. Pull canonical metadata ```bash asc metadata pull --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" ``` If the app has multiple app-info records, resolve the app-info ID first and pass it explicitly: ```bash asc apps info list --app "APP_ID" --output table asc metadata pull --app "APP_ID" --app-info "APP_INFO_ID" --version "1.2.3" --platform IOS --dir "./metadata" ``` ### 2. Edit local files Canonical files are written under: - `metadata/app-info/<locale>.json` for app-level fields: `name`, `subtitle`, `privacyPolicyUrl`, `privacyChoicesUrl`, `privacyPolicyText` - `metadata/version/<version>/<locale>.json` for version fields: `description`, `keywords`, `marketingUrl`, `promotionalText`, `supportUrl`, `whatsNew` Copyright is not a localization field. Manage it with: ```bash asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company" ``` ### 3. Validate before upload ```bash asc metadata validate --dir "./metadata" --output table ``` For subscription apps, include the extra Terms of Use / EULA heuristic: ```bash asc metadata validate --dir "./metadata" --subscription-app --output table ``` ### 4. Preview and apply Run a dry run first: ```bash asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --dry-run --output table ``` Apply after the plan looks correct: ```bash asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" ``` Use `asc metadata apply` when the user wants the apply-named command shape for the same canonical files: ```bash asc metadata apply --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --dry-run asc metadata apply --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" ``` ## Keyword-only workflow Use this when only the version-localization `keywords` field should change: ```bash asc metadata keywords diff --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" asc metadata keywords apply --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --confirm ``` For importing keyword research: ```bash asc metadata keywords import --dir "./metadata" --version "1.2.3" --locale "en-US" --input "./keywords.csv" asc metadata keywords sync --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --input "./keywords.csv" ``` ## Quick field updates For one-off version-localization edits, pass an explicit version selector. Use `--version-id` for deterministic updates when you already have it, or `--version` plus `--platform` when working from a version string. ```bash asc apps info edit --app "APP_ID" --version-id "VERSION_ID" --locale "en-US" --whats-new "Bug fixes and improvements" asc apps info edit --app "APP_ID" --version "1.2.3" --platform IOS --locale "en-US" --description "Your app description here" asc apps info edit --app "APP_ID" --version "1.2.3" --platform IOS --locale "en-US" --keywords "keyword1,keyword2,keyword3" asc apps info edit --app "APP_ID" --version "1.2.3" --platform IOS --locale "en-US" --support-url "https://support.example.com" ``` For app-info fields, prefer the post-create setup command: ```bash asc app-setup info set --app "APP_ID" --primary-locale "en-US" --privacy-policy-url "https://example.com/privacy" asc app-setup info set --app "APP_ID" --locale "en-US" --name "Your App Name" --subtitle "Your subtitle"