exploring-mcp-intent-clusters — Claude Code skill: install & guide
exploring-mcp-intent-clusters analyzes PostHog MCP agent intent clusters to reveal what agents attempt to do, tool failure patterns, and semantic routing competition.
no license 202 installs ★ 101 updated 2026-10-24
npx skills add PostHog/ai-plugin --skill exploring-mcp-intent-clusters -a claude-codeWhat exploring-mcp-intent-clusters does
This skill inspects agent actions by grouping free-text $mcp_intent values into semantic goal clusters. Unlike standard call counts, it groups tasks via vector embeddings to highlight the actual objectives behind calls. Because embedding-based grouping cannot run in basic SQL, the skill retrieves precomputed snapshots via posthog:mcp-analytics-intent-clusters-retrieve.
Each cluster entry reveals error percentages, call volumes, and routing entropy. High entropy marks scenarios where agents search aimlessly across multiple tools for a single goal. The tool pivot additionally tracks description fit and tool overlap, pinpointing where vague documentation causes agents to pick competing tools.
When cluster metrics are missing or outdated, posthog:mcp-analytics-intent-clusters-recompute triggers an asynchronous background update. Session summaries are intentionally bypassed during grouping to keep call attribution precise.
What it helps with
- group agent goals into semantic clusters using vector embeddings
- locate goal clusters suffering from elevated failure rates
- detect overlapping tools that agents confuse during execution
- evaluate whether tool descriptions match agent queries
Example prompts for the agent
- Group recent agent intents and show which goals fail most often
- Inspect tool overlap and discoverability using
posthog:mcp-analytics-intent-clusters-retrieve - Trigger an async clustering snapshot refresh with
posthog:mcp-analytics-intent-clusters-recompute
How to install exploring-mcp-intent-clusters
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill exploring-mcp-intent-clusters -a claude-code2Manually: put the files in place
~/.claude/skills/exploring-mcp-intent-clusters/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/exploring-mcp-intent-clusters/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill exploring-mcp-intent-clusters -a codex2Manually: put the files in place
.agents/skills/exploring-mcp-intent-clusters/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill exploring-mcp-intent-clusters -a cursor2Manually: put the files in place
.cursor/skills/exploring-mcp-intent-clusters/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/exploring-mcp-intent-clusters2Manually: put the files in place
.github/skills/exploring-mcp-intent-clusters/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill exploring-mcp-intent-clusters -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/exploring-mcp-intent-clustersManually: put the files in place
.devin/skills/exploring-mcp-intent-clusters/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill exploring-mcp-intent-clusters -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about exploring-mcp-intent-clusters
How do I install exploring-mcp-intent-clusters in Claude Code?
Run npx skills add PostHog/ai-plugin --skill exploring-mcp-intent-clusters -a claude-code. The skill file is placed at ~/.claude/skills/exploring-mcp-intent-clusters/SKILL.md.
What is the exploring-mcp-intent-clusters skill used for?
It analyzes PostHog MCP telemetry to show what agents are trying to accomplish. You can inspect cluster error rates, discoverability issues, and identify tools that compete for identical user goals.
Why does this analysis rely on stored snapshots instead of SQL queries?
Clustering requires embedding calculations across $mcp_intent values, which cannot be handled in standard SQL. PostHog stores these results as snapshots, which can be regenerated asynchronously when needed.