CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-traffic-tracking

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

68

Quality

82%

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

75%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, actionable skill body with concrete GA4 setup paths, a ready-to-use regex, and a verification checklist. The main improvement room is trimming minor duplication and adding an explicit validation step for the regex result.

Suggestions

Add a brief verification step after the regex filter (e.g., confirm Sessions appear for known AI sources, adjust regex if a source is missing) to close the workflow-clarity gap.

Remove the "Common AI Source Domains" table or fold it into the regex comment, since it duplicates the regex block and adds tokens without new capability.

Tighten the "Why Track Separately" section to one line or drop it; the rationale is the kind of context Claude can infer.

DimensionReasoningScore

Conciseness

The body is largely lean and actionable with no padding about what GA4 is, but the "Why Track Separately" rationale and the "Common AI Source Domains" table (which restates the regex) are minor trim candidates, fitting efficient-with-minor-over-explanation rather than the fully lean anchor at 5.

4 / 5

Actionability

Numbered GA4 setup steps with a copy-paste regex and named dimensions/metrics are mostly executable, but GSC analysis is delegated out ("see google-search-console") and AI Overviews guidance is partial ("can use GTM (partial coverage)"), leaving minor gaps versus the fully-executable anchor.

4 / 5

Workflow Clarity

The three setup options are clearly sequenced and capped by a Checklist checkpoint with a useful ordering gotcha (place "AI Chatbots" above "Referral"), but there is no explicit verify step confirming the regex matched AI traffic, leaving a minor validation gap below the 5 anchor.

4 / 5

Progressive Disclosure

No bundle files exist; the body is well-organized into clearly headed sections and cleanly signals related skills (google-search-console, generative-engine-optimization), but at ~85 lines with some table/regex duplication it sits just below the crisp overview anchor at 5.

4 / 5

Total

16

/

20

Passed

Description

90%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, trigger-rich description that clearly states both what the skill does and when to invoke it, with explicit disambiguation from a neighboring skill. The only soft spot is specificity, which lists a single broad action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ("track AI search traffic in GA4 or GSC") but does not list multiple distinct actions, fitting the 1-2 concrete actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

It explicitly answers both what ("track AI search traffic in GA4 or GSC") and when ("When the user wants to... Also use when the user mentions...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It packs in comprehensive natural synonyms users would actually say — "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "Claude traffic," "how to track AI traffic" — matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (AI traffic tracking in GA4/GSC) and even disambiguates from a sibling skill ("For AI SEO strategy, use generative-engine-optimization"), minimizing conflict risk.

5 / 5

Total

18

/

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
kostja94/marketing-skills
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.