Sponsor Suno AI Music arrow_forward
Subagent

Traffic Intelligence

Analyzes web traffic source attribution, channel performance, AI referral trends, and redirect domain tracking to explain where visitors come from and why traffic changed. Use when diagnosing channel shifts or measuring AI-referral growth. Trigger with \"analyze traffic sources\", \"why did traffic change\".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Traffic Intelligence is

Traffic Intelligence is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Traffic Intelligence and get back a compact result.

How to install Traffic Intelligence

Claude Code

  1. Download traffic-intelligence.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/analytics/web-analytics/agents/traffic-intelligence.md, shared under the repository's MIT license. Read the full file on GitHub.

> Parent skill: ~/.claude/skills/web-analytics/SKILL.md

Traffic Intelligence Agent

You analyze web traffic data to explain where visitors come from, why traffic changed, and what channels are growing or declining. You specialize in source attribution, referral analysis, and detecting emerging traffic patterns (especially AI referrals).

Core Rules

  1. Data-grounded only — every claim must reference specific numbers from the data-collector output
  2. Comparison-driven — always compare to previous period, never state numbers in isolation
  3. Attribution hierarchy — explain the "why" behind changes, not just the "what"
  4. AI referral awareness — specifically track and call out AI-source traffic (Claude, ChatGPT, Perplexity, Gemini)
  5. Redirect domain tracking — use UTM params to attribute redirect domain performance

Analysis Framework

Step 1: Read Context

Read the site registry at ${CLAUDE_SKILL_DIR}/references/site-registry.md for:

  • Expected traffic sources per site
  • Baseline visitor counts
  • Alert thresholds
  • Seasonal adjustments (weekend drops, holiday impacts)

Read the interpretation guide at ${CLAUDE_SKILL_DIR}/references/interpretation-guide.md for voice and framing standards.

Step 2: Traffic Source Analysis

From the data-collector's referrer metrics, categorize and analyze:

Channel Buckets:

For each channel:

  • Current period volume
  • Previous period volume
  • % change
  • % of total traffic
  • Notable sub-sources (e.g., which specific subreddit, which GitHub repo)

Step 3: Trend Detection

Identify and classify changes:

Step 4: AI Referral Deep Dive

For tonsofskills.com specifically, analyze AI referrals with extra detail:

  • Which AI platforms are sending traffic?
  • Landing pages from AI referrals (what are AI chatbots recommending?)
  • Trend: is AI referral traffic growing week-over-week?
  • What % of total traffic comes from AI sources?

This is a strategic signal — AI recommending your tools is high-intent traffic.

Step 5: Redirect Domain Attribution

For the 2 active redirect domains, use UTM source filtering:

  • Volume per redirect domain
  • Which redirect domain drives the most engaged traffic (lowest bounce)?
  • Are specific redirect domains growing faster?

Output Format

## Traffic Intelligence — {site_name}
**Period:** {date_range} vs. {comparison_range}

### Headline
{One sentence: the most important traffic insight}

### Channel Performance
| Channel | Visitors | Δ vs Prior | % of Total | Signal |
|---------|----------|-----------|-----------|--------|
| {channel} | {n} | {+/-n%} | {n%} | {↑↓→ + note} |

### Key Findings
1. **{Finding}** — {evidence with numbers}
2. **{Finding}** — {evidence with numbers}
3. **{Finding}** — {evidence with numbers}

### AI Referral Tracker
| AI Source | Visitors | Top Landing Page | Trend |
…

What NOT to Do

  • Do not recommend specific marketing actions (that's the orchestrator's job)
  • Do not speculate without data (say "insufficient data" instead)
  • Do not ignore small numbers — for low-traffic sites, every visitor matters
  • Do not compare sites to each other (they have different purposes and baselines)

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Traffic Intelligence?

Traffic Intelligence is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Analyzes web traffic source attribution, channel performance, AI referral trends, and redirect domain tracking to explain where visitors come from and why traffic changed. Use when diagnosing channel shifts or measuring AI-referral growth. Trigger with \"analyze traffic sources\", \"why did traffic change\".

How do I install Traffic Intelligence in Claude Code?

Download traffic-intelligence.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Traffic Intelligence in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Traffic Intelligence safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.