Tool Selection
databricks-solutions/ai-dev-kit
Evaluates whether the agent selected appropriate MCP tools instead of shell workarounds.
Investigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow.
Install Exploring MCP Tool Quality
$ npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-quality --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/mcp_analytics/skills/exploring-mcp-tool-quality .claude/skills/exploring-mcp-tool-quality && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "exploring-mcp-tool-quality" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-quality into .claude/skills/exploring-mcp-tool-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-quality", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-qualityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-quality --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/mcp_analytics/skills/exploring-mcp-tool-quality .agents/skills/exploring-mcp-tool-quality && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "exploring-mcp-tool-quality" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-quality into .agents/skills/exploring-mcp-tool-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-quality", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-quality --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/mcp_analytics/skills/exploring-mcp-tool-quality .cursor/skills/exploring-mcp-tool-quality && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "exploring-mcp-tool-quality" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-quality into .cursor/skills/exploring-mcp-tool-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-quality", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path products/mcp_analytics/skills/exploring-mcp-tool-quality--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-quality --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/mcp_analytics/skills/exploring-mcp-tool-quality .gemini/skills/exploring-mcp-tool-quality && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "exploring-mcp-tool-quality" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-quality into .gemini/skills/exploring-mcp-tool-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-quality", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog exploring-mcp-tool-qualityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/mcp_analytics/skills/exploring-mcp-tool-quality .github/skills/exploring-mcp-tool-quality && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "exploring-mcp-tool-quality" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-quality into .github/skills/exploring-mcp-tool-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-quality", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-quality --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/mcp_analytics/skills/exploring-mcp-tool-quality .opencode/skills/exploring-mcp-tool-quality && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "exploring-mcp-tool-quality" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-quality into .opencode/skills/exploring-mcp-tool-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-quality", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
exploring-mcp-tool-quality- GitHub stars
- 40k
- Token cost
- ~2k tokens
- SKILL.md length
- 749 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow.
- The user asks which MCP tool has the highest error rate?
- SKILL.md covers Governed metric first, The two rules that matter most, Workflow: which tool has the… and Workflow: tool-quality matrix, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Whats the slowest tool?
What it does
Exploring MCP Tool Quality is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Investigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow. Use when the user asks "which MCP tool has the highest error rate?", "what's the slowest tool?", "which tools fail most often?", "how reliable is tool X?", wants a tool-quality matrix, or pastes an MCP analytics tool-quality / dashboard URL and asks what it shows.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with PostHog, Model Context Protocol and SQL. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- The user asks which MCP tool has the highest error rate?
- Whats the slowest tool?
- Which tools fail most often?
- How reliable is tool X?
Example prompts
- “which MCP tool has the highest error rate?”
- “s the slowest tool?”
- “which tools fail most often?”
- “/exploring-mcp-tool-quality”
What it can do on your machine
Read from SKILL.md and the folder at commit 10f9ad7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are sql).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Exploring MCP Tool Quality loads about 2k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 749 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 749 words (~1,966 tokens).
“Any MCP server instrumented with PostHog's MCP analytics SDK emits a $mcp_tool_call event on the shared events table every time an agent invokes a tool. There is no dedicated ClickHouse table — every field lives as a $mcp_* property on…”
- name
- exploring-mcp-tool-quality
Files
Just SKILL.md in products/mcp_analytics/skills/exploring-mcp-tool-quality of PostHog/posthog.
Open the folder on GitHubat commit 10f9ad7
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Exploring MCP Tool Quality next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Exploring MCP Tool Quality this skillPostHog/posthog | 40k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Tool Selectiondatabricks-solutions/ai-dev-kit | 1.9k | — | ~519 | Automated safety check: Pass | Custom licence | |
| Meridian MCPMeridiona/meridian | 411 | — | ~967 | Automated safety check: Notes | Custom licence | |
| Head Of Datagetnao/sylph | 211 | — | ~920 | Automated safety check: Pass | None | |
| Google Cloud Storage Basicsgoogle/skills | 21k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Relational Database MCP CloudbaseMicrock/ordinary-claude-skills | 403 | 2 repos | ~1.3k | Automated safety check: Pass | Custom licence |
Similar skills
Meridian MCP
Meridiona/meridian
Build, configure, and debug the Meridian MCP server. An agent skill from Meridiona/meridian.
Head Of Data
getnao/sylph
Head of Data agent - creates reportings and ad-hoc analytics using nao MCP tools.
- Official
Google Cloud Storage Basics
google/skills
Stores, retrieves, and manages data as objects in Cloud Storage on Google Cloud (also known colloquially as GCS) buckets.
Relational Database MCP Cloudbase
Microck/ordinary-claude-skills
This is the required documentation for agents operating on the CloudBase Relational Database.
Flow Swarm
LeoYeAI/openclaw-master-skills
Multi-agent swarm orchestration via RuFlo + Claude Code. An agent skill from LeoYeAI/openclaw-master-skills.
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Exploring MCP Tool Quality
What does Exploring MCP Tool Quality do?
Investigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow. Exploring MCP Tool Quality is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Investigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow.
When should I use Exploring MCP Tool Quality?
Exploring MCP Tool Quality fits situations like: the user asks which MCP tool has the highest error rate?; whats the slowest tool?; which tools fail most often?; how reliable is tool X?.
How do I install Exploring MCP Tool Quality in Claude Code?
Run `npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a claude-code`. Or copy the skill folder (products/mcp_analytics/skills/exploring-mcp-tool-quality in PostHog/posthog) into .claude/skills/exploring-mcp-tool-quality in your project. Claude Code loads it when a task matches its description.
How do I install Exploring MCP Tool Quality in Codex?
Run `npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a codex`. Or copy the skill folder (products/mcp_analytics/skills/exploring-mcp-tool-quality in PostHog/posthog) into .agents/skills/exploring-mcp-tool-quality in your project. Codex loads it when a task matches its description.
Can I use Exploring MCP Tool Quality in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill exploring-mcp-tool-quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exploring-mcp-tool-quality, .gemini/skills/exploring-mcp-tool-quality, .github/skills/exploring-mcp-tool-quality and .opencode/skills/exploring-mcp-tool-quality in your project.
What does Exploring MCP Tool Quality need to run?
SKILL.md names no scripts, command-line tools or credentials: Exploring MCP Tool Quality is instructions for the agent only.
Does Exploring MCP Tool Quality access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Exploring MCP Tool Quality safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Exploring MCP Tool Quality use?
Exploring MCP Tool Quality has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Exploring MCP Tool Quality use?
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Exploring MCP Tool Quality?
Skills that share tags, products or a category with Exploring MCP Tool Quality: Tool Selection (databricks-solutions/ai-dev-kit, 1.9k stars), Meridian MCP (Meridiona/meridian, 411 stars), Head Of Data (getnao/sylph, 211 stars) and Google Cloud Storage Basics (google/skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Exploring MCP Tool Quality?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,182 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 8, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.