CtrlK
BlogDocsLog inGet started
Tessl Logo

exploring-mcp-sessions

Investigate individual PostHog MCP sessions — the sequence of tool calls a single agent made in one run, what it was trying to do, and where it went wrong. Use when the user asks "what did this MCP session do?", "show me the tool calls for session X", "what was the agent's goal?", "which sessions had errors?", "who is connecting to my MCP?", or pastes an MCP analytics sessions URL.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A dense, well-organized skill body: executable tool-call and SQL examples, three explicit workflows with validation loops, and a clean overview-plus-shared-reference structure. It assumes Claude's competence and adds only non-obvious sharp edges.

DimensionReasoningScore

Conciseness

Lean, high-signal prose throughout — 'order_by takes column names, not response field names', 'distinct_id_count is always 0' — with no padding or explanation of concepts Claude already knows; every token earns its place, matching the level-3 anchor.

3 / 3

Actionability

Provides copy-paste-ready JSON tool-call blocks with exact parameters (e.g. { "date_from": "-7d", "order_by": "-session_start", "limit": 100 }) and complete, runnable HogQL, matching the level-3 fully-executable anchor.

3 / 3

Workflow Clarity

Three clearly labelled workflows each with a concrete call, plus explicit validation/feedback checkpoints — the 'date-window trap' recovery loop and the 503 fallback for generate-intent — matching the level-3 explicit-checkpoint anchor.

3 / 3

Progressive Disclosure

Body acts as an overview that offloads the full property schema and query recipes to one-level-deep, clearly-signaled references (models-mcp.md, cited twice) and links related skills in a dedicated section, with no nested reference chains.

3 / 3

Total

12

/

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 high-quality description that names three concrete capabilities and pairs them with an explicit, multi-trigger 'Use when...' clause using natural user phrasing. It is tightly scoped to PostHog MCP sessions and unlikely to collide with related skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'the sequence of tool calls a single agent made in one run, what it was trying to do, and where it went wrong' — matching the level-3 anchor for several specific actions; not level 2 because it goes beyond naming a domain plus a few actions.

3 / 3

Completeness

Explicitly answers both 'what' (investigate the sequence of tool calls and the goal/errors) and 'when' via an explicit 'Use when...' clause with multiple triggers, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Includes six verbatim phrases a user would naturally say ('what did this MCP session do?', 'show me the tool calls for session X', 'which sessions had errors?', 'who is connecting to my MCP?') plus a URL-paste trigger, giving full coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche — individual PostHog MCP sessions — with triggers unlikely to fire for sibling skills (tool-usage, tool-quality, intent-clusters), so conflict risk is low.

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: 6 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.