What problem does it solve?
PostHog endpoints have no native cross-project copy operation, unlike feature flags or experiments. This Skill guides the read-then-recreate workflow needed to duplicate an endpoint into another project or under a new name in the same project, avoiding common mistakes like copying out of the wrong source project or silently overwriting an existing name.
Core Features & Use Cases
- Read-then-recreate workflow: Reads the full source endpoint config with
endpoint-get (query, variables, freshness, materialisation, tags) and recreates it with endpoint-create in the target project.
- Active-project switching: Coordinates switching the active MCP project between the source read and the target create, since neither tool accepts a project id.
- Safe defaults and collision checks: Verifies name availability in the target project and defaults the copy to unmaterialised to avoid unnecessary recompute costs.
- Use Case: Promote a validated endpoint from a staging project to production by reading its HogQL query and variables, switching to the production project, recreating it under the same name, and verifying it with
endpoint-run.
Quick Start
Copy the endpoint named weekly_active_users from my staging project to the production project and verify it runs correctly.
