Pp Googlehealth

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/devices/googlehealth/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Googlehealth — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the googlehealth-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install googlehealth --cli-only

2. Verify: googlehealth-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/devices/googlehealth/cmd/googlehealth-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

View and manage health and fitness metrics and measurement data from Fitbit, Pixel Watch, and other third-party devices and apps.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

• trends — Per-metric trailing rolling-average trend lines with net first-to-last delta, de-noising day-to-day scale-weight and resting-HR whiplash
• streaks — Current and longest consecutive-calendar-day streaks where a metric met a goal (e.g. 10k steps, resting HR under 60), with calendar gaps breaking the run
• correlate — Pearson correlation plus best-lag scan between any two daily metrics (steps vs resting HR, sleep vs HRV) over locally synced history
• sync — Mirror Google Health data points across data types into a local SQLite store for offline analysis
• search — FTS5 full-text search across locally synced Google Health records

Recipes

Step-goal streak

googlehealth-pp-cli streaks --metric steps --threshold 10000 --op ">=" --json

Resting-HR trend

googlehealth-pp-cli trends --metric daily-resting-heart-rate --window 14 --json

Live data points for a metric

googlehealth-pp-cli users data-types list me steps --json

Command Reference

projects — Manage projects

users — Manage users

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

googlehealth-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Auth Setup

Run googlehealth-pp-cli auth setup for the URL and steps to obtain a token (add --launch to open the URL). Then store it:

googlehealth-pp-cli auth set-token YOUR_TOKEN_HERE

Or set GOOGLEHEALTH_OAUTH2C as an environment variable.

Run googlehealth-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  googlehealth-pp-cli --help

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Explicit retries — use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.