HitKeep Analytics Agent Skills

HitKeep publishes five analytics skills for assistants that answer questions about scoped HitKeep data. They teach evidence selection, metric interpretation, privacy boundaries, and when to use MCP, official docs, the dashboard, REST API, exports, or takeout.

The skills contain no credentials and query no data by themselves. Pair them with the HitKeep MCP server for live aggregate analytics.

Two adapters, one analytics procedure

Each public skill contains:

a SKILL.md adapter for external assistants using production HitKeep MCP;
a transport-neutral references/procedure.md with the actual analytics reasoning.

HitKeep Ask AI compiles the same transport-neutral procedures into the application and supplies its own internal analytics tools. Ask AI does not use MCP, and HitKeep does not embed MCP token setup, external-client instructions, contributor workflows, or repository tooling into its prompt.

Analytics pack

Skill	Use it for
`hitkeep-analytics`	Broad analytics questions, evidence routing, MCP boundaries, and choosing the appropriate HitKeep surface.
`hitkeep-traffic-diagnosis`	Traffic drops, spikes, source shifts, deploy effects, suspicious changes, and measurement checks.
`hitkeep-ai-visibility-analyst`	AI crawler fetches, AI referrals, assistant families, path correlation, Search Console context, and fetch failures.
`hitkeep-ecommerce-analyst`	Revenue, orders, products, source quality, UTM performance, and conversion movement.
`hitkeep-tracking-verifier`	Tracker installation, missing pageviews or events, automatic events, hostname mismatch, blockers, consent, and CSP.

Install the full pack for broad assistant use. Install one specialist when the assistant has a deliberately narrow role. The parent remains useful when installed alone.

Install only the analytics pack

Use the /skills repository subdirectory so a customer-facing analytics assistant does not receive HitKeep’s contributor workflows.

List the pack:

npx skills add https://github.com/PascaleBeier/hitkeep/tree/main/skills --list

Install all five skills for Codex:

npx skills add https://github.com/PascaleBeier/hitkeep/tree/main/skills \
  --skill '*' --agent codex --copy -y

Install only traffic diagnosis:

npx skills add https://github.com/PascaleBeier/hitkeep/tree/main/skills \
  --skill hitkeep-traffic-diagnosis --agent codex --copy -y

Do not use a repository-wide --skill '*' command when the assistant only needs analytics. The repository also contains a separate contributor pack for changing HitKeep itself.

Connect production MCP

Enable MCP on a HitKeep leader:

HITKEEP_MCP_ENABLED=true
HITKEEP_MCP_PATH=/mcp

Create a dedicated personal or team API client token, grant only the sites the assistant needs, and configure the client to send it as a bearer token. MCP does not accept dashboard cookies.

Authorization: Bearer <hitkeep-api-client-token>

The production MCP surface is read-only and aggregate-only. It can provide visible sites, site overview, events, ecommerce, Web Vitals, AI visibility, saved Opportunities, imported Search Console reports, and official documentation. It does not expose raw visitor rows, raw hit exports, billing actions, token management, site administration, or analytics mutations.

Ask useful questions

Broad analysis:

Use $hitkeep-analytics to compare traffic, events, ecommerce, Web Vitals, AI visibility, and Search Console for the last 30 days.

Focused diagnosis:

Use $hitkeep-traffic-diagnosis to explain why organic traffic dropped after Tuesday's deploy.

Use $hitkeep-ai-visibility-analyst to review heavily fetched paths with weak later AI-referred traffic.

Use $hitkeep-ecommerce-analyst to compare revenue and conversion quality by source.

Use $hitkeep-tracking-verifier to determine whether this installation is actually sending pageviews and automatic events.

Good answers name the site, date range, comparison range, metric, evidence source, and material caveats. They keep crawler fetches separate from human referrals, treat path correlation directionally, and never infer individual identity from aggregate rows.

Contributor skills are separate

The repository’s contributor skills—hitkeep-development, hitkeep-workspace, hitkeep-qa, and hitkeep-i18n—live under .agents/skills. They operate the local hk developer platform and are never embedded into HitKeep Ask AI.

Contributors should follow the local development and contribution guide instead of installing the analytics pack as a development workflow.

Troubleshooting

The skill has no live data

Verify that MCP is enabled on the leader, the client uses the correct /mcp URL, the bearer token is present, and the API client has an explicit grant for the requested site.

Traffic or AI visibility counts disagree

Check the date range and filters first. AI crawler fetches, AI-referred human visits, Search Console rows, and normal traffic are different signals and may use different collection paths.

Tracking cannot be proven from aggregates

Use the dashboard tracking status, browser network evidence, or authorized server evidence. An empty aggregate report does not prove that a site has no visitors or that the tracker never loaded.