How do I install the Appstore Metadata Sync skill?

Run npx skillmds@latest add xopoko/appstore-metadata-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Appstore Metadata Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Appstore Metadata Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Appstore Metadata Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Appstore Metadata Sync?

Xopoko (@xopoko) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Appstore Metadata Sync by xopoko — Agent Skill

Name: Appstore Metadata Sync
Author: Xopoko

Appstore Metadata Sync

App Store metadata JSON: edit, validate, push, or sync canonical `./metadata`, plus legacy fastlane migration via `asc migrate`. Excludes translation-first work, standalone release notes, and IAP/subscription names.

Xopoko 8af7ce6 4 files · 17.4 KB Updated Sep 17, 2026

File contents

App Store Metadata Sync

Prefer canonical asc metadata JSON for app-info and version fields. Use .strings or fastlane flows only when specifically needed.

Use appstore-metadata-localizer when the main work is translation/adaptation across locales. Use appstore-release-notes-writer for What's New copy. Use appstore-subscription-localizer for subscription, group, or IAP display-name localizations.

Command Plan Helper

For a deterministic dry-run command plan, run the helper from the plugin root:

python3 "$PLUGIN_ROOT/skills/appstore-metadata-sync/scripts/metadata_sync_plan.py" \
  --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" \
  --app-info "APP_INFO_ID" --version-id "VERSION_ID" \
  --include-keywords --keywords-csv "./keywords.csv"

The helper prints commands only; it does not call ASC, mutate metadata, or read credentials. Pass --json for machine-readable output. Pass --confirming-actions only after manually verifying generated --confirm commands.

Workflow

Pull canonical metadata JSON into ./metadata before editing unless the user already provided a fresh metadata tree.
Resolve APP_INFO_ID when multiple app-info records exist.
Edit the owning JSON fields: app-info fields for name/subtitle/privacy text and version fields for description, keywords, marketing URL, promotional text, support URL, and What's New.
Validate locally, then run push --dry-run; apply/push without dry-run only after the diff and target app/version are confirmed.
Use alternate .strings or fastlane migration flows only for legacy repos or explicit user requests.

Limits: name/subtitle 30, keywords 100, description/What's New 4000, promotional text 170. Use table output for human verification and JSON for automation.

References

references/appstore-metadata-sync.md for detailed canonical JSON, keyword, quick-edit, .strings, and fastlane commands.

---name: appstore-metadata-syncdescription: App Store metadata JSON: edit, validate, push, or sync canonical `./metadata`, plus legacy fastlane migration via `asc migrate`. Excludes translation-first work, standalone release notes, and IAP/subscription names.---# App Store Metadata SyncPrefer canonical `asc metadata` JSON for app-info and version fields. Use `.strings` or fastlane flows only when specifically needed.Use `appstore-metadata-localizer` when the main work is translation/adaptation across locales. Use `appstore-release-notes-writer` for What's New copy. Use `appstore-subscription-localizer` for subscription, group, or IAP display-name localizations.## Command Plan HelperFor a deterministic dry-run command plan, run the helper from the plugin root:```bashpython3 "$PLUGIN_ROOT/skills/appstore-metadata-sync/scripts/metadata_sync_plan.py" \ --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" \ --app-info "APP_INFO_ID" --version-id "VERSION_ID" \ --include-keywords --keywords-csv "./keywords.csv"```The helper prints commands only; it does not call ASC, mutate metadata, or read credentials. Pass `--json` for machine-readable output. Pass `--confirming-actions` only after manually verifying generated `--confirm` commands.## Workflow1. Pull canonical metadata JSON into `./metadata` before editing unless the user already provided a fresh metadata tree.2. Resolve `APP_INFO_ID` when multiple app-info records exist.3. Edit the owning JSON fields: app-info fields for name/subtitle/privacy text and version fields for description, keywords, marketing URL, promotional text, support URL, and What's New.4. Validate locally, then run `push --dry-run`; apply/push without dry-run only after the diff and target app/version are confirmed.5. Use alternate `.strings` or fastlane migration flows only for legacy repos or explicit user requests.Limits: name/subtitle 30, keywords 100, description/What's New 4000, promotional text 170. Use table output for human verification and JSON for automation.## References- `references/appstore-metadata-sync.md` for detailed canonical JSON, keyword, quick-edit, `.strings`, and fastlane commands.

Frequently asked questions