What problem does it solve?
Publishing a PostHog canvas involves version guards, capability declarations, queued server-side builds, and conflict recovery; doing it wrong can silently overwrite concurrent work or leave a stale canvas after a failed build. This Skill walks through the full lifecycle so every publish is safe and verified.
Core Features & Use Cases
- Capability declaration and validation: Inventory every insight, capture event, inline query, agent request, and network origin, then iterate on
canvas-validate-create diagnostics until clean.
- Guarded publishing and drafts: Publish with
expected_current_version_id, or stage a draft build and promote it only after user approval, with capability_widening surfaced before promotion.
- Build monitoring and conflict recovery: Poll
canvas-builds-retrieve until the build is terminal, retry 429 capacity limits, and recover from 409 version conflicts by re-reading and re-applying edits.
- Use Case: After editing a canvas that already has a live version, stage a draft, wait for its build to become ready, show the user the widened capabilities, and promote only on approval.
Quick Start
Validate my canvas project, stage it as a draft build, and tell me when the build is ready to promote.