asc-metadata-sync
Skill6 starsChanged 33 days agoMITView on GitHub
Sync and validate App Store metadata and localizations with asc, including legacy metadata format migration. Use when updating metadata or translations.
8 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- VelimirMueller/claude-skillstheir own version, first seen Nov 1, 2026
- VelimirMueller/ai-development-skillstheir own version, first seen Nov 1, 2026
- deonmenezes/mobile-app-skilledited, first seen Nov 1, 2026
- rorkai/app-store-connect-cli-skillstheir own version, first seen Oct 26, 2026
- CamilleScholtz/swmpcedited, first seen Oct 8, 2026
- malpern/VoxClawedited, first seen Oct 8, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- CamilleScholtz/swmpc★ 23913% same
- malpern/VoxClaw★ 20880% same
- deonmenezes/mobile-app-skill★ 410% same
- moasq/ios-dev-agent★ 413% same
Wrote their own version · 4
- rudrankriyam/app-store-connect-cli-skills★ 1.1ksame name
- rorkai/app-store-connect-cli-skills★ 1.1ksame name
- VelimirMueller/ai-development-skills★ 7same name
- VelimirMueller/claude-skills★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository79 other files it gives its agents.
- adr-phase-coverageSkill
- aposd-red-flag-reviewSkill
- apple-on-device-aiSkill
- artifact-gatesSkill
- asc-app-create-uiSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- choose-boring-technologySkill
- ci-preflightSkill
- conways-lawSkill
- cost-routingSkill
- cost-tier-routingSkill
- cunninghams-lawSkill
- ddd-strategic-auditSkill
- ddd-tactical-reviewSkill
- debug-test-captureSkill
- developing-ios-appsSkill
- doerrs-lawSkill
- fitts-lawSkill
- fix-regression-guardSkill
- galls-lawSkill
- goodharts-lawSkill
- greenspuns-tenth-ruleSkill
- gsd-core-hooksSkill
- hofstadters-lawSkill
- hyrums-lawSkill
- ios-accessibilitySkill
- ios-simulator-boot-healthSkill
- kerckhoffs-principleSkill
- kernighans-lawSkill
- knuths-optimization-principleSkill
- lady-lovelaces-objectionSkill
- leaky-abstractionsSkill
- linuss-lawSkill
- mobile-ios-designSkill
- money-boundary-judgmentSkill
- moores-lawSkill
- no-deferSkill
- norvigs-lawSkill
- parkinsons-lawSkill
- peter-principleSkill
- postels-lawSkill
- post-fix-traceSkill
- qa-test-architectSkill
- rubber-duckSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to keep local metadata in sync with App Store Connect.
- Very specific: line 40
Note: If you get "multiple app infos found", you must specify --app-info with the correct ID.
- Very specific: line 143
Use asc migrate validate to check limits before upload.
- Very specific: line 148
Use asc localizations list to confirm available locales and IDs.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
asc metadata sync
Use this skill to keep local metadata in sync with App Store Connect.
Two Types of Localizations
1. Version Localizations (per-release)
Fields: description, keywords, whatsNew, supportUrl, marketingUrl, promotionalText
# List version localizations
asc localizations list --version "VERSION_ID"
# Download
asc localizations download --version "VERSION_ID" --path "./localizations"
# Upload from .strings files
asc localizations upload --version "VERSION_ID" --path "./localizations"2. App Info Localizations (app-level)
Fields: name, subtitle, privacyPolicyUrl, privacyChoicesUrl, privacyPolicyText
# First, find the app info ID
asc app-infos list --app "APP_ID"
# List app info localizations
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID"
# Upload app info localizations
asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"Note: If you get "multiple app infos found", you must specify --app-info with the correct ID.
Legacy Metadata Format Workflow
Export current state
asc migrate export --app "APP_ID" --output "./metadata"Validate local files
# Use --help to discover flags for your metadata directory
asc migrate validate --helpThis checks character limits and required fields.
Import updates
# Use --help to discover flags for your metadata directory
asc migrate import --helpQuick Field Updates
Version-specific fields
# What's New
asc app-info set --app "APP_ID" --locale "en-US" --whats-new "Bug fixes and improvements"
# Description
asc app-info set --app "APP_ID" --locale "en-US" --description "Your app description here"
# Keywords
asc app-info set --app "APP_ID" --locale "en-US" --keywords "keyword1,keyword2,keyword3"
# Support URL
asc app-info set --app "APP_ID" --locale "en-US" --support-url "https://support.example.com"Version metadata
# Copyright
asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"
# Release type
asc versions update --version-id "VERSION_ID" --release-type AFTER_APPROVALTestFlight notes
asc build-localizations create --build "BUILD_ID" --locale "en-US" --whats-new "TestFlight notes here".strings File Format
For bulk updates, use .strings files:
// en-US.strings
"description" = "Your app description";
"keywords" = "keyword1,keyword2,keyword3";
"whatsNew" = "What's new in this version";
"supportUrl" = "https://support.example.com";For app-info type:
// en-US.strings (app-info type)
"privacyPolicyUrl" = "https://example.com/privacy";
"name" = "Your App Name";
"subtitle" = "Your subtitle";Multi-Language Workflow
- Export all localizations:
asc localizations download --version "VERSION_ID" --path "./localizations"- Translate the .strings files (or use translation service)
- Upload all at once:
asc localizations upload --version "VERSION_ID" --path "./localizations"- Verify:
asc localizations list --version "VERSION_ID" --output tableCharacter Limits
| Field | Limit |
| Name | 30 |
| Subtitle | 30 |
| Keywords | 100 (comma-separated) |
| Description | 4000 |
| What's New | 4000 |
| Promotional Text | 170 |
Use asc migrate validate to check limits before upload.
Notes
- Version localizations and app info localizations are different; use the right command and
--typeflag. asc migrate validateenforces character limits before upload.- Use
asc localizations listto confirm available locales and IDs. - Privacy Policy URL is in app info localizations, not version localizations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

