agentleFS
stape-iostape-io/google-tag-manager-mcp-server/skills/google-tag-manager/SKILL.md

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

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. carlosuhart/seo-audit-skills★ 6same name
    2. 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
  1. Very specific:

    Read the guide first: Call gtm_guide with the topic that matches the task (safeEditing, naming, audit, trackingPlan, consentMode, …

    line 18
  2. Very specific:

    Updates replace the whole entity: Always get first, apply the change to the full object, and send it back with its fingerprint.

    line 19
  3. Very specific:

    Work in a workspace, never live: Check with gtm_workspace getStatus and quickPreview before creating a version.

    line 20
  4. Very specific:

    Related changes go together: Use gtm_workspace bulkUpdate (temporary IDs new_1, new_2, ...) so a tag and its new trigger land atomically.

    line 21
  5. Very specific:

    Large lists paginate: Follow pagination.nextPage.

    line 25

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read the guide first. Call gtm_guide with the topic that matches the task (safeEditing, naming, audit, trackingPlan, consentMode, serverSide) before planning changes.
  2. Updates replace the whole entity. Always get first, apply the change to the full object, and send it back with its fingerprint. Anything omitted is deleted.
  3. Work in a workspace, never live. Check with gtm_workspace getStatus and quickPreview before creating a version.
  4. Related changes go together. Use gtm_workspace bulkUpdate (temporary IDs new_1, new_2, ...) so a tag and its new trigger land atomically.
  5. Prefer gallery templates over Custom HTML. gtm_template importFromGallery needs acknowledgePermissions: true — show the user the permissions the template requests and get consent first.
  6. Publishing and deleting need explicit user confirmation. gtm_version publish changes live traffic; remove actions are destructive.
  7. Auth errors: on a 401/403 call gtm_auth_status. It shows whether the token works, when it expires and which scopes are missing.
  8. Large lists paginate. Follow pagination.nextPage; for versions use resourceType to page through one resource type at a time.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.