CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-posthog

PostHog MCP extension. PostHog analytics as a GA4 alternative or complement. Organic traffic, landing pages, device / country breakdowns, referrers, via the PostHog MCP server. Triggers on "PostHog", "posthog analytics", "GA4 alternative", "product analytics SEO".

Quality

83%

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

The canonical home for this skill is seo-posthog in AgriciDaniel/claude-seo

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, instruction-only dispatcher skill: concrete routing commands with defaults, clear validation and error-recovery guidance, and good deferral of setup detail to external docs. The recurring cost is redundancy in the Security section and the absence of a worked example of an actual HogQL query through the exec tool.

Suggestions

Consolidate the Security section: state the read-only requirement once (the bolded recommendation plus its rationale) and drop the repeated 'never create, update or delete' paragraph, since the no-credential point is already made in the frontmatter and intro.

Add one short example of delegating a query (e.g., the HogQL SELECT for per-day organic visits via `call execute-sql`) so the common case is copy-paste ready.

Trim the cross-skill spelling digression ('mcp__posthog__exec ... or mcp__PostHog__exec otherwise. Either spelling counts.') to a single line, e.g. 'Accept either `mcp__posthog__exec` or `mcp__PostHog__exec`.'

DimensionReasoningScore

Conciseness

The body is mostly efficient — a tight routing table, brief prerequisites, and pointed error handling — with no explanations of concepts Claude already knows. The Security section states the read-only rule three times and the no-credential point appears in the frontmatter, intro, and Security section, which is trimmable redundancy keeping it below anchor 5.

4 / 5

Actionability

The routing table gives concrete commands with per-command purposes, specifies the exec path ("HogQL queries through the MCP `exec` tool (`call execute-sql`)"), defaults ("days (default 28) and limit (default 50)"), and stepwise error handling. It stops short of anchor 5 because no example HogQL query or exec invocation is shown, leaving a minor gap for the common query cases.

4 / 5

Workflow Clarity

Dispatch is unambiguous per command, with a dedicated validation step (`/seo posthog check` confirms MCP connectivity and `$pageview` events) and an error-recovery checkpoint (verify "project, window, and that `$referring_domain` is captured before reporting zero organic traffic"). It does not reach anchor 5 because the cross-skill audit delegation flow has no explicit end-to-end sequence with feedback loops.

4 / 5

Progressive Disclosure

Sections are well organized, appropriately sized for a SKILL.md overview, and setup detail is correctly deferred to clearly signaled one-level-deep pointers ("extensions/posthog/docs/POSTHOG-SETUP.md"). It falls short of anchor 5 because those pointers reference paths outside the skill bundle rather than local reference files, and the ~75-line body exceeds the under-50-line simple-skill threshold the guideline cites for a top score.

4 / 5

Total

16

/

20

Passed

Description

83%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 description that clearly states the skill's capabilities and includes explicit, natural trigger phrases, with a well-defined niche. The main gaps are verb-light capability phrasing, a few missing synonyms in the trigger list, and slight overlap risk from the "GA4 alternative" trigger.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities ("Organic traffic, landing pages, device / country breakdowns, referrers, via the PostHog MCP server") covering the skill's command surface. It falls short of anchor 5 because the capabilities are noun phrases rather than explicit actions and the positioning sentence ("PostHog analytics as a GA4 alternative or complement") is the only verb-like framing.

4 / 5

Completeness

It explicitly answers both questions: what it does ("PostHog analytics as a GA4 alternative or complement. Organic traffic, landing pages, device / country breakdowns, referrers, via the PostHog MCP server") and when to use it ("Triggers on 'PostHog', 'posthog analytics', 'GA4 alternative', 'product analytics SEO'"). This matches anchor 5's requirement for concrete trigger phrases alongside a clear capability statement.

5 / 5

Trigger Term Quality

The trigger list ("PostHog", "posthog analytics", "GA4 alternative", "product analytics SEO") contains natural phrases a user would say, and the body adds terms like organic traffic and referrers. A few natural synonyms (e.g., "Google Analytics alternative", "web analytics", "traffic sources") are missing, so it does not reach anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The PostHog-via-MCP niche is clear and the triggers are distinct from generic analytics skills. The "GA4 alternative" trigger could fire for users seeking any GA4 alternative (e.g., Matomo or Amplitude), creating minor overlap risk with closely related sibling skills, which matches anchor 4 rather than anchor 5.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AgriciDaniel/claude-seo

Path

extensions/posthog/skills/seo-posthog/SKILL.md

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.