Download for MacApple silicon, macOS 14+
Skill

adspirer-tag-manager

@adspirer Updated 2026-10-20

Inspect Google Tag Manager tags, triggers, and variables through Adspirer when diagnosing conversion tracking, and apply a tag fix only after an explicit yes. Publishing the container is a second yes. A tag that exists is not proof it fires.

Install

With your agent

Install OMGSkills skill "adspirer/adspirer-claude-plugin:skills/adspirer-tag-manager" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/Adspirer/adspirer-claude-plugin /tmp/adspirer-claude-plugin && ln -s /tmp/adspirer-claude-plugin/skills/adspirer-tag-manager ~/.claude/skills/adspirer-tag-manager

From README

Google Tag Manager The router is googletagmanager. It appears only when Tag Manager is connected. Follow adspirer-mcp: {"action": "listtools"} first, then execute an exact name from that list. gettoolschema before any write. If it isn't connected, say so and point the user at https://adspirer.ai/connections. The ads-manager check in adspirer-ads-manager-browser can still describe tag health from the ad platform's UI. Resolve one level at a time Account, then container, then workspace. The first call lists account options. Labels can be identical, so always show the id next to the label. If a level has several options, the user picks. Never assume an id. A write to the wrong container changes the wrong website, quietly. Confirm which conversion is in scope, then read the tags, triggers, and variables that serve it. Say whether what you have is configuration only.