Play Developer Console
- 609 installs
- 29 repo stars
- Updated August 1, 2026
- rjyo/moshi-skill
play-developer-console is a Claude Code skill that manages Google Play Store metadata, graphics, release tracks, app bundles, and in-app products through a local Bun TypeScript play CLI for Android release workflows.
About
play-developer-console is an rjyo/moshi-skill agent skill for operating Google Play Developer Console assets and releases via a local Bun-linked TypeScript CLI exposed as play --help. The skill directs agents to run play commands from the project's marketing directory when editing store listings, uploading graphics, promoting release tracks, publishing app bundles, or configuring subscriptions and in-app products. Developers reach for play-developer-console during Android ship cycles when console changes must be scripted safely rather than clicked through the web UI. The workflow assumes a locally linked play-cli repository and a marketing/play asset folder structure for Moshi Android, making it best suited to teams that already maintain Play assets as files. Use it when debugging CLI failures, syncing listing copy, or automating track promotions ahead of a Play Store launch.
- Local Bun TypeScript CLI for Google Play Developer Console operations
- Supports metadata, images, tracks, reviews, subscriptions and in-app products
- Enforces sequential execution of one edit-backed command at a time
- Built-in validation with `play metadata validate` before any upload
- Read-only inspection commands for safe pre- and post-change checks
Play Developer Console by the numbers
- 609 all-time installs (skills.sh)
- +10 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #37 of 248 Release Management skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/rjyo/moshi-skill --skill play-developer-consoleAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 609 |
|---|---|
| repo stars | ★ 29 |
| Last updated | August 1, 2026 |
| Repository | rjyo/moshi-skill ↗ |
How do you manage Play Store listings from CLI?
Safely manage Google Play Store metadata, graphics, tracks, bundles, and in-app products for an Android app using a local CLI.
Who is it for?
Android developers maintaining file-based Play Store assets who want CLI-driven listing, track, and bundle management during release cycles.
Skip if: Teams without a linked local play CLI or those publishing only to Apple App Store should skip play-developer-console.
When should I use this skill?
Trigger when editing Play Store metadata, graphics, tracks, app bundles, subscriptions, or in-app products with the local play CLI.
What you get
Updated Play Store metadata, graphics assets, release tracks, bundles, and in-app product configurations
- Play Store listing files
- Release track promotions
- Bundle upload configurations
Files
Play Developer Console
Use the local Bun TypeScript CLI at:
/Users/jyo/projects/tools/play-cliThe CLI is linked locally with Bun and exposes:
play --helpFor Moshi Android, run commands from:
/Users/jyo/projects/ai/moshi/marketingThe Play assets live in:
play/
.env
metadata/
images/
release-notes/Workflow
- Inspect
play/CLAUDE.mdand relevant local files before changing store assets. - Run one Play edit-backed command at a time. Do not parallelize
play metadata,play app-info,play images,play bundle, orplay trackscommands. - Validate local listing text before upload:
play metadata validate- Use read-only checks before and after changes:
play metadata list
play app-info show
play tracks list --json
play tracks show production --json
play reviews list --limit 5Release Workflow
Use the built-in track commands for release operations. Do not write ad hoc scripts against src/api.ts for normal release tasks.
Attach or update a release already uploaded to Play:
play tracks release internal \
--version-code 6 \
--status completed \
--name "Moshi 2.8.2" \
--notes en-US=play/release-notes/en-US.txtPrepare a production draft with release notes:
play tracks release production \
--version-code 6 \
--status draft \
--name "Moshi 2.8.2" \
--notes en-US=play/release-notes/en-US.txtIf a draft app has stale releases that block validation, clear the track first, then create the intended release:
play tracks clear internal
play tracks release internal --version-code 6 --status draft --name "Moshi 2.8.2"When no --notes flag is provided, play tracks release reads all files in play/release-notes/ as localized release notes. Use --no-notes only when intentionally omitting notes.
- For bugs or missing Play API behavior, patch
/Users/jyo/projects/tools/play-cli, then run:
cd /Users/jyo/projects/tools/play-cli
bun run typecheck
bun testRetry from /Users/jyo/projects/ai/moshi/marketing after the fix.
Auth
Moshi uses keyless local auth via gcloud ADC and a quota project in play/.env. Do not create or require service account JSON keys unless the user explicitly asks.
Expected env keys:
PLAY_AUTH_MODE=gcloud
PLAY_QUOTA_PROJECT=play-cli-moshi-260429103059
PLAY_PACKAGE_NAME=app.getmoshi.androidRelated skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.11.2k38.5k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.7k37.5k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.9k71.8k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.6k23.3k
Opensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4.3k238k
Community PublishInstantly share running services with public URLs, list projects on a discoverable dashboard, or open-source code to a community GitHub repository.3.9k21FAQ
What CLI does play-developer-console use?
play-developer-console uses a local Bun TypeScript CLI linked as play, invoked via play --help. Commands run from the project's marketing directory where Play Store asset files are maintained.
Which Play Console tasks does the skill cover?
play-developer-console covers metadata, graphics, release tracks, app bundles, reviews, subscriptions, and in-app products. The skill targets scripted console operations rather than general Android app coding.