OpenClaw Playstore Automation

Installable OpenClaw plugin + standalone CLI for Google Play release operations:

• ASO + compliance audit scoring (strict target support)
• Fastlane metadata generation and optional upload
• EAS Android build + submit orchestration
• End-to-end release command (audit -> metadata -> lint -> typecheck -> build -> submit)

Install as OpenClaw plugin

From local path (development)

openclaw plugins install -l ./tools/playstore-automation

From npm package

openclaw plugins install @invoicerate/openclaw-playstore-automation

Then restart OpenClaw Gateway and enable/configure playstore-automation under:

• plugins.entries.playstore-automation.enabled
• plugins.entries.playstore-automation.config

Plugin config fields

Supported in openclaw.plugin.json:

• projectRoot: project root for command execution
• configPath: explicit playstore.config.json location
• defaultProfile: default EAS profile (e.g., production)
• defaultTrack: default Play track (internal|alpha|beta|production)
• serviceAccountKeyPath: key path used by metadata upload
• dryRunByDefault: prepend --dry-run when true

OpenClaw commands and tools

After install:

• CLI command: openclaw playstore <args...>
• Agent tool: playstore_automation (optional tool)

Examples:

openclaw playstore audit --strict
openclaw playstore metadata --upload --track production
openclaw playstore release --track production

Standalone CLI usage

playstore-automation init
playstore-automation audit --strict
playstore-automation release --track production

If no playstore.config.json exists in your project root, create one:

playstore-automation init

This writes a starter config. You can also copy playstore.config.template.json manually.

Notes on automation limits

The Google Play API cannot fully automate every policy form. This tool enforces strict checks and tracks manual review tasks, but some Play Console declarations still require manual completion.

Minimum requirements

• Node.js 20+
• EAS CLI auth configured for your Expo app
• Google Play service account credentials (for metadata upload/submission paths)
• fastlane installed if you use metadata upload (metadata --upload)