Name: copying-endpoints-across-projects
Rating: 73.6 (1 reviews)
Author: PostHog

copying-endpoints-across-projects

Copy a PostHog endpoint (a saved HogQL/insight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production, replicate an endpoint's query/variables/freshness config in another workspace, or clone an endpoint to iterate on it. Unlike feature flags and experiments, endpoints have NO native cross-project copy tool — this skill covers the read-then-recreate flow (endpoint-get then endpoint-create), the active-project switching it requires, name-collision checks, and the safe defaults (land unmaterialised in the target, verify with endpoint-run). Does not cover editing endpoint versions (see managing-endpoint-versions) or authoring a brand-new endpoint from scratch (see creating-an-endpoint).

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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.

A well-structured procedural skill with a clear sequenced workflow, explicit validation checkpoints, concrete tool/field guidance, and safe defaults. It is lean and assumes competence, with only minor repetition and the absence of a filled example call keeping it from the top tier.

Suggestions

Consolidate the repeated active-project-switching and 'no server-side copy' caveats into a single statement to tighten conciseness.

Add one concrete example endpoint-create call payload (with representative query/variables fields) to lift actionability to fully copy-paste ready.

Consider trimming the rationale prose in step 5 (materialisation default) into a shorter justification to reduce body length toward an overview.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no padding about what HogQL/MCP is), but the 'no server-side copy' and active-project-switching caveats are repeated across the intro, 'one thing to know first', and the workflow steps — minor trimming possible.	4 / 5
Actionability	Names exact tools (endpoint-get/create, endpoints-get-all, endpoint-run, project-get) and enumerates the create fields and safe defaults, but provides no concrete filled example of an endpoint-create invocation, leaving a minor gap.	4 / 5
Workflow Clarity	An 8-step sequenced workflow with explicit validation checkpoints — confirm active project before reading, name-collision check with stop-and-ask, and an endpoint-run verification step — plus a feedback loop on collision for this create/destructive operation.	5 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers (When to use, What it doesn't cover, Workflow, Important notes, Available tools) and no nested or buried references; appropriately self-contained for a procedural skill, though slightly longer than an ideal overview.	4 / 5
	Total	17 / 20 Passed

Description

100%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.

A strong, third-person description that states concrete capabilities, gives a clear 'Use when' trigger clause with natural synonyms, and explicitly distinguishes this skill from adjacent endpoint/flag/experiment skills. No first/second-person voice; no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Copy a PostHog endpoint', 'duplicate it under a new name', the read-then-recreate flow ('endpoint-get then endpoint-create'), name-collision checks, and safe defaults — with comprehensive coverage of the operation.	5 / 5
Completeness	Explicitly answers both what (copy/duplicate an endpoint across projects or under a new name) and when ('Use when the user wants to duplicate... promote... replicate... or clone...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers the natural synonyms users would say — 'duplicate an endpoint', 'promote an endpoint from staging to production', 'replicate an endpoint's query/variables/freshness config', 'clone an endpoint to iterate on it' — with comprehensive variation.	5 / 5
Distinctiveness Conflict Risk	Clear niche (PostHog endpoints) with explicit boundaries — 'Unlike feature flags and experiments, endpoints have NO native cross-project copy tool' and 'Does not cover... see managing-endpoint-versions / creating-an-endpoint' — minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PostHog/posthog
Path: products/endpoints/skills/copying-endpoints-across-projects/SKILL.md
Commit: 6fca5f8

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.