Standard Skill: BI Import (Metabase)
BI Import (Metabase) is a Standard Skill: it brings what your company already built in Metabase into the Semantic Layer, so that it isn’t typed again. The agent loads it when you ask it to import from Metabase or your BI tool. To pick it yourself, type / and choose bi-import-metabase.
What you need
Section titled “What you need”- Your own Metabase Integration, selected for the Conversation. The agent reaches Metabase only through it, so it sees exactly what you may see in Metabase. If it needs you to sign in, the agent asks you to connect; without one, it tells you to add or select it. See Metabase.
- The Right to create Context Change Requests on the Data Source you import into.
The agent only reads in Metabase: it creates, changes and deletes nothing there.
What the agent does
Section titled “What the agent does”- It matches the Metabase database to the Data Source by their table names and asks you to confirm the match.
- It lists what Metabase has on that database, models, metrics and saved questions with their collections, and asks which to import, recommending the verified ones and those in shared collections. It leaves out drafts, broken questions, duplicates and archived ones, and says so. It asks before it imports anything from a personal collection, because the entry becomes visible to everyone who can access the Data Source.
- It reads the Semantic Layer first and changes an entry that exists rather than adding a second one. When Metabase and an entry disagree, it asks you which is right.
- Models and metrics go into the Data Model: a model’s columns with their display names and descriptions, each metric as a measure written in SQL, which it runs once to check. Every table and column name comes from the Data Source, never from Metabase alone.
- Saved questions become Verified Queries. Each runs on the Data Source before it is written, names the Metabase question with its address as its source, and says imported from Metabase rather than who confirmed it, because nobody here confirmed its result. A question whose SQL doesn’t run becomes an open question, not an entry.
- It proposes them as a Context Change Request of at most 50 changes, or several requests for more, whose explanation names the collections, what was left out and the open questions.