Gplay Vitals Monitoring
CheckedContinuously monitors game server health metrics like CPU, memory, and network latency to proactively identify performance issues.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add tamtom/gplay-cli-skills --skill gplay-vitals-monitoring -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto 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.
Automated safety checks
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
- Scanned
- 1 file, 137 lines
About this skill
What it does
The gplay-vitals-monitoring skill allows you to monitor Google Play Vitals data directly from the command line. It retrieves and displays key metrics like ANR rate, crash rate, and app start time, providing insights into your application's performance and stability on Android devices. This helps developers proactively identify and address issues impacting user experience.
When to use it
- Performance Regression Detection: Quickly check vitals after a new release to ensure no regressions have been introduced.
- Root Cause Analysis: Investigate sudden drops in app ratings or negative user reviews by examining vital signs data.
- Scheduled Reporting: Automate the retrieval of vital metrics for regular reporting and tracking trends over time.
- Incident Response: During a production incident, use this skill to rapidly assess the impact on key vitals.
Key capabilities
- Retrieves Google Play Vitals data.
- Displays ANR rate.
- Displays crash rate.
- Displays app start time.
Example prompts
- "Show me the current crash rate for my app."
- "What's the average app start time over the last 7 days?"
- "Get the latest ANR rate data."
Tips & gotchas
- Requires authentication with Google Play Console. Ensure you have configured your
gplayCLI credentials correctly before using this skill.