DiscordSign up
SKILLS.SH

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.…

INSTALLATION
npx skills add https://github.com/rjyo/moshi-skill --skill play-developer-console
Run in your project or agent environment. Adjust flags if your CLI version differs.

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
BrowserAct

Let your agent run on any real-world website

Bypass CAPTCHA & anti-bot for free. Start local, scale to cloud.

Explore BrowserAct Skills →

Related skills

find-skills
2/3

Discover and install specialized agent skills from the open ecosystem when users need extended capabilities. Helps identify relevant skills by domain and task when users ask "how do I do X" or "find a skill for X" Integrates with the Skills CLI ( npx skills find , npx skills add ) to search, verify, and install packages from the skills.sh directory Recommends skills based on install count, source reputation, and GitHub stars to ensure quality before suggesting installation Presents skill options with install commands and links to skills.sh for user review and one-click installation

Verified authorvercel-labs
SKILLS.SH
1.5M19.6K
2026-05-22
vercel-react-best-practices
3/3

React and Next.js performance optimization guide with 64 prioritized rules across 8 categories. Organized by impact level, from critical waterfalls and bundle optimization down to advanced patterns, each rule includes incorrect/correct code examples and explanations Covers eight domains: async patterns, bundle size, server-side caching, client-side data fetching, re-render optimization, rendering performance, JavaScript efficiency, and advanced patterns Designed for use during component writing, code review, refactoring, and performance audits on React and Next.js applications Each rule has a prefix code (e.g., async-parallel , bundle-barrel-imports ) for easy reference in automated tooling and documentation

Verified authorvercel-labs
SKILLS.SH
389K26.9K
2026-05-22
azure-validate
2/3

Pre-deployment validation for Azure infrastructure, configuration, and permissions before deployment. Requires .azure/plan.md from a prior azure-prepare run; stops immediately if the plan is missing Executes recipe-specific validation commands (azd provision, bicep build, terraform validate) and records proof in the plan document Performs build verification, configuration checks, and permission validation; blocks deployment if any check fails Only authorized method to set plan status to Validated ; must be followed by azure-deploy skill to execute the actual deployment

Verified authormicrosoft
SKILLS.SH
324K1.1K
2026-05-22
appinsights-instrumentation
3/3

Guidance and reference material for instrumenting webapps with Azure Application Insights. Covers SDK setup, telemetry patterns, and configuration for ASP.NET Core and Node.js applications hosted in Azure Distinguishes between this skill (reference and guidance) and azure-prepare (actual implementation); invoke azure-prepare when the user wants to add instrumentation to their project Provides auto-instrumentation guidance for C# ASP.NET Core apps in Azure App Service, plus manual instrumentation paths for creating App Insights resources via Bicep templates or Azure CLI Includes language-specific code modification guides for ASP.NET Core, Node.js, and Python, plus quick references for OpenTelemetry SDKs and exporters

Verified authormicrosoft
SKILLS.SH
324K1.1K
2026-05-22

Stop writing automation&scrapers

Install the CLI. Run your first Skill in 30 seconds. Scale when you're ready.

Start free
free · no credit card