PaperclipOrg
Claude Agent Skill · by Rudrankriyam

Asc Metadata Sync

Install Asc Metadata Sync skill for Claude Code from rudrankriyam/app-store-connect-cli-skills.

Install
Terminal · npx
$npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-metadata-sync
Works with Paperclip

How Asc Metadata Sync fits into a Paperclip company.

Asc Metadata Sync drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

E
E-Commerce EmpirePaired

Pre-configured AI company — 20 agents, 9 skills, one-time purchase.

$59$89
Explore pack
Source file
SKILL.md148 lines
Expand
---name: asc-metadata-syncdescription: Sync and validate App Store metadata and localizations with asc, including legacy metadata format migration. Use when updating metadata or translations.--- # 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` ```bash# List version localizationsasc localizations list --version "VERSION_ID" # Downloadasc localizations download --version "VERSION_ID" --path "./localizations" # Upload from .strings filesasc localizations upload --version "VERSION_ID" --path "./localizations"``` ### 2. App Info Localizations (app-level)Fields: `name`, `subtitle`, `privacyPolicyUrl`, `privacyChoicesUrl`, `privacyPolicyText` ```bash# First, find the app info IDasc apps info list --app "APP_ID" # List app info localizationsasc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID" # Upload app info localizationsasc 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 Fastlane Metadata Workflow ### Export current state```bashasc migrate export --app "APP_ID" --version-id "VERSION_ID" --output-dir "./fastlane"``` ### Validate local files```bashasc migrate validate --fastlane-dir "./fastlane"```This checks character limits and required fields. ### Import updates```bashasc migrate import --app "APP_ID" --version-id "VERSION_ID" --fastlane-dir "./fastlane" --dry-runasc migrate import --app "APP_ID" --version-id "VERSION_ID" --fastlane-dir "./fastlane"``` ## Quick Field Updates ### Version-specific fields```bash# What's Newasc apps info edit --app "APP_ID" --locale "en-US" --whats-new "Bug fixes and improvements" # Descriptionasc apps info edit --app "APP_ID" --locale "en-US" --description "Your app description here" # Keywordsasc apps info edit --app "APP_ID" --locale "en-US" --keywords "keyword1,keyword2,keyword3" # Support URLasc apps info edit --app "APP_ID" --locale "en-US" --support-url "https://support.example.com"``` ### Version metadata```bash# Copyrightasc versions update --version-id "VERSION_ID" --copyright "2026 Your Company" # Release typeasc versions update --version-id "VERSION_ID" --release-type AFTER_APPROVAL``` ### TestFlight notes```bashasc 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 1. Export all localizations:```bashasc localizations download --version "VERSION_ID" --path "./localizations"``` 2. Translate the .strings files (or use translation service) 3. Upload all at once:```bashasc localizations upload --version "VERSION_ID" --path "./localizations"``` 4. Verify:```bashasc localizations list --version "VERSION_ID" --output table``` ## Character Limits | Field | Limit ||-------|-------|| Name | 30 || Subtitle | 30 || Keywords | 100 (comma-separated) || Description | 4000 || What's New | 4000 || Promotional Text | 170 | Use `asc metadata validate --dir "./metadata"` for canonical metadata trees.Use `asc migrate validate --fastlane-dir "./fastlane"` for legacy fastlane-format metadata. ## Notes- Version localizations and app info localizations are different; use the right command and `--type` flag.- Use `asc localizations list` to confirm available locales and IDs.- Privacy Policy URL is in app info localizations, not version localizations.