CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging-surveys

Debug, support, and build PostHog Surveys across the backend and all five SDKs (web/posthog-js, iOS, Android, Flutter, React Native). Use whenever a Surveys support ticket is pasted ("survey not showing", "fewer responses than expected", "responses disappeared", "survey shows on wrong platform"), when diagnosing why a survey does or doesn't display, or when doing survey feature work that must ship across SDKs. Covers the eligibility pipeline, cross-SDK feature parity, the known-cause catalog, read-only diagnostic queries, staff access, and the customer-reply style guide.

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

Passed

No findings from the security scan

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 high-signal, actionable debugging guide with clear sequenced workflows, validation checkpoints, and well-structured one-level-deep references to real bundle files. Its only weakness is mild verbosity from restated table content and slightly long prose sections, which keeps conciseness below the top anchor.

Suggestions

Collapse the 'Consequences worth memorizing' bullets into references to the parity table above, or trim them to only the non-obvious consequences not already readable from the table, to remove restated content.

Tighten the Repos and Access sections by leading with the commands/endpoints and moving rationale into shorter clauses, cutting prose that assumes less than Claude's competence.

Consider promoting the detailed 'How a survey actually gets shown' pipeline walkthrough to a reference file if it grows, keeping the inline version to the ordered checklist plus the two non-obvious facts.

DimensionReasoningScore

Conciseness

Mostly efficient and packed with PostHog-specific knowledge Claude lacks, but the 'Consequences worth memorizing' bullets restate the parity table and the repos/access prose runs long enough to tighten. Not padded with basic concepts, yet not lean enough for the top anchor.

2 / 3

Actionability

Provides executable commands (scripts/repos.py invocations), concrete API endpoints with parameter shapes, exact file paths to grep, and links to copy-paste-ready HogQL templates — fully actionable guidance.

3 / 3

Workflow Clarity

The 7-step debugging workflow has an explicit disambiguation checkpoint ('none vs fewer') and a 'confirm with one targeted query' gate, while each known cause pairs a 'Signature' with a 'Fix', giving clear sequencing with validation feedback loops.

3 / 3

Progressive Disclosure

Keeps core tactical overview inline while externalizing separable material into verified one-level-deep references (diagnostic-queries.md, local-repos.md) and a script (repos.py), each clearly signaled with a description of its contents.

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 specific, complete, and distinctive: it names concrete capabilities across a clear niche, lists exact user-facing trigger phrases, and explicitly separates 'what' from 'when' in third-person imperative voice. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Debug, support, and build PostHog Surveys') across the backend and five named SDKs, then enumerates covered domains (eligibility pipeline, cross-SDK parity, known-cause catalog, diagnostic queries, staff access, reply style guide).

3 / 3

Completeness

Explicitly states what the skill does ('Debug, support, and build...') and when to use it ('Use whenever a Surveys support ticket is pasted...'), answering both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes verbatim phrases users actually paste ('survey not showing', 'fewer responses than expected', 'responses disappeared', 'survey shows on wrong platform'), giving strong natural-term coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to PostHog Surveys across five named SDKs with distinctive paste-trigger phrases, 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.