HitKeep Traffic Diagnosis
SkillSearchDiagnose HitKeep traffic drops, spikes, source shifts, and suspicious changes. Use when traffic, sessions, visitors, pageviews, events, or conversions changed; when a deploy may have affected measurement or behavior; or when search, referral, direct, campaign, and bot explanations need to be separated.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the HitKeep Traffic Diagnosis skill
What this skill tells your AI
The instructions your AI receives, as published by pascalebeier/hitkeep in skills/hitkeep-traffic-diagnosis/SKILL.md and read by ahel’s review.
Read procedure.md and follow it as the canonical diagnostic procedure.
Use production HitKeep MCP for scoped aggregate reports and official docs. Inspect live tool schemas rather than copying tool names, filters, or limits here. If MCP is unavailable, state which observations cannot be verified.
Keep the diagnosis aggregate-only, distinguish measurement changes from user-behavior changes, and report a ranked explanation rather than a list of unrelated possibilities.
Signals
- GitHub stars
- 88
- Forks
- 7
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
hitkeep-traffic-diagnosis- Source
- github.com/pascalebeier/hitkeep