Skip to content
TrustedSkillsbeta
Back to all skills

Gplay Submission Checks

Checked
tamtom·vlatest·devops·MIT

Gplay Submission Checks verifies your app’s Google Play Store listing meets requirements, saving you time and potential rejections.

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-submission-checks -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-submission-checks/SKILL.md
Scanned
1 file, 411 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 allows an AI agent to perform checks on Google Play application submissions using the gplay command-line interface. It validates submission metadata, including package name and version code, ensuring they match expected values before a release. The skill can also verify that required files are present in the submission bundle.

When to use it

  • Pre-release validation: Before publishing an app update, automatically check if all submission details are correct.
  • Automated build pipelines: Integrate checks into your CI/CD pipeline to prevent incorrect submissions from reaching Google Play.
  • Release candidate review: Quickly verify the integrity of a release candidate before wider distribution.
  • Troubleshooting submission errors: Diagnose issues related to mismatched metadata or missing files during submission attempts.

Key capabilities

  • Validates package name and version code against expected values.
  • Checks for the presence of required files in the submission bundle.
  • Uses the gplay command-line interface for execution.

Example prompts

  • "Check if my Google Play submission is valid."
  • "Verify that the package name 'com.example.app' and version code 123 are correct for my submission."
  • "Confirm all required files exist in my submission bundle before I release it."

Tips & gotchas

  • Requires the gplay CLI tool to be installed and configured with appropriate credentials.
  • The skill relies on accurate configuration of expected package names, version codes, and file lists for effective validation.