Conciseness

Dense with high-signal domain knowledge Claude lacks (SDK source paths, internal pipeline, parity table) and it avoids explaining basics, but several prose passages (e.g. the two-implementation wait-period explanation and the reply style guide) run long and could be trimmed. Anchor 4 ("efficient; minor instances of over-explanation that could be trimmed") fits better than 5 because not quite every token earns its place across ~285 lines.

Actionability

Provides concrete, executable guidance — specific endpoints ("GET /api/projects/<id>/surveys/<sid>/"), the HogQL helper signature "getSurveyResponse(<index>, '<questionId>')", activity-log URLs, and grep targets ("frontend/src/scenes/surveys/"). It stops short of 5 because the actual query templates and response-reading formats are deferred to references rather than given inline, leaving a minor gap.

Workflow Clarity

The "Debugging workflow" is a clearly sequenced 7-step process with explicit validation checkpoints — "Disambiguate none vs fewer" ("This single check redirects most investigations correctly"), step 2b, "Confirm with events," and "confirm with one targeted query" — and the "Before you call it an SDK bug" section is a 4-gate validation checklist for a risky conclusion. This matches anchor 5 (explicit validation steps plus a checklist for a complex process).

Progressive Disclosure

Structure and signaling are good — SKILL.md acts as an overview with clearly marked one-level-deep markdown links to references/reading-responses.md and references/diagnostic-queries.md — but those referenced files are absent from the bundle, so the navigation is broken. Per the guideline to score against the actual bundle structure, dangling references cap this at 3 rather than 4.

Specificity

Lists multiple concrete diagnostic actions and coverage areas — "Diagnose PostHog Surveys configuration and responses across all five SDKs," the eligibility pipeline, response storage ("partial responses, branching, optional questions, auto-submit"), "cross-SDK feature parity, the known-cause catalog, read-only diagnostic queries, staff access, and the customer-reply style guide" — comprehensive and concrete rather than abstract.

Completeness

Explicitly answers both halves: what ("Diagnose PostHog Surveys configuration and responses across all five SDKs…") and when ("Use whenever a Surveys support ticket is pasted (…) or when diagnosing why a survey does or doesn't display") with concrete trigger phrases. Voice is third person ("Diagnose", "Use").

Trigger Term Quality

Surfaces seven verbatim natural ticket phrases a user would actually say ("survey not showing", "fewer responses than expected", "responses disappeared", "responses are incomplete", "only the first question was answered", "the user says they didn't mean to submit", "survey shows on wrong platform") plus "diagnosing why a survey does or doesn't display" — comprehensive coverage of natural trigger terms.

Distinctiveness Conflict Risk

Occupies a narrow, well-defined niche — PostHog Surveys debugging across five named SDKs — with highly specific ticket-trigger phrases, making overlap with unrelated skills minimal.