CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnosing-sdk-health

Diagnoses the health of a project's PostHog SDK integrations — which SDKs are out of date and how to fix them. Use when a user asks about PostHog SDK versions, outdated SDKs, upgrade recommendations, "SDK health", "SDK doctor" (the former name), or when events or features seem off and it might be due to an old SDK.

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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-sequenced, highly actionable workflow with concrete tool calls and a thoughtful trust boundary. Its only weakness is length: a few explanatory prose passages and quoted blocks could be tightened to improve token efficiency.

Suggestions

Tighten the quoted block under 'Why is it still outdated?': keep the canonical URL and a one-line trigger rule, and drop or shorten the full sample response paragraph to reduce tokens.

Compress the mobile-vs-web phrasing guidance in 'Showing the events from an outdated version' into a compact rule with a single example rather than three bulleted paraphrases.

Trim 'Interpreting severity' slightly by stating each rule as a one-line bullet; the current expansions repeat 'you don't re-check them' context already covered in the intro.

DimensionReasoningScore

Conciseness

Information-dense and free of basic-concept padding, but several passages (the full quoted 'why is it still outdated' block, the expanded mobile-vs-web phrasing examples) could be trimmed without losing the instruction; mostly efficient but with tightenable prose.

2 / 3

Actionability

Provides concrete, copy-paste-ready tool calls with exact JSON arguments (e.g. posthog:health-issues-list with kind=sdk_outdated, status=active), named fields to act on, and specific manifest files to edit, matching the fully-executable anchor.

3 / 3

Workflow Clarity

A clear five-step sequence (triage, list, drill, act, link) with explicit handling of the healthy/empty case in Step 1 and delay-expectation guidance after a fix; the rule-rechecking checkpoints are spelled out rather than left implicit.

3 / 3

Progressive Disclosure

Single self-contained file with well-organized, clearly headed sections and one clearly-signaled one-level-deep external reference (the keeping-sdks-current docs URL); no bundle files exist, so the well-organized single file satisfies the top anchor.

3 / 3

Total

11

/

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.

The description is precise, third-person, and self-contained: it states what the skill does, when to use it, and lists natural trigger terms including the legacy product name. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Diagnoses the health', 'which SDKs are out of date and how to fix them' — matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both what ('Diagnoses the health... which SDKs are out of date and how to fix them') and when via an explicit 'Use when a user asks about...' clause, matching the top anchor.

3 / 3

Trigger Term Quality

Strong coverage of natural user phrasings including 'PostHog SDK versions', 'outdated SDKs', 'upgrade recommendations', the former name 'SDK doctor', and a symptom-based trigger ('events or features seem off and it might be due to an old SDK').

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (PostHog SDK health) with distinctive triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.