New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tracking Schema

by jtrackingai in jtrackingai/analytics-tracking-automation

A skill your agent uses when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

Apache-2.0Auto-check passedMarketing & SEO

Install Tracking Schema

skills CLI
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-schema -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jtrackingai/analytics-tracking-automation tracking-schema --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tracking-schema .claude/skills/tracking-schema && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tracking-schema
GitHub stars
142
Token cost
~1.1k tokens
SKILL.md length
433 words
Files
2
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

  • The user wants schema preparation
  • SKILL.md covers Inputs, Workflow, Role And Quality Bar and Required Output, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Selector validation

What it does

Tracking Schema is an agent skill from jtrackingai/analytics-tracking-automation. Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Marketing & SEO, covering Product analytics and Go-to-market strategy. It works with Google Analytics. The repository describes itself as: AI-powered GA4 + GTM event tracking — automates site analysis, event schema, GTM sync, preview verification, and publishing. Works with Cursor, Codex, and any AI agent. The licence is Apache-2.0.

When your agent uses it

  • The user wants schema preparation
  • Selector validation
  • Event-spec generation

Example prompts

  • “/tracking-schema”

What it can do on your machine

Read from SKILL.md and the folder at commit 68378e0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tracking Schema loads about 1.1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jtrackingai/analytics-tracking-automation at commit 68378e0, republished under its Apache-2.0 licence (© jtrackingai). 433 words, ~1,055 tokens.

Download SKILL.mdSave it as .claude/skills/tracking-schema/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
tracking-schema
description
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

Tracking Schema

Use this skill for Step 3 work only.

Inputs

One of:

  • confirmed <artifact-dir>/site-analysis.json
  • existing <artifact-dir>/event-schema.json

Workflow

Role And Quality Bar

During schema work, act as an expert in event tracking design.

Your job is not to list generic events. Your job is to produce a tracking plan that is:

  • aligned with common GA4 / GTM industry standards
  • comprehensive enough to cover the site's meaningful business journeys
  • accurate enough to be implemented and verified without guesswork
  • disciplined enough to avoid noisy, redundant, or low-signal events
  • easy for the user to review, approve, QA, and maintain

Favor event definitions that are business-meaningful, implementation-ready, and analytically useful. Do not preserve weak legacy patterns just for continuity. Do not inflate the schema with events that add little reporting or decision value.

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

If schema context is not prepared yet:

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

If the site has a live GTM container installed, make sure tracking-live-gtm has already produced <artifact-dir>/live-gtm-analysis.json before running prepare-schema.

Then:

validate-schema --check-selectors launches a real Chromium via Playwright to test each schema selector against the live site. Run it in an environment that permits outbound network and local browser execution; environments that restrict either tend to cause Playwright to hang or fail silently rather than return a clean error.

bash
./event-tracking validate-schema <artifact-dir>/event-schema.json --check-selectors
./event-tracking generate-spec <artifact-dir>/event-schema.json
./event-tracking confirm-schema <artifact-dir>/event-schema.json

During review:

  • explain what live tracking problems the schema fixes when live-gtm-analysis.json is present
  • explain what benefits the new schema brings compared with the current live baseline
  • default to a compact tracking-plan summary in this order: Event Table, Common Properties, Event-specific Properties
  • keep long parameter inventories out of the main event table
  • stop for user approval before GTM generation
  • a broad request such as "full workflow" or "全流程" does not count as schema approval
  • do not run ./event-tracking confirm-schema <artifact-dir>/event-schema.json --yes on the user's behalf unless the user explicitly confirms the schema and parameters in the current turn
Show full SKILL.md (113 more words)Show less

Required Output

Produce and share:

  • <artifact-dir>/event-schema.json
  • optional <artifact-dir>/event-spec.md
  • optional <artifact-dir>/tracking-plan-comparison.md when live-gtm-analysis.json is present
  • <artifact-dir>/schema-decisions.jsonl after schema confirmation
  • <artifact-dir>/schema-restore/ restore snapshots after schema confirmation
  • updated <artifact-dir>/workflow-state.json

Closeout Style

  • default to a decision-ready tracking-plan summary before listing files
  • keep the chat structure in this order: Event Table, Common Properties, Event-specific Properties
  • if a live baseline comparison exists, keep it as a compact appendix rather than replacing the tracking-plan structure
  • list files and next steps only after the summary

Stop Boundary

Stop after schema approval.

Do not continue into generate-gtm from a broad workflow request alone. The user must explicitly approve the current event-schema.json and its parameters first.

Default next phase:

bash
./event-tracking generate-gtm <artifact-dir>/event-schema.json --measurement-id <G-XXXXXXXXXX>

References

© jtrackingai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/tracking-schema of jtrackingai/analytics-tracking-automation.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 68378e0

Compare with similar skills

Tracking Schema next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tracking Schema compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tracking Schema this skilljtrackingai/analytics-tracking-automation142—~1.1kAutomated safety check: PassApache-2.0
Gtm Tracking Plancognyai/claude-code-marketing-skills104—~1.4kAutomated safety check: NotesNone
Analytics Trackingborghei/Claude-Skills874—~5.7kAutomated safety check: PassMIT
Gtm Setupcognyai/claude-code-marketing-skills104—~4.8kAutomated safety check: NotesNone
AnalyticsNexus-JPF/note-companion8696 repos~2.2kAutomated safety check: PassMIT
Gtm Auditcognyai/claude-code-marketing-skills104—~1.6kAutomated safety check: PassNone

Similar skills

  • Gtm Tracking Plan

    cognyai/claude-code-marketing-skills

    Turn a measurement plan into a Google Tag Manager spec — tags, triggers, variables, and copy-paste dataLayer snippets for every event

    104 GitHub stars~1.4k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check: notes

  • Analytics Tracking

    borghei/Claude-Skills

    End-to-end analytics implementation for web and SaaS: GA4, Google Tag Manager, event taxonomy, conversion tracking, and UTM strategy.

    874 GitHub stars~5.7k tokensUpdated today
    Marketing & SEOAuto-check passed

  • Gtm Setup

    cognyai/claude-code-marketing-skills

    GTM Event Tracking & Setup Reference — dataLayer fundamentals, trigger types, variable types, GA4 tag configuration, debug mode, and best practices

    104 GitHub stars~4.8k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check: notes

  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    869 GitHub starsUsed in 6 repos~2.2k tokens
    Marketing & SEOAuto-check passed

  • Gtm Audit

    cognyai/claude-code-marketing-skills

    Google Tag Manager container audit — tag health, orphaned and paused tags, duplicate GA4 config, trigger coverage, Consent Mode, naming, workspace hygiene

    104 GitHub stars~1.6k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed

  • Google Tag Manager

    thatrebeccarae/claude-marketing

    Google Tag Manager expertise. An agent skill from thatrebeccarae/claude-marketing.

    162 GitHub stars~2.6k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed

More from jtrackingai/analytics-tracking-automation

All 8 skills in this repo

  • Tracking Discover

    jtrackingai/analytics-tracking-automation

    A skill your agent uses when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.

    142 GitHub starsUsed in 1 repo~614 tokens
    Auto-check passed

  • Analytics Tracking Automation

    jtrackingai/analytics-tracking-automation

    A skill your agent uses when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.

    142 GitHub stars~2.8k tokensUpdated 5 mo ago
    Auto-check passed

  • Tracking Group

    jtrackingai/analytics-tracking-automation

    A skill your agent uses when the work starts from site-analysis.json and the user wants page-group authoring, grouping adjustments, or page-group approval.

    142 GitHub stars~492 tokensUpdated 5 mo ago
    Auto-check passed

  • Tracking Live Gtm

    jtrackingai/analytics-tracking-automation

    A skill your agent uses when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.

    142 GitHub stars~721 tokensUpdated 5 mo ago
    Auto-check passed

  • Tracking Sync

    jtrackingai/analytics-tracking-automation

    A skill your agent uses when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.

    142 GitHub stars~677 tokensUpdated 5 mo ago
    Auto-check passed

  • Tracking Verify

    jtrackingai/analytics-tracking-automation

    A skill your agent uses when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.

    142 GitHub stars~695 tokensUpdated 5 mo ago
    Auto-check passed

Works with

Categories

Questions about Tracking Schema

What does Tracking Schema do?

A skill your agent uses when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation. Tracking Schema is an agent skill from jtrackingai/analytics-tracking-automation. Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

When should I use Tracking Schema?

Tracking Schema fits situations like: the user wants schema preparation; selector validation; event-spec generation.

How do I install Tracking Schema in Claude Code?

Run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-schema -a claude-code`. Or copy the skill folder (skills/tracking-schema in jtrackingai/analytics-tracking-automation) into .claude/skills/tracking-schema in your project. Claude Code loads it when a task matches its description.

How do I install Tracking Schema in Codex?

Run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-schema -a codex`. Or copy the skill folder (skills/tracking-schema in jtrackingai/analytics-tracking-automation) into .agents/skills/tracking-schema in your project. Codex loads it when a task matches its description.

Can I use Tracking Schema in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-schema -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tracking-schema, .gemini/skills/tracking-schema, .github/skills/tracking-schema and .opencode/skills/tracking-schema in your project.

What does Tracking Schema need to run?

SKILL.md names no scripts, command-line tools or credentials: Tracking Schema is instructions for the agent only.

Does Tracking Schema access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tracking Schema safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tracking Schema use?

Tracking Schema is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tracking Schema use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tracking Schema?

Skills that share tags, products or a category with Tracking Schema: Gtm Tracking Plan (cognyai/claude-code-marketing-skills, 104 stars), Analytics Tracking (borghei/Claude-Skills, 874 stars), Gtm Setup (cognyai/claude-code-marketing-skills, 104 stars) and Analytics (Nexus-JPF/note-companion, 869 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tracking Schema?

jtrackingai (a GitHub user) maintains it in jtrackingai/analytics-tracking-automation, which has 142 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on April 29, 2026.

Source: jtrackingai/analytics-tracking-automation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.