Agent skill · posthog
managing-dashboards
Guides PostHog engineers through dashboard platform and scene changes. Use when changing Dashboard, DashboardTile, dashboardLogic, dashboard layouts, dashboard sharing or embeds, public dashboards, templates, filters, variables, refresh behavior, tile loading, dashboard lists, or dashboard permissions. Covers normal, shared, embedded, export, product-embedded, and template surfaces; RBAC; cache and query behavior; responsive layouts; and large or small dashboards. Use manage-dashboard-widgets instead for a widget_type or WidgetCard change.
What it needs
About 5k tokens when loaded.
What this skill does
Managing dashboards Use this skill for a dashboard change that affects the dashboard platform, dashboard scene, or an existing non-widget tile type. Use manage-dashboard-widgets for a new widgettype or a WidgetCard change. 1. Route the request Request Primary path -------------------------------------------------------------------------------- -------------------------- Dashboard metadata, tile lifecycle, filters, variables, refresh, list, or layout This skill Public links, sharing settings, embeds, exports, or product-embedded dashboards This skill Dashboard template creation, editing, scope, or copying This skill New or changed widgettype, widget config, widget query, or WidgetCard manage-dashboard-widgets Before coding, decide the effect on each surface. Record affected, unaffected, or not applicable. Authenticated dashboard Public shared dashboard Embedded dashboard Exported dashboard Product-embedded dashboard Dashboard template Dashboard list and project homepage, if the change changes metadata or visibility Read surfaces and ownership before you select files. 2. Define feature intake and acceptance criteria Do this before implementation for a new dashboard feature. Skip it for a narrow bug fix with an existing contract. 1. State the user problem, intended actor, and explicit non-goals. 2. State the feature action and its default behavior. 3. State where the feature stores its state: dashboard, tile, request, user, URL, or a separate team-scoped resource. 4. State the availability, read permission, and mutation permission. 5. State behavior for new rows, existing rows, and invalid or absent state. 6. State the acceptance criteria for allowed, denied, shared, and failure paths. 7. State the expected query, cache, and database-write effect. 8. State the metric or event that shows adoption, failure, or regression. 9. If the feature adds persisted state or relations, define migration, cleanup, and concurrent-edit behavior. 10. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/managing-dashboards