CtrlK
BlogDocsLog inGet started
Tessl Logo

exploring-mcp-tool-usage

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.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable router skill with strong question-to-tool mapping and a clear follow-up loop. Its main weakness is redundancy: the failures raw-name exception and the per-tool tool list each recur across multiple sections.

Suggestions

State the posthog:query-mcp-tool-failures raw-$mcp_tool_name exception once (in "Finding the tool name") and reference it elsewhere instead of repeating it in the intro and "When to drop to SQL" sections.

Drop the "Covered by a typed tool" table in "When to drop to SQL" since it duplicates the Suggested-questions menu; keep only the "Not covered" list and the flag-off fallback note there.

Trim the opening two paragraphs into one — the $mcp_tool_call event explanation and the mcp-analytics flag/toolName-nuance can be folded so the menu appears sooner.

DimensionReasoningScore

Conciseness

The body is dense and free of basic-concept padding, but the posthog:query-mcp-tool-failures raw-$mcp_tool_name exception is restated three times (intro, "Finding the tool name", and "When to drop to SQL") and the "Covered by a typed tool" table duplicates the Suggested-questions menu, so it could be tightened.

2 / 3

Actionability

Maps each question to a specific typed tool, gives a copy-ready example call (posthog:query-mcp-tool-stats with toolName/dateRange JSON), and explicitly enumerates which cases require posthog:execute-sql.

3 / 3

Workflow Clarity

Clear routing sequence — offer the menu, find the tool name (broad question → exploring-mcp-tool-quality → drill in), call the per-tool tool, then offer a natural follow-up from the menu — with an explicit follow-up loop after results.

3 / 3

Progressive Disclosure

A single well-organized file with clearly signaled, one-level-deep links to sibling skills and models-mcp.md; no bundle files are needed and the menu is appropriately inline as the core content.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does and gives multiple natural trigger phrases. It is specific, complete, and well-distinguished from sibling focused skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "routes a broad question to the typed tool that answers it", "Offers a menu of questions, each backed by a query tool, then hands off to the focused skill" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (routes broad questions to typed tools / offers a menu / hands off to the focused skill) and when ("Use when the user asks…" with concrete triggers).

3 / 3

Trigger Term Quality

Includes six quoted natural phrases a user would actually say — "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?", plus pasting an MCP analytics URL.

3 / 3

Distinctiveness Conflict Risk

A narrow PostHog MCP-analytics niche positioned as the entry router that "hands off to the focused skill", with distinct broad-question triggers unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository
PostHog/posthog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.