gtm-monitor — Claude Code skill: weekly GTM container check
Diffs a Google Tag Manager container against last week: tags added, edited or removed, plus draft changes still sitting unpublished.
npx skills add cognyai/claude-code-marketing-skills --skill gtm-monitor -a claude-codeWhat gtm-monitor does
Once a week the skill takes a snapshot of a GTM container and compares it with the previous one. You get the tags, triggers and variables that appeared, changed or disappeared, along with orphaned tags that fire nothing and tags paused after being live the week before. Draft edits that never went out are called out too, since the live site then lags behind the container.
The diff relies on the fingerprint field GTM itself updates on every edit, so there is no need to hash configs by hand. Connect GA4, Plausible or Microsoft Clarity and the skill also checks whether an event stopped arriving after a tag change and whether script errors rose on the affected pages.
Everything runs through Cogny's MCP gateway: a Cogny Agent subscription at $9/mo is required, and the container is readable only through the GTM API. Without Google Tag Manager connected in Cogny the skill stops. Scheduling it weekly via /loop or /schedule fits the intended rhythm.
What it helps with
- see which GTM tags changed over the past week
- find tags that have no firing trigger
- check for edits left unpublished
- tell whether an event stopped arriving after a tag edit
- spot a tag paused after it had been live
Example prompts for the agent
- Run gtm-monitor and show what changed in the container this week
- Check the GTM container for orphaned tags and unpublished changes
- Diff the current container state against last week's snapshot and flag critical changes
How to install gtm-monitor
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-monitor -a claude-code2Manually: put the files in place
~/.claude/skills/gtm-monitor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gtm-monitor/
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-monitor -a codex2Manually: put the files in place
.agents/skills/gtm-monitor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-monitor -a cursor2Manually: put the files in place
.cursor/skills/gtm-monitor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cognyai/claude-code-marketing-skills gtm-monitor2Manually: put the files in place
.github/skills/gtm-monitor/SKILL.md1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-monitor -a gemini-cli2Platform CLI
gemini skills install https://github.com/cognyai/claude-code-marketing-skills --path skills/gtm-monitorManually: put the files in place
.devin/skills/gtm-monitor/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-monitor -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gtm-monitor
How do I install gtm-monitor in Claude Code?
Run npx skills add cognyai/claude-code-marketing-skills --skill gtm-monitor -a claude-code. The skill lands in ~/.claude/skills/gtm-monitor/SKILL.md.
What does gtm-monitor do?
It snapshots a GTM container and compares it with the prior week: tags, triggers and variables added, edited or removed. It also checks for orphaned tags and unpublished draft changes.
What do I need for gtm-monitor to work?
A Cogny Agent subscription and Google Tag Manager connected in Cogny. GA4, Plausible and Microsoft Clarity are optional and let the skill verify downstream impact after a tag change.
