Asc Metadata Sync
- 2.2k installs
- 934 repo stars
- Updated July 21, 2026
- rorkai/app-store-connect-cli-skills
This is a copy of asc-metadata-sync by rudrankriyam - installs and ranking accrue to the original listing.
asc-metadata-sync is an agent skill that syncs, validates, and applies App Store Connect metadata and localizations through the asc CLI canonical workflow for mobile release managers.
About
asc-metadata-sync is a Rork agent skill for iOS developers and release engineers managing App Store listing data with the asc CLI. It documents the canonical asc metadata pull and apply flow for app-info and version localization fields, plus lower-level asc localizations and asc migrate paths for .strings files or legacy fastlane-format metadata when needed. Developers reach for asc-metadata-sync when updating titles, descriptions, keywords, or locale files and want App Store Connect to match the repo without manual copy-paste errors. The skill assumes asc as the source of truth and steers agents away from ad hoc edits that drift from Connect.
- Pulls canonical metadata into structured JSON files under metadata/app-info and metadata/version directories
- Supports explicit app-info ID resolution for apps with multiple records
- Handles app-level fields (name, subtitle, privacy urls) and version-level fields (description, keywords, promotional tex
- Provides lower-level asc localizations and asc migrate commands for .strings files or legacy fastlane metadata
- Canonical workflow that replaces error-prone manual updates and legacy fastlane pipelines
Asc Metadata Sync by the numbers
- 2,153 all-time installs (skills.sh)
- +228 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-metadata-syncAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.2k |
|---|---|
| repo stars | ★ 934 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 21, 2026 |
| Repository | rorkai/app-store-connect-cli-skills ↗ |
How do you sync App Store metadata with App Store Connect?
Keep App Store metadata, localizations, and keywords synchronized with App Store Connect without manual copy-paste errors.
Who is it for?
iOS release engineers maintaining App Store listings who already use or want to adopt the asc CLI workflow.
Skip if: Android Play Console metadata workflows or teams that only edit listings manually in the App Store Connect web UI.
When should I use this skill?
The user mentions updating App Store metadata, localizations, keywords, asc metadata pull, or migrating legacy fastlane metadata.
What you get
Validated canonical metadata files, synchronized localizations, and applied App Store Connect listing updates.
- Synced metadata files
- Applied App Store Connect localization updates
Files
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
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:
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>.jsonfor app-level fields:name,subtitle,privacyPolicyUrl,privacyChoicesUrl,privacyPolicyTextmetadata/version/<version>/<locale>.jsonfor version fields:description,keywords,marketingUrl,promotionalText,supportUrl,whatsNew
Copyright is not a localization field. Manage it with:
asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"3. Validate before upload
asc metadata validate --dir "./metadata" --output tableFor subscription apps, include the extra Terms of Use / EULA heuristic:
asc metadata validate --dir "./metadata" --subscription-app --output table4. Preview and apply
Run a dry run first:
asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --dry-run --output tableApply after the plan looks correct:
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:
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:
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" --confirmFor importing keyword research:
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.
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:
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"Lower-level localization files
Use .strings files when the user specifically wants import/export files instead of canonical JSON:
asc localizations list --version "VERSION_ID" --output table
asc localizations download --version "VERSION_ID" --path "./localizations"
asc localizations upload --version "VERSION_ID" --path "./localizations" --dry-run
asc localizations upload --version "VERSION_ID" --path "./localizations"For app-info localizations:
asc apps info list --app "APP_ID" --output table
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --output table
asc localizations download --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"
asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations" --dry-run
asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"Legacy fastlane metadata
Use this only for existing fastlane-format trees:
asc migrate export --app "APP_ID" --version-id "VERSION_ID" --output-dir "./fastlane"
asc migrate validate --fastlane-dir "./fastlane"
asc migrate import --app "APP_ID" --version-id "VERSION_ID" --fastlane-dir "./fastlane" --dry-run
asc migrate import --app "APP_ID" --version-id "VERSION_ID" --fastlane-dir "./fastlane"Character limits
| Field | Limit |
|---|---|
| Name | 30 |
| Subtitle | 30 |
| Keywords | 100 comma-separated characters |
| Description | 4000 |
| What's New | 4000 |
| Promotional Text | 170 |
Agent behavior
- Start with
asc metadata pullunless the user specifically asks for.stringsor fastlane metadata. - Always run
asc metadata validatebefore remote writes. - Preview remote changes with
--dry-runwhen the command supports it. - For quick edits, always pass
--version-idor--versionplus--platform; do not rely on ambiguous latest-version behavior. - Keep app-info fields and version fields separate.
- Use
--output tablefor human verification and JSON for automation.
Related skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.10.9k38.3k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.6.9k37.1k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.8k71.1k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.3k23.1k
Opensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4k234k
OnboardingInstall this skill to create your first LaunchDarkly boolean flag, add evaluation code, and prove OFF then ON behavior end-to-end after the SDK is in place.3.8k20How it compares
Use asc-metadata-sync for repo-driven App Store listing sync; use competitor-tracking when the goal is monitoring rival app store changes.
FAQ
What is the canonical asc-metadata-sync workflow?
asc-metadata-sync prefers asc metadata pull and apply for app-info and version localization fields, using asc localizations or asc migrate only when .strings files or legacy fastlane metadata are required.
Does asc-metadata-sync replace manual App Store Connect edits?
asc-metadata-sync automates bidirectional sync between local canonical metadata and App Store Connect via asc CLI commands, reducing copy-paste errors when updating titles, descriptions, and keywords.
Is Asc Metadata Sync safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.