A skill your agent uses when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tracking-verify .claude/skills/tracking-verify && rm -rf skills-srcUse ~/.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/
Install the "tracking-verify" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verify into .claude/skills/tracking-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tracking-verify .agents/skills/tracking-verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tracking-verify" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verify into .agents/skills/tracking-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tracking-verify .cursor/skills/tracking-verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tracking-verify" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verify into .cursor/skills/tracking-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jtrackingai/analytics-tracking-automation.git --path skills/tracking-verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tracking-verify .gemini/skills/tracking-verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tracking-verify" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verify into .gemini/skills/tracking-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tracking-verify .github/skills/tracking-verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tracking-verify" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verify into .github/skills/tracking-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tracking-verify .opencode/skills/tracking-verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tracking-verify" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verify into .opencode/skills/tracking-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
tracking-verifyA skill your agent uses when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Tracking Verify is an agent skill from jtrackingai/analytics-tracking-automation. Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Its SKILL.md is about 700 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 Product & Project Management, covering Feature launches and release readiness and Go-to-market strategy. It works with Google Analytics and Shopify. 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.
Read from SKILL.md and the folder at commit 68378e0. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Tracking Verify loads about 695 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 236 words of instructions outside code blocks.
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.
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.
The full file from jtrackingai/analytics-tracking-automation at commit 68378e0, republished under its Apache-2.0 licence (© jtrackingai). 236 words, ~695 tokens.
.claude/skills/tracking-verify/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Use this skill for verification and optional publish handoff.
<artifact-dir>/event-schema.json<artifact-dir>/gtm-context.jsonIf the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.
Run preview:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.jsonIf comparing against an older preview run, pass the previous health baseline:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json --baseline <previous-tracking-health.json>preview launches a real Chromium via Playwright and exercises the live site to fire GA4/GTM events for verification. 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.
Then interpret:
If the user explicitly wants to publish after verification:
./event-tracking publish --context-file <artifact-dir>/gtm-context.json --version-name "GA4 Events v1 - <date>"If tracking-health.json is missing, still manual-only, or has blockers, publish now stops by default. Only use --force when the user explicitly wants to override that gate.
Produce and share:
<artifact-dir>/preview-report.md<artifact-dir>/preview-result.json<artifact-dir>/tracking-health.json<artifact-dir>/tracking-health-report.md<artifact-dir>/tracking-health-history/<artifact-dir>/workflow-state.jsonIf the platform is Shopify, switch to the Shopify-specific rules in tracking-shopify.
© 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
SKILL.md and 1 other file in skills/tracking-verify of jtrackingai/analytics-tracking-automation.
Open the folder on GitHubat commit 68378e0
Tracking Verify 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tracking Verify this skilljtrackingai/analytics-tracking-automation | 142 | — | ~695 | Automated safety check: Pass | Apache-2.0 | |
| 60 Launch Playbook Globalminhnv0807/ai-business-skills | 608 | — | ~3k | Automated safety check: Pass | MIT | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Organic Growth Path Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~5.2k | Automated safety check: Pass | Custom licence |
minhnv0807/ai-business-skills
A skill your agent uses when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room…
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
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.
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.
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.
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.
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.
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.
Works with
Categories
A skill your agent uses when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff. Tracking Verify is an agent skill from jtrackingai/analytics-tracking-automation. Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Tracking Verify fits situations like: the user wants preview QA; failure interpretation; release readiness; an explicit publish handoff.
Run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a claude-code`. Or copy the skill folder (skills/tracking-verify in jtrackingai/analytics-tracking-automation) into .claude/skills/tracking-verify in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a codex`. Or copy the skill folder (skills/tracking-verify in jtrackingai/analytics-tracking-automation) into .agents/skills/tracking-verify in your project. Codex loads it when a task matches its description.
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-verify -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-verify, .gemini/skills/tracking-verify, .github/skills/tracking-verify and .opencode/skills/tracking-verify in your project.
SKILL.md names no scripts, command-line tools or credentials: Tracking Verify is instructions for the agent only.
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.
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.
Tracking Verify 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.
About 695 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Tracking Verify: 60 Launch Playbook Global (minhnv0807/ai-business-skills, 608 stars), .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars) and Final Release Review (openai/openai-agents-python, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.
