Localize App Store Listings for Openclaw

Localize and update App Store listing copy across storefronts with agent-written translations, MetaRun previews, and verified publishing.

iderasyh
v1.0.0
Oct 7, 2026
0
132
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install metarun-localize-listing

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install metarun-localize-listing using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Localize App Store Listings?

This skill helps an AI agent localize or edit App Store listing content across languages through MetaRun. The agent writes and translates the copy; MetaRun stages changes per locale behind previews and applies them after confirmation. It supports app names, subtitles, descriptions, keywords, What's New, promotional text, and URLs.

Openclaw Skills users can use it to manage localization with clear checks for editable listing surfaces, Apple character limits, keyword quality, and missing locale coverage. Translation is not performed server-side: the agent is responsible for preserving tone, meaning, and brand terminology. Every change is previewed before application, then verified against listing coverage.

Localize App Store Listings Use Cases

  • Translate an App Store listing into a newly supported language.
  • Update descriptions, subtitles, keywords, or promotional text across existing locales.
  • Identify empty or incomplete fields with listing coverage before starting a localization task.
  • Prepare localized What's New copy for an app update.
  • Improve locale-specific keyword sets using ASO linting and cross-locale indexing information.
  • Review staged changes before applying them, especially promotional text that may publish immediately on a live app.

How Localize App Store Listings Works

  1. Inspect existing listing metadata and version localizations, then check coverage to identify missing fields and locales.
  2. Check listing editability to determine which localization surfaces are open and which are locked.
  3. Select valid locale codes when adding languages, and write or translate the requested copy while preserving brand terms and character budgets.
  4. Validate keywords with ASO linting and consult cross-locale indexing information to avoid duplication and make effective use of storefront indexing.
  5. Preview changes for each locale on the appropriate surface: app-info or version localization.
  6. Present the staged changes to the user, then apply each change using its confirmation token.
  7. Read listing coverage again, address any remaining requested gaps, and report which languages were updated.

Localize App Store Listings Setup

The skill requires npx and access to MetaRun tools through its MCP server or CLI. Authenticate with MetaRun login, or provide a METARUN_TOKEN personal access token. Login stores credentials in ~/.metarun/config.json.

npx metarun login

Use the CLI to inspect available tool schemas and invoke a tool when needed:

npx metarun tools <tool-name> --json
npx metarun run <tool-name> '<json>'

The token is optional when login has already stored credentials. Check listing editability before attempting writes, and preview every change before applying it.

Localize App Store Listings Data Schema & Taxonomy

Listing content is organized by locale across two distinct App Store surfaces:

Surface Typical fields Workflow
App-info localization Store name, subtitle, privacy URLs Preview with apple_preview_set_app_info_localization, then apply with apple_apply_set_app_info_localization
Version localization Description, keywords, What's New, promotional text, support and marketing URLs Preview with apple_preview_set_version_localization, then apply with apple_apply_set_version_localization
  • apple_list_app_metadata reads metadata across current locales; apple_list_version_localizations reads copy for the editable version.
  • apple_get_listing_coverage reports filled and empty fields by language and identifies gaps.
  • apple_list_supported_locales provides valid locale codes. Creating an app-info localization requires a store name in its payload; creating a version localization requires the locale.
  • Apple character limits: name 30, subtitle 30, keywords 100, promotional text 170, and description 4,000 characters.
  • What's New is available only for updates, not a first release. Promotional text can publish immediately on a live app.
  • The skill does not describe generating local files. MetaRun stores authentication configuration after login, and changes are recorded in change history and can be reverted per change.

Localize App Store Listings Advanced Features

  • Uses editability checks to distinguish open localization surfaces from locked ones before writing.
  • Supports locale coverage reporting to find incomplete fields and verify that requested languages were actually updated.
  • Applies changes through preview-and-confirm workflows, with separate tools for app-info and version localizations.
  • Runs aso_lint_metadata to detect keyword violations and duplication.
  • Uses aso_cross_locale_plan to understand which additional locales each storefront indexes and plan keyword sets accordingly.
  • Treats promotional text on a live app as an immediate publish and avoids writing What's New for a first release.
  • Provides change-history-based reversibility for applied changes.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*