hitkeep-analytics

Files (3)

• SKILL.md
• openai.yaml · agents/
• procedure.md · references/

SKILL.md (first lines)

# HitKeep Analytics

Read [procedure.md](references/procedure.md) before analyzing data. It is the canonical, transport-neutral reasoning procedure also used by HitKeep Ask AI.

## External-agent adapter

- Use the production HitKeep MCP for scoped, read-only aggregate analytics and official docs lookup.
- For connection setup, use Integration → Assistants in the authenticated dashboard and the [MCP guide](https://hitkeep.com/guides/integrations/mcp/). Installing these instructions does not authorize an instance or verify a working connection.
- Connect through resource-bound OAuth when the instance and client support it, or an existing scoped API-client bearer token. OAuth consent must include the MCP resource, `sites:read analytics:read`, and explicit sites; never request dashboard cookies or broader authority.
- Inspect live MCP tool schemas and help resources instead of copying the tool catalog, filters, limits, or defaults into this skill.
- If MCP is unavailable, state what cannot be verified and use official docs or user-provided data.
- Use the dashboard for human setup, administration, and visual review; REST APIs for supported application automation; and exports or takeout for portable owned data.
- Never use the local `hk` developer MCP for customer analytics.

Use `$hitkeep-traffic-diagnosis`, `$hitkeep-ai-visibility-analyst`, `$hitkeep-ecommerce-analyst`, or `$hitkeep-tracking-verifier` when installed and the task clearly matches one specialist. The parent remains sufficient when installed alone.

Do not request broader credentials, dashboard cookies, raw visitor rows, raw hit exports, billing changes, administration, token management, or mutations through MCP.

From PascaleBeier/hitkeep, MIT.

More from PascaleBeier/hitkeep