메뉴
Export content from a running Metabase instance, validate with checkers, edit YAML, and import back. Use when the user wants to export, import, or run the full serdes round-trip workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | serdes-workflow |
| description | Export content from a running Metabase instance, validate with checkers, edit YAML, and import back. Use when the user wants to export, import, or run the full serdes round-trip workflow. |
End-to-end workflow for exporting Metabase content as YAML, validating it, editing it, and importing it back.
All commands require the :ee alias since export, import, and checkers live in enterprise code.
You need MB_DB_CONNECTION_URI set to point at the target Metabase Postgres database when importing. The running dev instance's connection string is in the worktree environment (check the nREPL or startup output).
clojure -M:run:ee export /path/to/export-dir
Flags:
-c 123,456 - export only specific collection IDs-f - include field values-e - continue on errorThis writes YAML files in the serdes directory layout:
databases/<db-name>/<db-name>.yaml
databases/<db-name>/schemas/<schema>/tables/<table>/<table>.yaml
databases/<db-name>/schemas/<schema>/tables/<table>/fields/<field>.yaml
collections/<eid>_<slug>/cards/<eid>_<slug>.yaml
Always run both checkers after any modification. They skip full Metabase startup (~8s each).
clojure -M:run:ee --mode checker --checker structural --export /path/to/export-dir
Validates YAML shapes against Malli schemas. Catches typos, missing required fields, wrong types.
clojure -M:run:ee --mode checker --checker cards --export /path/to/export-dir
Validates that card queries resolve correctly against exported metadata (tables, fields, FKs). Uses Lib under the hood.
Additional cards checker flags:
--lenient - fabricate metadata on demand (when no database schema files exist)--manifest /path/to/manifest.yaml - write manifest of all referenced entities (lenient mode only)--output /path/to/results.edn - write detailed results to fileSee the serdes-yaml-edit skill for guidance on editing YAML files. The critical rule: run both checkers after every edit before proceeding.
MB_DB_CONNECTION_URI="postgres://user:pass@localhost:5432/metabase_dbname" \
clojure -M:run:ee import /path/to/export-dir -e
The -e flag continues on error. The MB_DB_CONNECTION_URI must point at the same Postgres database the running Metabase instance uses - without it, import defaults to H2 which is wrong.
clojure -M:run:ee export /tmp/metabase-exportMB_DB_CONNECTION_URI=... clojure -M:run:ee import /tmp/metabase-export -eGuide Clojure and ClojureScript development using REPL-driven workflow, coding conventions, and best practices. Use when writing, developing, or refactoring Clojure/ClojureScript code.
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports from components.
Review Cypress E2E spec files for Metabase conventions, common gotchas, and flakiness/performance issues. Use when reviewing pull requests or diffs containing Cypress spec files in e2e/test/scenarios/.
Update or build a Metabase design-system component (frontend/src/metabase/ui — Chip, Badge, Alert, Switch, etc.) to match a Figma spec described in a Linear issue. Use when a ticket asks to restyle an existing `metabase/ui` component or implement a new one from Figma. Covers: checking out the issue, mapping the component (usage/blast radius for an existing one, or scaffolding a new one), building a Storybook showcase matrix (before styling for existing components, after for new ones), styling from exact Figma tokens while iterating with the user, and committing + migrating call sites LAST.
Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.
Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.