CtrlK
BlogDocsLog inGet started
Tessl Logo

check-posthog-loading

Inspect how the PostHog JavaScript SDK is loaded across a list of URLs. Use to confirm consistent installation across pages, find pages missing the snippet, detect mismatched API keys or hosts between pages, and verify the load method (head snippet vs deferred vs array.js).

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

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.

A well-structured, concise MCP-wrapper skill that gives concrete invocation parameters and a useful diagnostic checklist for interpreting results. The only minor gap is the absence of an example tool-call payload.

Suggestions

Add a short example invocation showing a concrete `urls` list and the default `posthog_host` to make the call copy-paste ready.

Optionally include a one-line example of the returned structured summary shape to anchor the interpretation guidance.

DimensionReasoningScore

Conciseness

Lean and efficient body with no padding about what PostHog is or how analytics SDKs work; every section (reports, when to use, how to invoke, interpreting results) earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides concrete invocation guidance ('Call the `check_posthog_loading` MCP tool with: urls (required)..., posthog_host (default...)') and specific red-flag interpretation criteria, but lacks a literal example call payload.

4 / 5

Workflow Clarity

Single-purpose read-only skill with an unambiguous action (call the tool, then interpret results); the red-flags checklist in 'Interpreting the result' acts as a clear validation/decision guide, satisfying the simple-skill exception.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references; content is split into well-organized, clearly signaled sections (When to use, How to invoke, Interpreting the result) and no bundle files are present.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A strong, specific description that clearly states what the skill does and when to use it with concrete trigger scenarios. Third-person voice is used correctly and capabilities are concrete rather than vague.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'confirm consistent installation across pages', 'find pages missing the snippet', 'detect mismatched API keys or hosts', 'verify the load method (head snippet vs deferred vs array.js)' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ('Inspect how the PostHog JavaScript SDK is loaded across a list of URLs') and when ('Use to confirm consistent installation..., find pages missing the snippet, detect mismatched API keys or hosts..., verify the load method') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('PostHog', 'snippet', 'API keys', 'hosts', 'pages', 'load method') that users debugging instrumentation would say, though a few natural synonyms ('events', 'tracking', 'project') are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — PostHog JS SDK loading inspection across URLs — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.