managing-dashboards

Guides PostHog dashboard platform changes across API, frontend, sharing, and template surfaces.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill managing-dashboards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-dashboards
Source: https://github.com/PostHog/posthog-foss/tree/main/.agents/skills/managing-dashboards
Command: npx skills add https://github.com/PostHog/posthog-foss --skill managing-dashboards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Dashboard changes in PostHog span many surfaces—authenticated scenes, public shares, embeds, exports, and templates—and a change that works in one place can silently break permissions, caching, or layouts in another. This Skill gives engineers a structured routing, design, and testing process so dashboard platform changes stay consistent and safe across every surface.

Core Features & Use Cases

  • Change routing and surface analysis: Classifies requests between dashboard platform work and widget work, then forces an explicit affected/unaffected decision for each rendering surface before coding.
  • Design gates and contracts: Provides checklists for RBAC, filters and variables, caching and scale, responsive layouts, templates, and backend operations, backed by seven in-depth reference documents.
  • Boundary-focused testing and code map: Lists edge cases (empty dashboards, shared tokens, concurrent edits, streaming failures) plus a file-level map of the dashboards backend, frontend scene, and MCP tools.
  • Use Case: When adding a new dashboard filter type, an engineer uses the Skill to define filter precedence, verify shared-token behavior, update serializers and OpenAPI output, and run the focused test commands for each edited layer.

Quick Start

Ask the agent to plan and implement a change to PostHog dashboard filters, layout, sharing, or templates using the managing-dashboards skill.

Frequently Asked Questions about managing-dashboards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely change a PostHog dashboard feature?

Route the request first, record which surfaces are affected, then define a change contract covering permissions, shared and embedded behavior, filter precedence, and cache behavior before implementing. The Skill provides checklists and reference docs for each area.

When should I use manage-dashboard-widgets instead of this Skill?

Use manage-dashboard-widgets whenever the change involves a new or modified widget_type, widget config, widget query, or WidgetCard. This Skill covers the dashboard platform, scene, tiles, sharing, and templates instead.

What must I check before enabling public sharing on a dashboard?

Verify the shared response hides private metadata, uses the shared-safe widget serializer, blocks forced refreshes, and keeps the cache clamp so anonymous traffic cannot trigger recomputation. Test enable, disable, read, and denied mutation paths.

Does this Skill cover dashboard API and MCP changes?

Yes. It requires serializer schema annotations, running hogli build:openapi after contract changes, defining MCP operations in products/dashboards/mcp/tools.yaml with scopes, and testing REST and MCP behavior separately.

How are dashboard layout changes tested?

Test narrow and wide breakpoints, drag, resize, insert, duplicate, and persisted layout reload, while preserving old layout JSON. Run the focused tests for tileLayouts, insertTileGeometry, and editLayoutGesture listed in the layout reference.

What are the limits of this Skill's scope?

It does not cover widget internals, Django migration mechanics, or generic DRF and Kea patterns; those are delegated to companion skills like manage-dashboard-widgets, django-migrations, and writing-kea-logics.