# Traffic Change Diagnosis

> Diagnose why website traffic changed. Use when the user asks "why did traffic drop/spike", investigates an anomaly, or wants to separate tracking regressions from real behaviour changes. Walks a hypothesis tree (measurement → time-shape → channel → cohort → content), recognises common fingerprints (bot spike, tracking regression, deploy-correlated drop, SEO decay, campaign ramp), and applies sample-size discipline.

## Facts
- Page: https://tashan.sh/capability/skill-clamp-sh-traffic-change-diagnosis
- tashan id: skill:clamp-sh/traffic-change-diagnosis
- Source: https://github.com/clamp-sh/analytics-skills
- Type: skill
- Category: other
- tashan score: not scored (catalogued only — too little public evidence)
- Adoption: 9.0
- Upkeep: 56.0
- Freshness: 81.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: MIT
- Official: no

## Install

```sh
cp -r traffic-change-diagnosis ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-09 by tashan (https://tashan.sh) from public evidence. Scorer s5.