rjyo/moshi-skill

play-developer-console

Use when managing Google Play Developer Console metadata, graphics, tracks, app bundles, reviews, subscriptions, or in-app products with the local `play` CLI.

First seen Apr 29, 2026

Installation

$ npx skills add rjyo/moshi-skill --skill play-developer-console

Summary

  • Use when managing Google Play Developer Console metadata, graphics, tracks, app bundles, reviews, subscriptions, or in-app products with the local `play` CLI.
  • Trigger this for Moshi Android Play Store work, especially when editing `/Users/jyo/projects/ai/moshi/marketing/play` assets or debugging `/Users/jyo/projects/tools/play-cli`.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rjyo/moshi-skill.

npx skills add rjyo/moshi-skill

Browse all from rjyo/moshi-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 28
Default branch main
Open issues 15
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,825 B
  • docs SUMMARY.md 364 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 636 installs

SKILL.md

Play Developer Console

Use the local Bun TypeScript CLI at:

/Users/jyo/projects/tools/play-cli

The CLI is linked locally with Bun and exposes:

play --help

For Moshi Android, run commands from:

/Users/jyo/projects/ai/moshi/marketing

The Play assets live in:

play/
  .env
  metadata/
  images/
  release-notes/

Workflow

  • Inspect play/CLAUDE.md and 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, or play tracks commands.
  • 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 5

Release 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.txt

Prepare 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.txt

If 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 test

Retry 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.android