Name: signals-scout-mcp-tool-calls
Rating: 68 (1 reviews)
Author: PostHog

signals-scout-mcp-tool-calls

Signals scout for PostHog MCP tool calls. Watches $mcp_tool_call telemetry for tools that need improvement — high, broad-reach failure rates, retry/hammering that betrays a confusing schema, slow or context-bloating responses — groups problem tools by $mcp_tool_category (the owning product team) and files one report per problem category listing that category's problem tools each with a fix suggestion; falls back to one report per tool where category coverage is absent. Immediately-actionable reports carry a fix-loop metric (measurement query, baseline, goal) so the auto-started implementation task iterates until the number moves. Otherwise writes durable memory and closes out empty. Adapts to which fields the project actually captures.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

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

The body is a well-structured, highly actionable scout playbook with a clear sequenced workflow, validation checkpoints, feedback loops, and a properly externalized SQL cookbook — its only weakness is occasional verbose nested phrasing that could be tightened.

Dimension	Reasoning	Score
Conciseness	The body is dense and high-signal, assuming Claude's competence (no basic-concept padding), but several long nested parentheticals and double-clause sentences could be trimmed without losing meaning.	4 / 5
Actionability	Provides concrete executable guidance throughout — named tools (execute-sql, scout-emit-report, scout-edit-report), exact HogQL accessors, specific scratchpad key formats with example content, report fields, and verbatim cookbook queries referenced by number.	5 / 5
Workflow Clarity	Clear sequenced workflow (Orient → probe → grain → lenses → Decide → fix-loop metric → close out) with explicit validation checkpoints (search inbox first, disqualifiers, sanity-check novel categories) and feedback loops (measure→fix→re-measure fix-loop metric, edit-vs-author-vs-skip).	5 / 5
Progressive Disclosure	SKILL.md is an overview/framing body while the 393-line SQL cookbook is externalized to references/queries.md as a clearly-signaled one-level-deep link, and deep-dives point to baked-in posthog: skills, giving easy navigation.	5 / 5
	Total	19 / 20 Passed

Description

75%Weight 40%Scale 1-5

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

The description is specific and distinct, naming many concrete actions and a precise telemetry niche, but it lacks an explicit 'Use when…' trigger clause, which caps its completeness and leaves the invocation condition implicit.

Suggestions

Add an explicit trigger clause such as 'Use when reviewing PostHog MCP tool quality or when the user asks about failing/confusing/slow MCP tools' to satisfy the 'when' half of completeness.

Broaden trigger-term coverage with natural synonyms users say — 'MCP server', 'tool quality', 'MCP tools' — alongside the existing $mcp_tool_call jargon.

Consider tightening the long mid-sentence enumeration so the core capability reads more quickly without losing the concrete actions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Watches $mcp_tool_call telemetry', 'groups problem tools by $mcp_tool_category', 'files one report per problem category…each with a fix suggestion', 'writes durable memory and closes out empty' — giving comprehensive coverage of what it does.	5 / 5
Completeness	The 'what' is explicit and detailed, but there is no 'Use when…' clause or equivalent explicit trigger guidance for when Claude should invoke the skill, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Good keyword coverage with natural terms like 'PostHog MCP tool calls', '$mcp_tool_call telemetry', 'failure rates', 'retry/hammering', but missing common synonyms a user might say such as 'MCP server' or 'tool quality'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — PostHog MCP tool-quality scouting over the $mcp_tool_call event — with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: PostHog/posthog
Path: products/signals/skills/signals-scout-mcp-tool-calls/SKILL.md
Commit: d293866

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.