CtrlK
BlogDocsLog inGet started
Tessl Logo

analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.

75

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient skill body that stays lean while delivering concrete event specs, naming conventions, executable snippets, a validation checklist, and a clean progressive-disclosure split into three real reference files. Workflow feedback loops are slightly implicit but validation is explicit and the overall sequence is clear.

DimensionReasoningScore

Conciseness

Lean, reference-style body using compact tables and minimal code snippets, with no padding explaining what GA4/UTMs/tag managers are; every section earns its tokens and assumes Claude's competence, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Provides concrete, specific guidance — exact event names, property tables, an object-action naming format, an executable gtag() snippet, a dataLayer.push snippet, a validation checklist, and a copy-paste output template — which is actionable for an instruction/planning skill per the rubric's code_vs_instruction note.

3 / 3

Workflow Clarity

Clear assess→plan→implement→validate sequence (Initial Assessment, GA4 Quick Setup numbered 1–5, Debugging & Validation with an explicit checklist and a common-issues table providing error-recovery guidance), matching the 'clear sequence with checklists' anchor; feedback loops are present via the issue table though softer than a strict validate→fix→retry loop.

3 / 3

Progressive Disclosure

Body is a concise overview with well-signaled, one-level-deep references to verified bundle files (event-library.md, ga4-implementation.md, gtm-implementation.md) introduced with bold lead-ins, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what/when structure, excellent natural trigger-term coverage, and clear distinctiveness reinforced by a cross-reference to a sibling skill. The only weak spot is specificity, where the stated actions are generic verbs rather than a varied list of concrete operations.

DimensionReasoningScore

Specificity

Names the domain and three verbs ('set up, improve, or audit analytics tracking and measurement') but these are generic actions rather than a list of distinct concrete operations, matching the 'names domain and some actions' anchor rather than 'lists multiple specific concrete actions'.

2 / 3

Completeness

Explicitly answers both what ('set up, improve, or audit analytics tracking and measurement') and when ('Also use when the user mentions...') with an explicit trigger list, matching the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

Broad natural-term coverage including product names users actually say ('GA4,' 'Google Analytics,' 'GTM,' 'tag manager,' 'UTM parameters,' 'conversion tracking,' 'event tracking,' 'set up tracking,' 'tracking plan'), matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Clear niche with specific product trigger terms and an active cross-reference ('For A/B test measurement, see ab-test-setup') that reduces overlap, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 6 suspicious

Warning

Total

14

/

16

Passed

Repository
freekmurze/dotfiles
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.