Skip to content

PollyGlot/google-play-cli-skills / skills/gplay-vitals

gplay-vitals

Verified

Android vitals with gplay `vitals`: crash/ANR and other rates, error reports, Play-detected anomalies (read-only). Use when checking crash or ANR health after a rollout, investigating a spike, gating CI on vitals, or reading clustered crash issues and stack traces.

FileKindSize
SKILL.mdskill md4.5 KB
---
name: gplay-vitals
description: "Android vitals with gplay `vitals`: crash/ANR and other rates, error reports, Play-detected anomalies (read-only). Use when checking crash or ANR health after a rollout, investigating a spike, gating CI on vitals, or reading clustered crash issues and stack traces."
---

# gplay vitals (post-launch quality signals)

`gplay vitals` reads Android vitals: the rate presets below, error reports, and
Play-detected anomalies. Shared conventions are in `gplay-cli-usage`.

Two things set this namespace apart:

- **A distinct Google service.** Vitals is backed by the Play Developer
  Reporting API, with its own OAuth scope. A service account invited only for
  publishing gets a 403 (exit `11`) on every vitals call until the reporting
  scope is granted: an environment fix, not a flag.
- **Read-only throughout:** no `--confirm`, and `GPLAY_READONLY` never blocks
  it.

## Preset rate commands: the fast path

One preset per vital, 28-day DAILY window by default:

```bash
gplay vitals crashes           # crash rate (on the pinned package)
gplay vitals anr               # ANR rate
gplay vitals slowstart         # slow cold-start rate
gplay vitals slowrendering     # janky-frames rate
gplay vitals excessivewakeup   # excessive wakeup rate
gplay vitals lmk               # low-memory-kill rate
gplay vitals stuckbgwakelock   # stuck background wakelock rate
```

All presets share the same knobs:

```bash
gplay vitals crashes --by versionCode --version-code 123   # slice, then filter to one build
gplay vitals anr --since 7d --period HOURLY                # window: 28d default; HOURLY opt-in
gplay vitals crashes --user-cohort OS_BETA                 # OS_PUBLIC, APP_TESTERS or OS_BETA
```

`--period HOURLY` exists only on `crashes` and `anr` (`crashrate`, `anrrate`);
every other set is DAILY. `--user-cohort` picks the user view; the sets that
accept each value are listed in `gplay vitals query --help`, any other
combination exits `2` offline.

`--version-code` takes the codes `gplay vitals releases` lists (the tracks and
serving releases the Reporting service knows), `[experimental]`.

## `vitals query`: full control

When you need more than a preset's primary metric, `vitals query <metric-set>`
wraps the metric set directly:

```bash
gplay vitals query crashrate --metrics crashRate,distinctUsers --dimensions versionCode
gplay vitals query anrrate --period HOURLY --since 24h
gplay vitals query bitmapmemoryusage --since 28d --dimensions versionCode
```

`--metrics`/`--dimensions`/`--period` are validated offline against the
embedded schema (an unknown name lists the valid set). Two memory sets have no
preset and are `query`-only, DAILY only: `anonrssandswapmemoryusage` and
`bitmapmemoryusage`.

## `vitals errors`: reports, issues, counts

```bash
gplay vitals errors counts      # error report counts over a window
gplay vitals errors issues      # clustered issues, crashes/ANRs grouped by cause
gplay vitals errors reports     # individual error reports (the stack traces)
gplay vitals errors issues --since 6h --sample-reports 1 --output json   # hourly window, one sample report per issue
```

On `errors issues` and `errors reports`, `--since` in days (`7d`) covers whole
UTC days; in hours (`6h`, `24h`) it counts whole hours back from the newest
data (gplay 2.5.0+; older builds silently searched whole days).
`--sample-reports 1` attaches one sample report name per issue, which saves a
second lookup.

Obfuscated (R8/ProGuard) stacks stay unreadable until the versionCode's mapping
is uploaded under `releases` (`--mapping` on `releases upload`, or `releases
mappings upload`): see `gplay-release-flow`.

## `vitals anomalies`: what Play flagged itself

```bash
gplay vitals anomalies --since 90d
gplay vitals anomalies --filter 'activeBetween("2026-01-01T00:00:00Z", UNBOUNDED)'
```

`--filter` (raw AIP-160) overrides `--since` for an open-ended range;
`--limit 0` returns all.

## Freshness: an empty window means unknown

Metrics land with a lag: every rate/query command prints a freshness note to
stderr (the latest date carrying data). Since gplay 2.4.2 the window ends at
that freshness, not today, and `--since` counts back from it, so a DAILY query
made before Google publishes the day no longer fails with HTTP 400. A short
window right after a release can still be empty: an empty window means
unknown, not zero. `--describe` on a preset or `query` returns the set's
latest available end time instead of a timeline: ask it to know which day the
window ends on.

## CI gate

One `jq` line over `--output json` (the API timeline verbatim).
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall