Skip to content
TrustedSkillsbeta
Back to all skills

Gplay Release Flow

Checked
tamtom·vlatest·devops·MIT

Automates Google Play app releases by streamlining build uploads, testing, and publishing, saving developers time & ensuring smooth deployments.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tamtom/gplay-cli-skills --skill gplay-release-flow -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tamtom

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tamtom/gplay-cli-skills at 10301b2463.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
10301b2463
Manifest
skills/gplay-release-flow/SKILL.md
Scanned
1 file, 259 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates Google Play release flow using the gplay CLI. It handles tasks like creating new releases, uploading APKs and AABs, setting release tracks (internal, alpha, beta, production), and managing release notes. The skill streamlines the process of publishing updates to your Android applications on the Google Play Store.

When to use it

  • You need to create a new internal test release for quick feedback from your team.
  • You want to upload an APK or AAB bundle to the alpha track for broader testing.
  • You're ready to promote a beta release to a wider audience of testers.
  • You are preparing a production release and need to automate the final steps before publishing.

Key capabilities

  • Create new releases
  • Upload APK/AAB files
  • Manage release tracks (internal, alpha, beta, production)
  • Set release notes

Example prompts

  • "Create a new internal test release for version 1.2.3."
  • "Upload the latest AAB file to the beta track."
  • "Promote the alpha release to the production track."

Tips & gotchas

  • Ensure you have the gplay CLI installed and configured with your Google Play Developer credentials before using this skill.
  • The skill relies on the gplay CLI; familiarize yourself with its command structure for more complex operations.