play-developer-console — Claude Code skill: Google Play from the CLI
A skill for managing Google Play Developer Console through the local play CLI: metadata, graphics, tracks, bundles, reviews and subscriptions.
npx skills add rjyo/moshi-skill --skill play-developer-console -a claude-codeWhat play-developer-console does
The skill covers managing the Google Play console with a local play CLI — a Bun TypeScript tool. It lays out the workflow for the Moshi Android project: read play/CLAUDE.md and local files before touching store assets, validate listing text with play metadata validate, run read-only checks before and after edits.
Release work uses built-in track commands. A production draft is created with play tracks release production, passing a version code, status and notes. When stale releases block validation, the track is cleared first and the intended release created after. Without a --notes flag the command reads every file in play/release-notes/ as localized notes.
One hard constraint: edit-backed commands must not run in parallel — one at a time. Auth is keyless, through gcloud ADC and a quota project in play/.env, so no service account JSON is needed. If the CLI lacks some Play API behavior, the skill says to patch the CLI itself, then run bun run typecheck and bun test.
What it helps with
- validate listing text before uploading to Play
- prepare a production draft release with notes
- clear a track of stale releases
- list reviews and tracks as JSON
- fix missing Play API behavior in the local CLI
Example prompts for the agent
- show app metadata with play metadata list
- create a production draft release with version-code 6
- validate the listing text before upload
How to install play-developer-console
1Skills CLI (Vercel)
npx skills add rjyo/moshi-skill --skill play-developer-console -a claude-code2Manually: put the files in place
~/.claude/skills/play-developer-console/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/play-developer-console/
1Skills CLI (Vercel)
npx skills add rjyo/moshi-skill --skill play-developer-console -a codex2Manually: put the files in place
.agents/skills/play-developer-console/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rjyo/moshi-skill --skill play-developer-console -a cursor2Manually: put the files in place
.cursor/skills/play-developer-console/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rjyo/moshi-skill play-developer-console2Manually: put the files in place
.github/skills/play-developer-console/SKILL.md1Skills CLI (Vercel)
npx skills add rjyo/moshi-skill --skill play-developer-console -a gemini-cli2Platform CLI
gemini skills install https://github.com/rjyo/moshi-skill --path skills/play-developer-consoleManually: put the files in place
.devin/skills/play-developer-console/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add rjyo/moshi-skill --skill play-developer-console -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about play-developer-console
How do I install play-developer-console in Claude?
Run npx skills add rjyo/moshi-skill --skill play-developer-console -a claude-code. The skill lands in ~/.claude/skills/play-developer-console/SKILL.md.
What does play-developer-console do?
It describes managing Google Play Developer Console through the local play CLI: metadata, graphics, tracks, bundles, reviews, subscriptions and in-app products.
Does the skill need a service account JSON key?
No. Auth runs through gcloud ADC and a quota project in play/.env, so no keys are required.
