analytics-tracking
Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.
64
Quality
47%
Does it follow best practices?
Impact
95%
1.18xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-analytics-tracking/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (analytics tracking) with reasonable action verbs, but lacks the explicit trigger guidance essential for skill selection. It uses appropriate third-person voice but relies on abstract language ('decision-ready data') rather than concrete, user-facing terminology that would help Claude distinguish this skill from general data or analytics skills.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions analytics setup, event tracking, Google Analytics, tag management, or tracking implementation'.
Include more specific user-facing keywords such as 'GA4', 'UTM parameters', 'conversion tracking', 'event schemas', 'tracking plans', or 'measurement strategy'.
Replace abstract outcomes like 'decision-ready data' with concrete deliverables such as 'create tracking specifications', 'debug missing events', or 'document measurement plans'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (analytics tracking systems) and lists three actions (design, audit, improve), but these actions are somewhat abstract and don't specify concrete deliverables like 'create tracking plans', 'validate event schemas', or 'implement UTM strategies'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no trigger guidance at all. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'analytics', 'tracking', and 'data', but misses common user variations such as 'Google Analytics', 'event tracking', 'metrics', 'dashboards', 'KPIs', 'conversion tracking', or 'tag management'. | 2 / 3 |
Distinctiveness Conflict Risk | The phrase 'analytics tracking systems' provides some specificity, but 'reliable, decision-ready data' is vague and could overlap with data analysis, business intelligence, or reporting skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive measurement strategy framework with strong workflow structure and clear decision gates. However, it leans toward conceptual guidance rather than executable implementation, and the document length could be reduced by extracting detailed reference material into separate files. The scoring index is a valuable diagnostic tool but the skill would benefit from concrete code examples for implementation.
Suggestions
Add executable code examples for key implementations (e.g., GTM dataLayer push syntax, GA4 event configuration snippets)
Extract detailed sections (GA4/GTM guidance, UTM rules, validation checklists) into separate reference files and link to them
Condense the scoring category definitions into a more compact format - the current explanations repeat concepts Claude already understands
Add a concrete worked example showing the full workflow from business question → event design → implementation → validation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeated emphasis on 'non-negotiable' principles, verbose category definitions that could be condensed). The scoring rubric tables are useful but the surrounding explanations could be tighter. | 2 / 3 |
Actionability | Provides structured frameworks and checklists but lacks concrete executable examples. The event naming conventions show patterns but no actual implementation code (GTM dataLayer pushes, GA4 config). The guidance is more conceptual than copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear phased workflow (Phase 0 → Phase 1) with explicit gates ('If verdict is Broken, stop and recommend remediation first'). Validation section lists required checks. The sequence is logical with clear decision points and feedback loops. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document (~300 lines) that could benefit from splitting detailed sections (GA4/GTM specifics, UTM rules, validation checklists) into separate reference files. Related skills are mentioned but no actual file references for deeper content. | 2 / 3 |
Total | 9 / 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
- boisenoise/skills-collections
- Commit
5c5ae21
- 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.