Hitkeep traffic diagnosis
Diagnose 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.From its SKILL.md
npx -y skills add PascaleBeier/hitkeep --skill hitkeep-traffic-diagnosisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
0.9 KB, 97 tokens by cl100k_base, as published. Nobody here has run it
HitKeep Traffic Diagnosis
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.
What ships with it: 2 files
1.1 KB alongside SKILL.md
agents/
- openai.yaml242 B
references/
- procedure.md907 B