analytics-tracking
Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data. Use when the user wants to set up, fix, or evaluate analytics tracking (GA4, GTM, product analytics, events, conversions, UTMs). This skill focuses on measurement strategy, signal quality, and validation— not just firing events.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/analytics-tracking/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific actions, comprehensive trigger terms covering both platform names and user intents, explicit 'Use when' guidance, and clear scope boundaries that distinguish it from simpler analytics skills. The clarification about focusing on 'measurement strategy, signal quality, and validation—not just firing events' is particularly effective for disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Design, audit, and improve analytics tracking systems' with specific outcomes 'reliable, decision-ready data' and clarifies scope 'measurement strategy, signal quality, and validation'. | 3 / 3 |
Completeness | Clearly answers both what ('Design, audit, and improve analytics tracking systems') and when ('Use when the user wants to set up, fix, or evaluate analytics tracking') with explicit trigger guidance and scope clarification. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'GA4, GTM, product analytics, events, conversions, UTMs, analytics tracking, set up, fix, evaluate' - these are exactly what users mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on analytics tracking systems with specific platform mentions (GA4, GTM) and explicit scope boundary ('not just firing events'). The distinction between measurement strategy vs. simple event firing reduces conflict with basic analytics skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill body functions primarily as a table of contents with minimal actionable content in the main file. While it correctly attempts to defer details to sub-skills, it provides no concrete guidance, examples, or clear workflow in the overview itself. The 24 sub-skill links lack meaningful organization or descriptions, making it hard to know where to start or what each contains.
Suggestions
Add a concrete quick-start workflow with 3-5 numbered steps showing the actual process for auditing or setting up analytics tracking
Include at least one executable code example (e.g., a GTM dataLayer push or GA4 event call) directly in the main skill file
Group the 24 sub-skills into logical categories (e.g., 'Discovery', 'Implementation', 'Validation') with brief descriptions of what each contains
Add explicit validation checkpoints to the workflow (e.g., 'Before proceeding to implementation, verify Signal Quality Index ≥60')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively lean with minimal unnecessary explanation, but the numbered list of 24 sub-skills with generic titles adds bulk without providing immediate value. The intro section is efficient but the module list could be more descriptive. | 2 / 3 |
Actionability | The skill body contains no concrete code, commands, or executable examples. It describes a framework ('calculate the Signal Quality Index') but provides no actual implementation—everything is deferred to sub-skill files with no inline guidance. | 1 / 3 |
Workflow Clarity | Despite mentioning 'Phase 0' as required, there is no clear sequence of steps, no validation checkpoints, and no workflow structure. The 24 linked modules have no indicated order or dependencies beyond their numbering. | 1 / 3 |
Progressive Disclosure | The skill attempts progressive disclosure by linking to 24 sub-skills, but the references are poorly signaled—titles like '2. Total Score: **0–100**' are cryptic and don't clearly indicate content. The flat list of 24 items without grouping makes navigation difficult. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.