Tracking Discover
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
Mirror any GTM container into a local database, then audit, diff Trigger phrases: audit my GTM container, diff my GTM workspace against live, what GA4 ids are in my tag manager, check consent mode…
$ npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-tag-manager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-skills/pp-google-tag-manager .claude/skills/pp-google-tag-manager && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pp-google-tag-manager" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-tag-manager into .claude/skills/pp-google-tag-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-tag-manager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-tag-managerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-tag-manager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-skills/pp-google-tag-manager .agents/skills/pp-google-tag-manager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pp-google-tag-manager" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-tag-manager into .agents/skills/pp-google-tag-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-tag-manager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-tag-manager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-skills/pp-google-tag-manager .cursor/skills/pp-google-tag-manager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pp-google-tag-manager" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-tag-manager into .cursor/skills/pp-google-tag-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-tag-manager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mvanhorn/printing-press-library.git --path cli-skills/pp-google-tag-manager--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-tag-manager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-skills/pp-google-tag-manager .gemini/skills/pp-google-tag-manager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pp-google-tag-manager" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-tag-manager into .gemini/skills/pp-google-tag-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-tag-manager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mvanhorn/printing-press-library pp-google-tag-managerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-skills/pp-google-tag-manager .github/skills/pp-google-tag-manager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pp-google-tag-manager" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-tag-manager into .github/skills/pp-google-tag-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-tag-manager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mvanhorn/printing-press-library pp-google-tag-manager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mvanhorn/printing-press-library.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-skills/pp-google-tag-manager .opencode/skills/pp-google-tag-manager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pp-google-tag-manager" agent skill from https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-google-tag-manager into .opencode/skills/pp-google-tag-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pp-google-tag-manager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pp-google-tag-managerMirror any GTM container into a local database, then audit, diff Trigger phrases: audit my GTM container, diff my GTM workspace against live, what GA4 ids are in my tag manager, check consent mode…
Pp Google Tag Manager is an agent skill from mvanhorn/printing-press-library. Mirror any GTM container into a local database, then audit, diff Trigger phrases: audit my GTM container, diff my GTM workspace against live, what GA4 ids are in my tag manager, check consent mode coverage, what fires on this GTM trigger, use google-tag-manager, run google-tag-manager.
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Go-to-market strategy. It works with Google Analytics. The repository describes itself as: Official library of CLIs generated by the CLI Printing Press. Endorsed, tested, and community-contributed. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d9a1696. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
goclaudegcloudnpxFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
googleapis.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
GTM_ACCESS_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pp Google Tag Manager loads about 4.3k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 1,737 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, BashAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mvanhorn/printing-press-library at commit d9a1696, republished under its Apache-2.0 licence (© mvanhorn). 1,737 words, ~4,257 tokens.
.claude/skills/pp-google-tag-manager/SKILL.md (or your agent's skills folder).<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/marketing/google-tag-manager/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/". -->
This skill drives the google-tag-manager-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
$HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:npx -y @mvanhorn/printing-press-library install google-tag-manager --cli-onlygoogle-tag-manager-pp-cli --version$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/marketing/google-tag-manager/cmd/google-tag-manager-pp-cli@latestIf --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.
The Google Tag Manager console can't diff anything, can't bulk-query, can't cross-reference the tag/trigger/variable graph, and can't export to version control. This CLI pulls a container into local SQLite and turns all of that into one command: audit hygiene, diff workspace-vs-live or container-vs-container, inventory GA4 ids and Consent Mode coverage across your whole fleet, and full-text search every parameter. It is read-only by construction — the mutating endpoints are stripped, so it is safe to point at a production container.
Use this CLI to audit, diff, export, and query Google Tag Manager container configuration from the terminal, CI, or an agent. It is the right tool for hygiene checks before a release, comparing two containers or a workspace against live, inventorying GA4 ids and Consent Mode coverage across many containers, and full-text search over tag/trigger/variable config. It is read-only — it never creates, edits, deletes, or publishes.
Do not use this CLI for:
These capabilities aren't available in any other tool for this API.
pull — Walk an entire GTM container — every tag, trigger, variable, folder, template, client, zone, and gtag config — into a local SQLite store in one command.
Reach for this first — every other command reads the mirror, and re-pulls become time-stamped snapshots for history/drift.
google-tag-manager-pp-cli pull --account 6012345 --container 9876543 --liveexport — Emit a deterministic flattened representation of the container for clean version-control diffs, or container-export-compatible JSON.
Use to check GTM config into git and review changes in pull requests.
google-tag-manager-pp-cli export --flataudit — Run a battery of hygiene checks against the mirror: dead tags, orphan triggers, unused variables, paused tags, Custom HTML tags, and tags firing on All Pages.
Use to gate a release in CI or sanity-check a container before publishing; typed exit code fails the build on high-severity findings.
google-tag-manager-pp-cli audit --json --fail-on highconsent-report — Per-tag consentSettings coverage and a list of tags that fire without consent gating, classified by vendor (ads vs analytics).
Use to answer 'are we Consent Mode v2 compliant for the EEA' without clicking through every tag.
google-tag-manager-pp-cli consent-report --jsondiff — Field-level diff between two snapshots: workspace vs live, version vs version, or container vs container, with stable name+type keys so renames are not add+remove.
Use before publishing to see exactly what changed, or to compare two properties' containers.
google-tag-manager-pp-cli diff live workspace:7fleet — One table across all pulled containers: GA4/measurement-id inventory, Consent Mode coverage, Custom HTML count, and entity counts per container.
Use when you manage containers across multiple properties and need a portfolio view the console can never give.
google-tag-manager-pp-cli fleet --metric ga4 --jsonsearch — Substring search across every entity's name, type, parameters, and notes — find hardcoded GA4 ids, stray pixels, or leftover URLs across all pulled containers.
Use to track down where a measurement id, domain, or vendor pixel is referenced before changing or removing it.
google-tag-manager-pp-cli search "G-ABCDE12345"uses — Show everything that references a variable or trigger — the safe-to-delete / what-breaks-if-I-touch-this check.
Use before deleting or renaming a variable or trigger to see its blast radius.
google-tag-manager-pp-cli uses "DLV - userId"fires — Bidirectional graph walk: which tags fire on a trigger, or which triggers and variables a tag depends on.
Use for incident debugging — 'why did this fire' or 'what fires here'.
google-tag-manager-pp-cli fires --trigger 42 --jsontagmanager — Manage tagmanager
google-tag-manager-pp-cli tagmanager accounts-containers-destinations-list — Lists all Destinations linked to a GTM Container.google-tag-manager-pp-cli tagmanager accounts-containers-environments-list — Lists all GTM Environments of a GTM Container.google-tag-manager-pp-cli tagmanager accounts-containers-list — Lists all Containers that belongs to a GTM Account.google-tag-manager-pp-cli tagmanager accounts-containers-lookup — Looks up a Container by destination ID.google-tag-manager-pp-cli tagmanager accounts-containers-snippet — Gets the tagging snippet for a Container.google-tag-manager-pp-cli tagmanager accounts-containers-version-headers-latest — Gets the latest container version headergoogle-tag-manager-pp-cli tagmanager accounts-containers-version-headers-list — Lists all Container Versions of a GTM Container.google-tag-manager-pp-cli tagmanager accounts-containers-versions-live — Gets the live (i.e. published) container versiongoogle-tag-manager-pp-cli tagmanager accounts-containers-workspaces-built-in-variables-list — Lists all the enabled Built-In Variables of a GTM Container.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-clients-list — Lists all GTM Clients of a GTM container workspace.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-folders-list — Lists all GTM Folders of a Container.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-get-status — Finds conflicting and modified entities in the workspace.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-gtag-config-list — Lists all Google tag configs in a Container.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-list — Lists all Workspaces that belong to a GTM Container.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-tags-list — Lists all GTM Tags of a Container.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-templates-list — Lists all GTM Templates of a GTM container workspace.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-triggers-list — Lists all GTM Triggers of a Container.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-variables-list — Lists all GTM Variables of a Container.google-tag-manager-pp-cli tagmanager accounts-containers-workspaces-zones-list — Lists all GTM Zones of a GTM container workspace.google-tag-manager-pp-cli tagmanager accounts-list — Lists all GTM Accounts that a user has access to.google-tag-manager-pp-cli tagmanager accounts-user-permissions-get — Gets a user's Account & Container access.google-tag-manager-pp-cli tagmanager accounts-user-permissions-list — List all users that have access to the account along with Account and Container user access granted to each of them.When you know what you want to do but not which command does it, ask the CLI directly:
google-tag-manager-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.
google-tag-manager-pp-cli diff live workspace:7 --jsonSee exactly what a workspace changes relative to the published live container before publishing.
google-tag-manager-pp-cli consent-report --json --select tags.name,tags.consentStatusList every tag with its consent gating status, narrowed to just name and status for a compact agent-friendly payload.
google-tag-manager-pp-cli fleet --metric ga4 --csvExport which GA4 measurement ids appear in which containers across your whole estate as CSV.
google-tag-manager-pp-cli uses "DLV - userId" --jsonList every tag and trigger that references a variable so you know what breaks before touching it.
google-tag-manager-pp-cli search "facebook" --json --select results.container,results.name,results.typeFull-text search every entity across all pulled containers for leftover vendor pixels, narrowing the nested response to the fields that matter.
Google Tag Manager has no API key — it uses OAuth 2.0. Provide a read-scoped access token as GTM_ACCESS_TOKEN. The quickest path with gcloud: run gcloud auth application-default login --scopes=https://www.googleapis.com/auth/tagmanager.readonly, then export GTM_ACCESS_TOKEN=$(gcloud auth application-default print-access-token). Alternatively use a service account whose email is granted Viewer access in GTM admin and mint a token for it. The CLI sends the token as Authorization: Bearer <token> and only ever needs the read-only scope.
Run google-tag-manager-pp-cli doctor to verify setup.
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:
google-tag-manager-pp-cli tagmanager accounts-containers-destinations-list mock-value --agent --select id,name,statusPreviewable — --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
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.
When you (or the agent) notice something off about this CLI, record it:
google-tag-manager-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
google-tag-manager-pp-cli feedback --stdin < notes.txt
google-tag-manager-pp-cli feedback list --json --limit 10Entries are stored locally at ~/.local/share/google-tag-manager-pp-cli/feedback.jsonl. They are never POSTed unless GOOGLE_TAG_MANAGER_FEEDBACK_ENDPOINT is set AND either --send is passed or GOOGLE_TAG_MANAGER_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.
Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|---|---|
stdout | Default; write to stdout only |
file:<path> | Atomically write output to <path> (tmp + rename) |
webhook:<url> | POST the output body to the URL (application/json or application/x-ndjson when --compact) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
google-tag-manager-pp-cli profile save briefing --json
google-tag-manager-pp-cli --profile briefing tagmanager accounts-containers-destinations-list mock-value
google-tag-manager-pp-cli profile list --json
google-tag-manager-pp-cli profile show briefing
google-tag-manager-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Parse $ARGUMENTS:
help, or --help → show google-tag-manager-pp-cli --help outputinstall → ends with mcp → MCP installation; otherwise → see Prerequisites above--agent)go install github.com/mvanhorn/printing-press-library/library/marketing/google-tag-manager/cmd/google-tag-manager-pp-mcp@latestclaude mcp add google-tag-manager-pp-mcp -- google-tag-manager-pp-mcpclaude mcp listwhich google-tag-manager-pp-cli
If not found, offer to install (see Prerequisites at the top of this skill).--agent flag:google-tag-manager-pp-cli <command> [subcommand] [args] --agentgoogle-tag-manager-pp-cli <command> --help.© mvanhorn, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cli-skills/pp-google-tag-manager of mvanhorn/printing-press-library.
Open the folder on GitHubat commit d9a1696
Pp Google Tag Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pp Google Tag Manager this skillmvanhorn/printing-press-library | 2.1k | — | ~4.3k | Automated safety check: Notes | Apache-2.0 | |
| Tracking Discoverjtrackingai/analytics-tracking-automation | 142 | — | ~614 | Automated safety check: Pass | Apache-2.0 | |
| Gtm Auditcognyai/claude-code-marketing-skills | 104 | — | ~1.6k | Automated safety check: Pass | None | |
| Tracking Live Gtmjtrackingai/analytics-tracking-automation | 142 | — | ~721 | Automated safety check: Pass | Apache-2.0 | |
| Gtm Setupcognyai/claude-code-marketing-skills | 104 | — | ~4.8k | Automated safety check: Notes | None | |
| Tracking Schemajtrackingai/analytics-tracking-automation | 142 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
cognyai/claude-code-marketing-skills
Google Tag Manager container audit — tag health, orphaned and paused tags, duplicate GA4 config, trigger coverage, Consent Mode, naming, workspace hygiene
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
cognyai/claude-code-marketing-skills
GTM Event Tracking & Setup Reference — dataLayer fundamentals, trigger types, variable types, GA4 tag configuration, debug mode, and best practices
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
cognyai/claude-code-marketing-skills
Turn a measurement plan into a Google Tag Manager spec — tags, triggers, variables, and copy-paste dataLayer snippets for every event
mvanhorn/printing-press-library
Desktop automation through the real Rust agent-desktop CLI, published in Printing Press through a small bridge.
mvanhorn/printing-press-library
Search, browse, and download Google Fonts from the terminal via the gfonts CLI.
mvanhorn/printing-press-library
The free, offline Trigger phrases: search 1688 for, find a factory on 1688 for, wholesale price on 1688 for, who is the cheapest supplier on 1688 for, compare 1688 suppliers for, use 1688, run 1688.
mvanhorn/printing-press-library
Inspect known Activity Japan plan IDs or URLs, compare dated prices and sessions, check language-sitemap coverage, and hand off to canonical booking pages.
mvanhorn/printing-press-library
Every Admin By Request portal action, plus a local SQLite mirror of audit, events, inventory and requests for ad-hoc...
mvanhorn/printing-press-library
macOS screen capture, window recording, GIF conversion, and agent evidence bundles from the terminal.
Works with
Categories
Mirror any GTM container into a local database, then audit, diff Trigger phrases: audit my GTM container, diff my GTM workspace against live, what GA4 ids are in my tag manager, check consent mode…. Pp Google Tag Manager is an agent skill from mvanhorn/printing-press-library. Mirror any GTM container into a local database, then audit, diff Trigger phrases: audit my GTM container, diff my GTM workspace against live, what GA4 ids are in my tag manager, check consent mode coverage, what fires on this GTM trigger, use google-tag-manager, run google-tag-manager.
Pp Google Tag Manager fits situations like: phrases: audit my GTM container; diff my GTM workspace against live; what GA4 ids are in my tag manager; check consent mode coverage.
Run `npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a claude-code`. Or copy the skill folder (cli-skills/pp-google-tag-manager in mvanhorn/printing-press-library) into .claude/skills/pp-google-tag-manager in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a codex`. Or copy the skill folder (cli-skills/pp-google-tag-manager in mvanhorn/printing-press-library) into .agents/skills/pp-google-tag-manager in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvanhorn/printing-press-library --skill pp-google-tag-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pp-google-tag-manager, .gemini/skills/pp-google-tag-manager, .github/skills/pp-google-tag-manager and .opencode/skills/pp-google-tag-manager in your project.
Going by SKILL.md and its folder, Pp Google Tag Manager needs the command-line tools its instructions call (go, claude, gcloud and npx) and credentials named GTM_ACCESS_TOKEN. Our summary lists: Node.js; A credential in GTM_ACCESS_TOKEN. Its frontmatter pre-approves these tools: Read, Bash.
SKILL.md names 1 domain. In commands or code: googleapis.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Pp Google Tag Manager is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pp Google Tag Manager: Tracking Discover (jtrackingai/analytics-tracking-automation, 142 stars), Gtm Audit (cognyai/claude-code-marketing-skills, 104 stars), Tracking Live Gtm (jtrackingai/analytics-tracking-automation, 142 stars) and Gtm Setup (cognyai/claude-code-marketing-skills, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mvanhorn (a GitHub user) maintains it in mvanhorn/printing-press-library, which has 2,056 GitHub stars. The repository holds 506 skills in this directory. The repository was last updated on October 9, 2026.
Source: mvanhorn/printing-press-library on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.