traffic-analysis

When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body is an efficient, well-structured reference skill with concrete UTM examples and clear GA4 navigation guidance. It loses a little on workflow clarity for implicit checkpoints and on progressive disclosure only because there is no bundle to offload detail into.

Suggestions

Add an explicit validation/checklist step to the Natural Traffic Benchmark and Segmenting Direct Traffic sequences (e.g., 'Confirm the GA4 segment excludes internal IPs before recording the baseline') to strengthen workflow clarity.

Consider moving the large UTM alignment table and channel attribution detail into a references file (e.g., references/utm-alignment.md) and linking from SKILL.md to improve progressive disclosure.

Trim minor padding such as the restated intro scope sentence and the brand-awareness truism to push conciseness toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is table-driven and lean, assuming Claude's competence, with only minor over-explanation such as the restated intro scope line and the truism 'Brand traffic grows over time as brand awareness increases.'	4 / 5
Actionability	It provides concrete, actionable guidance — real UTM parameter examples, a GA4 navigation path, a mitigation table with an explicit query string, and links to GA4 rules — with only minor advisory gaps and cited figures lacking methodology.	4 / 5
Workflow Clarity	Clear numbered sequences exist (Natural Traffic Benchmark steps, Segmenting Direct Traffic) and the skill involves no destructive or batch operations, so the destructive-ops cap does not apply; checkpoints are implicit rather than explicit, leaving a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist, so content is self-contained in SKILL.md with well-organized section headers and a 'Related Skills' pointer list plus two external reference URLs, with no nested references and minor organization gaps.	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.

The description is strong, with explicit what/when guidance, comprehensive natural trigger terms, and a clear niche reinforced by a handoff to a sibling skill. The only mild weakness is specificity, which names the domain and a couple of actions rather than enumerating many concrete capabilities.

Suggestions

Expand the 'what' clause to enumerate a few more concrete actions (e.g., 'identify dark traffic, segment direct traffic, and recommend UTM tagging conventions') to lift specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	The description names the domain and one to two concrete actions ("analyze website traffic sources, attribution, or dark traffic") but does not list multiple specific concrete actions, matching the anchor that names domain plus 1-2 actions.	3 / 5
Completeness	It explicitly answers both what ("analyze website traffic sources, attribution, or dark traffic") and when ("When the user wants to... Also use when the user mentions...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	It provides comprehensive coverage of natural phrases users would say ("traffic sources," "dark traffic," "UTM parameters," "channel attribution," "organic vs paid traffic," etc.), including synonyms and variations.	5 / 5
Distinctiveness Conflict Risk	It occupies a clear niche (traffic analysis/attribution/dark traffic) with distinct triggers and an explicit handoff ("For GA4 setup, use analytics-tracking") that minimizes overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: skills/analytics/sources/traffic/SKILL.md
Commit: 26cef34

Reviewed: 23 hours ago

Table of Contents

Discovery Implementation Validation

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.