What problem does it solve?
Editing exported Metabase serdes YAML files (cards, dashboards, databases) is error-prone because portable references must exactly match exported databases, tables, and fields, and mistakes break imports. This Skill provides the structural conventions, safe-edit rules, and a mandatory validation loop to keep edits consistent.
Core Features & Use Cases
- Portable Reference Guidance: Explains how databases, tables, fields, and cards are referenced by name paths and entity IDs instead of integer IDs.
- Safe vs Structural Edits: Distinguishes low-risk changes (name, display, visualization_settings) from schema-bound changes (dataset_query, result_metadata, table_id).
- Validation Loop: Requires running the structural and cards checkers after every edit and provides a self-healing workflow for resolving checker errors.
- Use Case: When changing a card's source table from ACCOUNTS to ORDERS in an exported instance, update table_id, source-table, and every result_metadata entry consistently, then verify with both checkers.
Quick Start
Ask the AI to rename a card and change its visualization to a bar chart in the exported serdes YAML, then run both checkers to confirm the edits are valid.