CtrlK
BlogDocsLog inGet started
Tessl Logo

creating-an-endpoint

Create a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says "create an endpoint", "expose this query as an API", "turn this insight into an endpoint", or asks for help structuring a new endpoint. Steers away from common mistakes: materialising a query with cohort breakdowns or compare mode, inline-only variables on a materialised endpoint, unbounded date ranges, ambiguous names.

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.

A well-structured, highly actionable skill body with a clear sequenced workflow, validation checkpoints, and appropriate progressive disclosure via a single real reference. Its main weakness is mild redundancy between the decision sections and the closing 'Important notes'.

Suggestions

Trim the 'Important notes' section to only items not already covered in the numbered decisions (e.g., drop the restated 'name lives in the URL' and 'HogQL endpoints are more flexible' points) to reduce redundancy.

Shorten the worked example interaction or move the verbose dialogue into a reference, keeping a compact representative snippet inline.

Consider moving the data_freshness_seconds enum table into references/materializing.md alongside the freshness-vs-recompute trade-off to slim the main body further.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific guidance (HogQL variables, the freshness enum, materialisation rules) that Claude would not already know, but the 'Important notes' section restates several decisions already covered (name lives in URL, HogQL default, materialised-variable requirement) and could be tightened.

2 / 3

Actionability

Provides concrete, executable detail — specific field names (data_freshness_seconds, code_name, derived_from_insight, is_materialized), the exact freshness enum, the run URL path, variable declaration syntax, named tools (endpoint-create, endpoint-run, endpoints-materialization-preview), and a worked example interaction.

3 / 3

Workflow Clarity

A clearly sequenced 9-step Workflow with explicit validation checkpoints — step 8 verifies the response shape via endpoint-run with a sample payload, and materialisation eligibility is checked with endpoints-materialization-preview before enabling it.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that signals one real one-level-deep reference (references/materializing.md, cited twice) for the materialisation deep-dive, keeping the dense decision tree out of the main body while summarising it inline.

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.

A strong, specific description that names the concrete decisions involved, gives natural trigger phrases, and steers away from common mistakes. It answers both what and when clearly and is unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise' plus specific anti-patterns like 'materialising a query with cohort breakdowns or compare mode'.

3 / 3

Completeness

Explicitly answers what (create a PostHog endpoint with the right shape, covering named decisions) and when (a 'Use when the user says...' clause with concrete triggers).

3 / 3

Trigger Term Quality

Provides verbatim natural phrases users would say — 'create an endpoint', 'expose this query as an API', 'turn this insight into an endpoint' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (PostHog endpoints) with domain-specific triggers unlikely to fire for unrelated skills; third-person voice throughout with no first/second-person penalty.

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.