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.
Install with Tessl CLI
npx tessl i github:Dokhacgiakhoa/antigravity-ide --skill analytics-trackingOverall
score
62%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 multiple analytics platforms and user intents, explicit 'Use when' guidance, and clear scope boundaries that distinguish it from related skills. The description effectively communicates both capabilities and appropriate use cases.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design, audit, and improve analytics tracking systems' with clear outcome focus on 'reliable, decision-ready data' and mentions specific concerns like '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 ('not just firing events'). | 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 would mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on analytics tracking systems with distinct triggers (GA4, GTM, UTMs, conversions). The clarification 'not just firing events' further distinguishes it from generic event tracking 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 functions primarily as a table of contents with minimal actionable content in the main body. While it establishes a clear philosophy ('track for decisions, not curiosity'), it provides no concrete guidance, examples, or workflows—everything is deferred to 24 sub-skills without clear organization or sequencing. The skill would benefit significantly from inline quick-start content and better-organized references.
Suggestions
Add a concrete quick-start section with at least one executable example (e.g., a sample GA4 event implementation or GTM tag configuration)
Include the Signal Quality Index calculation method inline rather than deferring entirely to sub-skills—show the formula and scoring criteria
Reorganize the 24 sub-skills into logical groups (e.g., 'Discovery', 'Implementation', 'Validation') with brief descriptions of when to use each
Add a clear workflow sequence showing the order of operations: assess readiness → define measurement strategy → implement tracking → validate
| 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-skills with no inline guidance. | 1 / 3 |
Workflow Clarity | Despite mentioning 'Phase 0' as required, there's no clear sequence of steps, no validation checkpoints, and no workflow visible in the main skill. The 24 sub-skill links are unnumbered in a meaningful sequence and lack any indication of order or dependencies. | 1 / 3 |
Progressive Disclosure | The skill attempts progressive disclosure by linking to 24 sub-skills, but the organization is poor—links are numbered arbitrarily, titles are inconsistent (some are categories, some are numbered steps), and there's no clear grouping or navigation structure to help Claude understand which sub-skill to consult for what purpose. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
91%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 | |
- 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.