google-tag-manager
Skill245 starsChanged 19 days agoApache-2.0View on GitHub
Use when working with Google Tag Manager through the Stape GTM MCP server (tools named gtm_*) - auditing a container, adding or changing tags, triggers, variables or templates, planning tracking, setting up Consent Mode or server-side tagging, or publishing a container version.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- carlosuhart/seo-audit-skillstheir own version, first seen Nov 1, 2026
- gmmh1/claude-paid-media-skillstheir own version, first seen Jul 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- carlosuhart/seo-audit-skills★ 6same name
- gmmh1/claude-paid-media-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read the guide first: Call gtm_guide with the topic that matches the task (safeEditing, naming, audit, trackingPlan, consentMode, …
- Very specific: line 19
Updates replace the whole entity: Always get first, apply the change to the full object, and send it back with its fingerprint.
- Very specific: line 20
Work in a workspace, never live: Check with gtm_workspace getStatus and quickPreview before creating a version.
- Very specific: line 21
Related changes go together: Use gtm_workspace bulkUpdate (temporary IDs new_1, new_2, ...) so a tag and its new trigger land atomically.
- Very specific: line 25
Large lists paginate: Follow pagination.nextPage.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Google Tag Manager via the Stape GTM MCP server
Setup: hosted at https://gtm-mcp.stape.io/mcp (Google OAuth in the browser), or locally with npx -y google-tag-manager-mcp-server and your own credentials. See the README.
How the tools are shaped
One tool per GTM resource, with an action parameter: gtm_account, gtm_container, gtm_workspace, gtm_tag, gtm_trigger, gtm_variable, gtm_built_in_variable, gtm_folder, gtm_template, gtm_client, gtm_transformation, gtm_zone, gtm_environment, gtm_version, gtm_version_header, gtm_gtag_config, gtag_destination, gtm_user_permission. Plus gtm_guide (best-practice guidance) and gtm_auth_status (credential diagnostics).
Navigate top-down: gtm_account list → gtm_container list → gtm_workspace list → entities in that workspace.
Rules
- Read the guide first. Call
gtm_guidewith the topic that matches the task (safeEditing,naming,audit,trackingPlan,consentMode,serverSide) before planning changes. - Updates replace the whole entity. Always
getfirst, apply the change to the full object, and send it back with itsfingerprint. Anything omitted is deleted. - Work in a workspace, never live. Check with
gtm_workspacegetStatusandquickPreviewbefore creating a version. - Related changes go together. Use
gtm_workspacebulkUpdate(temporary IDsnew_1,new_2, ...) so a tag and its new trigger land atomically. - Prefer gallery templates over Custom HTML.
gtm_templateimportFromGalleryneedsacknowledgePermissions: true— show the user the permissions the template requests and get consent first. - Publishing and deleting need explicit user confirmation.
gtm_versionpublishchanges live traffic;removeactions are destructive. - Auth errors: on a 401/403 call
gtm_auth_status. It shows whether the token works, when it expires and which scopes are missing. - Large lists paginate. Follow
pagination.nextPage; for versions useresourceTypeto page through one resource type at a time.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

