CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

posthog-instrumentation

Product analytics with posthog. Use when adding a meaningful user action or feature in `web/**`, touching PostHog capture code, changing session replay or its privacy boundaries, or answering product-usage questions.

Quality

84%

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

88%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 an exemplar of actionable, project-specific skill writing: concrete APIs, naming registries, privacy rules grounded in real incidents, and a numbered workflow with live verification and feedback loops. Its only notable weaknesses are mild repetition across the One-idea/Rules/Workflow/Anti-patterns sections and a SKILL.md that carries more inlined doctrine (especially session replay) than a lean overview-plus-references split would.

DimensionReasoningScore

Conciseness

The body is dense and project-earned — no explanation of what PostHog is or how analytics works — with nearly every token carrying non-obvious, hard-won guidance. Not anchor 5 because there is mild repetition: the "One idea" paragraph restates Rule 1, and the Workflow and Anti-patterns sections restate the six rules (efficiently, via "(Rule N)" cross-references, but still overlapping).

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: exact hook (`usePostHogClientCapture()` → `capture(eventName, props?)`), exact registry mechanism and typecheck enforcement, exact naming conventions with real examples (`saved_views:view_selected`), exact prop rules (`objectAdjective`, `is`/`has`, `Date` suffix), and an exact verification method (Playwright spy on `window.posthog.capture` or the ingest POST, with three named assertions). Per the rubric's code-vs-instruction note, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

The Workflow section gives a clear 5-step sequence (plan → register → wire → verify live → PR) with an explicit validation step carrying three concrete assertions (fire exactly once, dimension correct, no raw values), a feedback loop ("Fix any pre-existing leaks you pass"), a checklist section of anti-patterns, and a separate branch for replay-only changes. This matches anchor 5's sequence-plus-validation-plus-feedback shape.

5 / 5

Progressive Disclosure

Both referenced bundle files exist, are one level deep, and are clearly signaled with read-when guidance ("Read when designing a new taxonomy or debating naming/scope", "Read when hardening the pattern or adding global dimensions"), matching the top of the anchor range. Held at 4 rather than 5 because the body itself inlines the full six-rule doctrine and an entire session-replay privacy sub-skill (~80 lines) that could partly live in a reference, making SKILL.md heavier than a clear overview.

4 / 5

Total

18

/

20

Passed

Description

73%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 has an explicit, multi-trigger when-clause with concrete, natural trigger terms and a clearly distinct niche. Its main weakness is the what-clause: "Product analytics with posthog" is generic and omits the concrete actions the skill performs (event registration, metadata-only privacy rules, live verification), which also costs it trigger synonyms like "instrumentation" and "tracking".

Suggestions

State the concrete actions the skill performs in the what-clause, e.g. "Decide whether a frontend action warrants an analytics event, register typed PostHog events, enforce metadata-only privacy rules, and verify captures live" instead of the generic "Product analytics with posthog".

Add natural trigger synonyms users would say — "instrumentation", "tracking", "analytics events", "telemetry" — to the when-clause alongside the existing posthog/session-replay terms.

Make explicit that this is an instrumentation and privacy-boundary guide (including session replay masking), so the what tells Claude what it will be asked to do, not just the product domain.

DimensionReasoningScore

Specificity

The what-clause is just "Product analytics with posthog" — domain named but actions minimal — matching anchor 2's shape, while the concrete trigger activities ("adding a meaningful user action or feature in `web/**`", "touching PostHog capture code", "changing session replay or its privacy boundaries") pull it above the generic midpoint toward anchor 3. It falls between anchors 2 and 3 because the when-clause describes specific activities but the what never states what the skill actually does.

3 / 5

Completeness

Both what and when are present, and the when is explicit with multiple concrete trigger phrases ("Use when adding a meaningful user action... touching PostHog capture code, changing session replay..."). Not anchor 5 because the what ("Product analytics with posthog") is terse and does not state what the skill concretely does (decide whether to instrument, register events, enforce privacy rules, verify captures).

4 / 5

Trigger Term Quality

Good natural keyword coverage — "posthog", "product analytics", "session replay", "capture code", "product-usage questions" are phrases a user would plausibly say — but common synonyms like "instrumentation", "tracking", "analytics events", or "telemetry" are missing. Not anchor 5's comprehensive synonym/extension coverage; clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers — PostHog capture code, session replay privacy boundaries, "web/**" user actions — that few other skills would claim. "Answering product-usage questions" is slightly broad, but it stays within this skill's analytics scope, keeping conflict risk minimal per anchor 5.

5 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 suspicious

Warning

Total

15

/

16

Passed

Repository

langfuse/langfuse

Path

.agents/skills/posthog-instrumentation/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.