manage-boards

Manage Boards

Engine required — resolve an engine per ENGINE.md: one named in the conversation or loaded instructions is mandatory (not set up → offer /mixpanel:install for it); otherwise use the Mixpanel MCP server, or offer /mixpanel:install if it's unavailable.

Top-level router: validate project → route command → handle return.

This skill uses the resolved Mixpanel engine only. No other connectors are required or referenced.

---

Execution Philosophy

Silent execution. Do not narrate steps, announce phases, or explain what you are about to do. Run the work, process results, present only final output. The user sees:

• Command menu (when needed)
• Confirmation prompts before destructive operations (delete, bulk cleanup)
• Progress indicators during batch operations
• Error messages
• Final output

Nothing else. No "Starting X...", no "I'll now fetch Y...", no "Let me analyze Z...". Just do the work and show the result.

---

Global Rules

1. Silent execution — see the Execution Philosophy section above.
2. Project ID immutable. All work uses the confirmed project_id unless explicitly cross-project (template command).
3. Surface MCP failures explicitly. Never silently skip.
4. Confirm before destructive ops. Always preview + explicit user confirmation before: deleting a dashboard, bulk cleanup, or overwriting dashboard content.
5. 'exit' always valid. Stop, discard uncommitted, return to menu.
6. No per-command "what next" menus. Commands return control here. The router shows the menu.
7. Cross-project operations. The template command is the only one that works across projects. It validates both source and target project IDs and reconstructs the board in the target project (see commands/template-dashboard.md).
8. Validate every write before reporting success. After any operation that mutates a board — create, update, duplicate, or a template rebuild — re-read the affected board including its full layout and confirm the result matches intent (expected row count, report/text cell counts, title/description). If the readback diverges, do NOT report ✅ — surface what landed vs. what was requested. Layout cells use opaque server-generated IDs, so a write can partially succeed silently; the readback is the only reliable confirmation. Refresh dashboard_layout_cache from this readback.
9. Fetching the dashboard set. Default to the sortable entity-search capability when listing dashboards — it returns richer metadata and supports sorting. Fall back to the plain dashboard-list capability only if search is unavailable. Cache the result in dashboard_list_cache and reuse it across commands rather than re-fetching.
10. Shared constraints. Layout limits, the text-card HTML whitelist, and other API gotchas live once in references/mcp-tool-reference.md. Command files point to it by name rather than restating.