Agent skill · marketing growth · mvanhorn
pp-google-trends
Every Google Trends workflow pytrends offered, plus the local history and rate-limit resilience that archived, frozen wrapper never had. Trigger phrases: `check google trends for`, `interest over time for`, `what's trending right now`, `compare search interest`, `related queries for`, `search interest by region`, `use google-trends`, `run google-trends-pp-cli`.
Why this skill is useful
Adds a CLI tool for programmatic Google Trends research with unique capabilities like historical trending data and local caching that the AI wouldn't reliably generate on its own.
What it needs
Requires google-trends-pp-cli installed locally. About 10k tokens when loaded. Last updated 2026-08-06. 1,890 stars on the source repository.
What this skill does
Google Trends — Printing Press CLI Prerequisites: Install the CLI This skill drives the google-trends-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: 2. Verify: google-trends-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: 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. pytrends — the de-facto standard Python wrapper — was archived in April 2025, and Google Trends throttles anonymous access aggressively and unpredictably. This CLI absorbs the full explore-to-widget contract with built-in retry/backoff, caches every query locally so history compounds instead of evaporating, and answers questions the live site simply cannot: what was trending three weeks ago, what changed since your last check, and which related terms are actually worth a content brief. When to Use This CLI Use this CLI for programmatic Google Trends research: interest-over-time pulls, multi-keyword and cross-geo comparisons, related/rising query discovery for content planning, and tracking trending topics over time via the local cache. It is the right tool whenever you need history Google Trends' own UI discards, or when you're automating what used to be a manual pytrends script. Anti-triggers Do not use this CLI for: Do not use this CLI for absolute search volume — Google Trends only exposes relative 0-100 interest, never real query counts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mvanhorn/google-trends