CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analytics

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," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For getting conversions into ad platforms (pixels, conversion tags, CAPI, server-side) and verifying they arrived, see conversion-tracking. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing. Rate metrics divide matching closed windows — never full-period spend by partial-period results.

73

Quality

92%

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

86%Weight 40%Scale 1-5

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

A well-structured, highly actionable reference body with real bundle files backing every reference link and strong concrete guidance (code snippets, tables, checklists, output template). Its only weaknesses are a slightly padded Core Principles section and a workflow that is implied by section order rather than explicitly sequenced.

DimensionReasoningScore

Conciseness

The body is dominated by dense tables and terse bullets with concrete examples, but Core Principles 1–4 state generic wisdom Claude already knows ("Naming conventions matter", "Avoid vanity metrics", "Document everything") and could be trimmed. This is minor over-explanation rather than the broader tightening needed for a 3.

4 / 5

Actionability

Copy-paste-ready gtag('event', …) and dataLayer.push snippets, exact UTM parameter tables with examples, concrete per-partner-type UTM templates, a validation checklist, an issue→check debugging table, and a complete output-format template cover the common cases (GA4, GTM, UTM, validation) with executable specificity.

5 / 5

Workflow Clarity

The assess → plan → implement → validate flow is discernible (Initial Assessment questions, GA4 Quick Setup steps 1–5, Debugging/Validation section with tools and a checklist, error recovery via the Common Issues table), but it is organized as topical sections rather than one explicitly sequenced workflow with validation checkpoints, so it falls short of the top anchor.

4 / 5

Progressive Disclosure

The body is an overview that delegates detail through clearly signaled, one-level-deep references — references/event-library.md (260 lines), references/ga4-implementation.md (304 lines), and references/gtm-implementation.md (396 lines) all exist and are substantive, each linked with an explicit "See [references/…]" callout. Content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

95%Weight 40%Scale 1-5

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 framing, rich natural trigger terms including synonyms and colloquial phrasings, and explicit disambiguation against sibling skills. The only minor gap is that the capability list is less enumerated than the trigger list.

DimensionReasoningScore

Specificity

"set up, improve, or audit analytics tracking and measurement" names several concrete actions in the domain, but coverage is not comprehensive — deliverables like building a tracking plan or defining naming conventions are only implied via trigger terms rather than stated as capabilities. This fits 'several specific actions; minor gaps' better than the 1-2-action anchor at 3 or full enumerations at 5.

4 / 5

Completeness

Explicitly answers both what ("set up, improve, or audit analytics tracking and measurement") and when ("Also use when the user mentions…", "Use this whenever someone asks how to know if something is working"), with concrete trigger phrases throughout, matching the top anchor's example pattern. Third-person voice is maintained.

5 / 5

Trigger Term Quality

Comprehensive natural terms with synonyms: "GA4"/"Google Analytics", "GTM"/"tag manager", "UTM parameters", "Mixpanel", "Segment", plus real user phrasings like "are my events firing", "analytics isn't working", and "how do I measure this".

5 / 5

Distinctiveness Conflict Risk

Clear niche (tracking implementation/measurement) with explicit boundary routing to adjacent skills — "see conversion-tracking", "see attribution", "For A/B test measurement, see ab-testing" — minimizing the chance of triggering for the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/analytics/SKILL.md

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.