Pp Amplitude

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/marketing/amplitude/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/". -->

Amplitude — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the amplitude-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 amplitude --cli-only

2. Verify: amplitude-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.6 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/marketing/amplitude/cmd/amplitude-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.

Read-first Amplitude Analytics API surface for exports, cohorts, events, users, and chart-style analytics queries.

When Not to Use This CLI

Do not activate this CLI for requests that require creating, updating, deleting, publishing, commenting, upvoting, inviting, ordering, sending messages, booking, purchasing, or changing remote state. This printed CLI exposes read-only commands for inspection, export, sync, and analysis.

Command Reference

annotations — Manage annotations

• amplitude-pp-cli annotations — List project annotations.

cohorts — Manage cohorts

• amplitude-pp-cli cohorts get — Get cohort metadata or membership export status.
• amplitude-pp-cli cohorts list — List behavioral cohorts.

event_exports — Manage event exports

• amplitude-pp-cli event-exports — Export raw event data over a time range.

events — Manage events

• amplitude-pp-cli events — List event types tracked in an Amplitude project.

funnels — Manage funnels

• amplitude-pp-cli funnels — Query funnel conversion metrics.

retention — Manage retention

• amplitude-pp-cli retention — Query retention metrics.

revenue — Manage revenue

• amplitude-pp-cli revenue — Query revenue analytics.

segmentation — Manage segmentation

• amplitude-pp-cli segmentation — Query event segmentation metrics.

users — Manage users

• amplitude-pp-cli users <user_id> — Get a user profile by user ID.

usersearch — Manage usersearch

• amplitude-pp-cli usersearch — Search users by user ID, device ID, or user property filters.

Finding the right command

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

amplitude-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 amplitude-pp-cli auth setup to print the URL and steps for getting a key (add --launch to open the URL). Then set:

export AMPLITUDE_USERNAME="<your-key>"

Or persist it in ~/.config/amplitude-read-pp-cli/config.toml.

Run amplitude-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:

  amplitude-pp-cli annotations --agent --select id,name,status

• 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

• Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests

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.