Tracking Live Gtm

Community

jtrackingai

tracking-live-gtm

Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.

Overview

Publisher	jtrackingai
Repository	`analytics-tracking-automation`
Skill name	`tracking-live-gtm`
Stars	140
Forks	39
Bundled files	1
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jtrackingai on GitHub. Read the source before you install it.

Installation

Install the Tracking Live Gtm AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-live-gtm

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git /tmp/analytics-tracking-automation
mkdir -p .claude/skills
cp -r /tmp/analytics-tracking-automation/skills/tracking-live-gtm .claude/skills/tracking-live-gtm

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Tracking Live Gtm in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Tracking Live Gtm on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Tracking Live Gtm is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Tracking Live GTM

Use this skill to audit the site's real live GTM setup before event generation.

Inputs

One of:

confirmed <artifact-dir>/site-analysis.json
explicit live GTM public IDs when the crawl did not capture them

Workflow

If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.

Run the live baseline step before schema preparation whenever the site has a real GTM container installed:

bash
./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json

If multiple live containers matter and the user already knows the primary comparison target:

bash
./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json --primary-container-id GTM-XXXXXXX

If the user wants to test the quality of the already-published live GTM setup on the real site, run:

bash
./event-tracking verify-live-gtm <artifact-dir>/site-analysis.json

During review:

show all detected live GTM containers
explain which container is the primary comparison baseline
summarize existing live events, measurement IDs, and obvious issues
when verify-live-gtm was run, separate parsed live definitions from browser-verified live firing evidence
if this review is part of tracking_health_audit, clearly separate runtime-detected live definitions from any formal preview-verified automation evidence
stop before schema authoring if the user wants to review the live baseline first

Required Output

Produce and share:

<artifact-dir>/live-gtm-analysis.json
<artifact-dir>/live-gtm-review.md
optional <artifact-dir>/live-preview-result.json
optional <artifact-dir>/live-preview-report.md
optional <artifact-dir>/live-tracking-health.json
updated <artifact-dir>/workflow-state.json

Closeout Style

default to a compact live-tracking summary before listing files
name the detected live events directly instead of only reporting event counts
in tracking_health_audit, explicitly separate runtime-detected live definitions from formal preview-verified automation evidence
list artifacts only after the decision-ready summary

Stop Boundary

Stop after the live GTM baseline is reviewed unless the user explicitly asks to continue into schema work.

Default next phase:

bash
./event-tracking prepare-schema <artifact-dir>/site-analysis.json

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Tracking Live Gtm AI skill do?

Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.

Why use Tracking Live Gtm on TypingMind?

Because you install it once and use it with any model. Tracking Live Gtm is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Tracking Live Gtm in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-live-gtm. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Tracking Live Gtm?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Tracking Live Gtm?

As many as you like. As long as a model supports skills, you can use Tracking Live Gtm with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Tracking Live Gtm AI skill free?

Yes. It is published on GitHub by jtrackingai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Writing Fragments

mattpocock

CommunityPopular

Writing, explore: mine raw fragments, no structure yet.

Writing For Agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Karpathy Guidelines

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define…

Create Agent

Create a custom agent (.agent.md) for a specific job.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Tracking Live GTM

Inputs

Workflow

Required Output

Closeout Style

Stop Boundary

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now