Exploring The Wizard
PostHog/wizard
Drive the PostHog wizard headlessly against a throwaway app through wizard-ci MCP tools, inspect decisions, and capture the real TUI.
Starting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it.
Install Exploring MCP Tool Usage
$ npx skills add PostHog/posthog --skill exploring-mcp-tool-usage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-usage --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-usage .claude/skills/exploring-mcp-tool-usage && 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-usage" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-usage into .claude/skills/exploring-mcp-tool-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-usage", 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-usageType 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-usage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-usage --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-usage .agents/skills/exploring-mcp-tool-usage && 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-usage" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-usage into .agents/skills/exploring-mcp-tool-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-usage", 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-usage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-usage --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-usage .cursor/skills/exploring-mcp-tool-usage && 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-usage" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-usage into .cursor/skills/exploring-mcp-tool-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-usage", 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-usage--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-usage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog exploring-mcp-tool-usage --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-usage .gemini/skills/exploring-mcp-tool-usage && 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-usage" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-usage into .gemini/skills/exploring-mcp-tool-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-usage", 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-usageInstalls 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-usage -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-usage .github/skills/exploring-mcp-tool-usage && 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-usage" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-usage into .github/skills/exploring-mcp-tool-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-usage", 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-usage -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-usage --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-usage .opencode/skills/exploring-mcp-tool-usage && 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-usage" agent skill from https://github.com/PostHog/posthog/tree/master/products/mcp_analytics/skills/exploring-mcp-tool-usage into .opencode/skills/exploring-mcp-tool-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-mcp-tool-usage", 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-usage- GitHub stars
- 40k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 682 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Starting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it.
- The user asks how is my MCP doing?
- SKILL.md covers Governed metric first, Suggested questions, Finding the tool name and How to use a per-tool tool, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- What should I look at?
What it does
Exploring MCP Tool Usage is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Starting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it. Use when the user asks "how is my MCP doing?", "what should I look at?", "explore my tool calls", "who uses my MCP tools?", "what are agents doing with the MCP?", or pastes an MCP analytics URL without a specific question. Offers a menu of questions, each backed by a query tool, then hands off to the focused skill.
Its SKILL.md is about 1.8k 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 Model Context Protocol and PostHog. 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 how is my MCP doing?
- What should I look at?
- Explore my tool calls
- Who uses my MCP tools?
Example prompts
- “how is my MCP doing?”
- “what should I look at?”
- “explore my tool calls”
- “/exploring-mcp-tool-usage”
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.
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 Usage loads about 1.8k tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 682 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 682 words (~1,818 tokens).
“Any MCP server instrumented with the @posthog/mcp SDK emits a $mcp_tool_call event every time an agent invokes a tool. This skill is the front door for a user who knows they want to look at their MCP tool usage but…”
- name
- exploring-mcp-tool-usage
Files
Just SKILL.md in products/mcp_analytics/skills/exploring-mcp-tool-usage 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 Usage 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 Usage this skillPostHog/posthog | 40k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Exploring The WizardPostHog/wizard | 197 | — | ~2.2k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Fastmcp Client CLI
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
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 Usage
What does Exploring MCP Tool Usage do?
Starting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it. Exploring MCP Tool Usage is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Starting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it.
When should I use Exploring MCP Tool Usage?
Exploring MCP Tool Usage fits situations like: the user asks how is my MCP doing?; what should I look at?; explore my tool calls; who uses my MCP tools?.
How do I install Exploring MCP Tool Usage in Claude Code?
Run `npx skills add PostHog/posthog --skill exploring-mcp-tool-usage -a claude-code`. Or copy the skill folder (products/mcp_analytics/skills/exploring-mcp-tool-usage in PostHog/posthog) into .claude/skills/exploring-mcp-tool-usage in your project. Claude Code loads it when a task matches its description.
How do I install Exploring MCP Tool Usage in Codex?
Run `npx skills add PostHog/posthog --skill exploring-mcp-tool-usage -a codex`. Or copy the skill folder (products/mcp_analytics/skills/exploring-mcp-tool-usage in PostHog/posthog) into .agents/skills/exploring-mcp-tool-usage in your project. Codex loads it when a task matches its description.
Can I use Exploring MCP Tool Usage 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-usage -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-usage, .gemini/skills/exploring-mcp-tool-usage, .github/skills/exploring-mcp-tool-usage and .opencode/skills/exploring-mcp-tool-usage in your project.
What does Exploring MCP Tool Usage need to run?
SKILL.md names no scripts, command-line tools or credentials: Exploring MCP Tool Usage is instructions for the agent only.
Does Exploring MCP Tool Usage 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 Usage 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 Usage use?
Exploring MCP Tool Usage 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 Usage use?
About 1.8k tokens (SKILL.md is roughly 7.3k 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 Usage?
Skills that share tags, products or a category with Exploring MCP Tool Usage: Exploring The Wizard (PostHog/wizard, 197 stars), MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars) and MCP Integration for Plugins (anthropics/claude-plugins-official, 38k 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 Usage?
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.