ai-readiness-checklist — Claude Code skill: install
The ai-readiness-checklist Claude Code skill checks whether Metabase data is prepared for AI features. It guides work on the data behind Metabot or the Metabase MCP server.
MIT 135 installs ★ 60 updated 2026-10-24
npx skills add metabase/agent-skills --skill ai-readiness-checklist -a claude-codeWhat ai-readiness-checklist does
The skill walks through a Metabase data-readiness checklist for AI. Its scope includes modeling with Transforms, table and field metadata, the Glossary, saved Metrics, and marking canonical content. A real question to Metabot or the MCP server can reveal which checklist areas need attention.
This is a readiness coach, not a tool for investigating bad Metabot answers. For MCP checks, it first inspects the tools available in the current session and reports only what those tools let it verify; some details need to come from the user. The checklist also tracks completed work and what remains.
What it helps with
- check whether Metabase data is ready for AI queries
- prepare models and metadata for Metabot
- review saved Metrics and canonical content
- identify remaining data work before enabling AI features
Example prompts for the agent
- Run the AI-readiness checklist on my Metabase data.
- Help me prepare the data behind Metabot.
- Check what remains before I enable AI features in Metabase.
How to install ai-readiness-checklist
1Skills CLI (Vercel)
npx skills add metabase/agent-skills --skill ai-readiness-checklist -a claude-code2Manually: put the files in place
~/.claude/skills/ai-readiness-checklist/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ai-readiness-checklist/
1Skills CLI (Vercel)
npx skills add metabase/agent-skills --skill ai-readiness-checklist -a codex2Manually: put the files in place
.agents/skills/ai-readiness-checklist/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add metabase/agent-skills --skill ai-readiness-checklist -a cursor2Manually: put the files in place
.cursor/skills/ai-readiness-checklist/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install metabase/agent-skills skills/ai-readiness-checklist2Manually: put the files in place
.github/skills/ai-readiness-checklist/SKILL.md1Skills CLI (Vercel)
npx skills add metabase/agent-skills --skill ai-readiness-checklist -a gemini-cli2Platform CLI
gemini skills install https://github.com/metabase/agent-skills --path skills/ai-readiness-checklistManually: put the files in place
.devin/skills/ai-readiness-checklist/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add metabase/agent-skills --skill ai-readiness-checklist -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ai-readiness-checklist
How do I install ai-readiness-checklist in Claude Code?
Run npx skills add metabase/agent-skills --skill ai-readiness-checklist -a claude-code. The skill file is at ~/.claude/skills/ai-readiness-checklist/SKILL.md.
What does ai-readiness-checklist do?
It guides a review of Metabase data for AI use, covering models, metadata, the Glossary, Metrics, and canonical content.
How is ai-readiness-checklist different from ai-governance-checklist?
This skill focuses on preparing data for AI. ai-governance-checklist covers who can use AI, what Metabot can access, and how AI usage is controlled.
Source text
SKILL.md · MIT
---
name: ai-readiness-checklist
description: >
A Metabase AI-readiness coach, covering the *data groundwork* that makes AI answers
trustworthy: modeling with Transforms, table and field metadata, the Glossary, saved Metrics,
and marking canonical content. Use this skill whenever the user wants to check if their data
is ready for AI, prep the underlying data for Metabot or the Metabase MCP server, work
through an AI readiness checklist, or audit their data modeling/metadata/metrics before
turning on AI features. Trigger it even if the user just says "is my data AI ready?", "let's
get set up for Metabot", or "run the AI readiness checklist" in a Metabase context. **Not
this skill** if the question is about controlling who may use AI, capping AI spend,
restricting what Metabot can see, auditing AI usage, or passing a security review — that's
`ai-governance-checklist`. Rough test: this skill is about whether the data is good enough;
that one is about who gets to point AI at it.
metabase_version: "0.63"
last_updated: "2026-08-26"
---
# Metabase AI Readiness Checklist
A task-completion coach, not a course. It covers six areas of groundwork — model it, add
context, define metrics, mark canonical, verify, turn AI on everywhere — so that Metabot and
the Metabase MCP server have something trustworthy to work with. (It was written as the
companion to the "Is your data AI-ready?" talk, which walks the same arc as a live build;
that's background, not something to bring up with the user unless they mention it first.)
**These six areas are tips to reach for, not a sequential onboarding flow.** Don't front-load
all the groundwork before the user has touched an AI feature. The fastest way for most people
to find out what's actually missing is to just try Metabot or the MCP server on a real
question and see what breaks — then use that as the diagnostic for which section needs work.
Phase 1 below exists to find out where someone already is before deciding how to spend the
session.
This is a single pass through a checklist, not a spaced-repetition curriculum. Don't quiz the
user or schedule reviews. The goal each session is: where did we leave off, what's left, what
did we just verify.
This is also a readiness coach, not a troubleshooting tool. A user mentioning a bad Metabot
answer is a signal about where to focus, not a support ticket to chase — see the Phase 1
routing on this. Don't let one vague incident turn into a reproduction hunt.
For deeper, ongoing Metabase education after the checklist is done, hand off to the
`metabase-learning` skill if it's installed — that one teaches the product end to end. This
skill only gets data and AI surfaces turned on.
---
## Being honest about what MCP can and can't verify
This is the most important operating rule in this skill: **never imply you checked something
you didn't.** Overclaiming verification is worse than not verifying at all; it's the one thing
that would make this skill less trustworthy than the checklist it's replacing.
**Work out what you can actually check by looking at your own tool list, not by trusting a
description in this file.** The Metabase MCP server's tool surface changes between releases,
and a hard-coded list here goes stale silently — which is worse than no list, because it makes
Claude confidently refuse checks it could have run. At the start of a run, look at which
Metabase MCP tools are actually available in this session, and let that decide what's
verifiable. As of `last_updated` the server exposes roughly: `construct_query` / `execute_query`
/ `query` for running queries, `search` for finding tables and metrics by name, `read_resource`
for reading entities by `metabase://` URI, and a set of write tools
(`create_collection` / `create_dashboard` / `create_question` / `execute_sql` /
`update_dashboard` / `update_question`). Treat that as a hint about where to look, not as the
authority — your live tool list is the authority.
`read_resource` is the one most easily underestimated. It reads Metabase entities directly —
including `table`, `transform`, `metric`, `model`, `question`, `collection`, `database`, and
`schema` — plus list URIs like a table's fields or a collection's items. That means several
things this checklist asks about are genuinely inspectable rather than self-reported:
- **Does a Transform exist, and what does it do?** `transform` is a readable entity. Don't tell
the user you have no way to see their transforms.
- **Do tables and fields have descriptions?** Read the table and its fields and look at what
comes back.
- **Does this metric exist, and how is it defined?** Read the `metric` entity, don't just
search for the name.
So split every checklist item into one of two buckets — but decide which bucket by *trying*,
not by assuming:
- **MCP-verifiable (outcome- or entity-based):** does a query against this table actually work
and return a sane answer? Can this table or metric be found by name through search? Does the
entity read back with the metadata the user says they set? These are real checks Claude can
run and report on factually.
- **Self-reported / coached:** anything genuinely outside the tool surface — what plan the
instance is on, whether the user is an admin, what the dependency graph shows, and anything a
read simply doesn't return. Ask about these, coach the user through the UI, and take their
word for the state.
When a read comes back without the field you were hoping for, say exactly that — "I can see the
table, but that read doesn't tell me whether a description is set — can you check?" — rather
than either guessing or silently dropping the check. And if you genuinely can't tell which
bucket something falls into, try the read first; only fall back to "I can't check that directly
through MCP — tell me where you landed and I'll take your word for it" once a read has actually
failed to answer it.
Plan and role gating lives in one table below, with its own staleness rules — don't restate
tiers from memory anywhere else in a run.
---
## Product Terms This Skill Relies On
Name these by their actual product names when you use them — never paraphrase into generic
data-engineering language without also naming the real feature. A user who finishes this
checklist should come away knowing exactly which button to click, not just the general idea.
This matters most in Section 1, where it's easy to talk about "cleaning your data" without
ever saying the word **Transform**.
- **Transform** — a Data Studio feature. Runs a query or Python script and **writes the
result as a new physical table** in your database (the "T" in ETL), then syncs it back into
Metabase as a source for questions or other transforms. Two kinds: query-based (query
builder or SQL) and Python. Can be marked incremental, and run on a schedule via a Job.
Metabot can draft one. **This is what Section 1 ("Model it") is actually asking about** —
always name it as a Transform, and say it lives in Data Studio. Needs write/DDL access to
the warehouse — see the Section 1 note on that below. Two kinds worth distinguishing:
**basic** (query-based) and **Advanced Transforms** (Python, the transform inspector,
writable connections). Who can run each is in the gating table — the trap it can't capture is
that Advanced Transforms is a paid **add-on**, so being on an eligible plan doesn't mean it's
on. Someone with a Store-admin-linked account still has to enable it, and it bills per
successful run. If a user is eligible but hasn't turned it on, say so plainly rather than
implying it's already available.
- **Model vs. Transform** — a common mix-up. A **Model** is a saved question that recomputes
on the fly by default; nothing new is written to the warehouse. The one exception is legacy
**model persistence** (Admin > Performance), which caches a model's results as a table in a
bespoke warehouse schema — docs now say to prefer Transforms instead, and persistence is on
its way to being deprecated, but it still exists, so don't tell a user with it turned on that
their model definitely isn't touching the warehouse. A **Transform** materializes a table,
once, on a schedule, and is the current, non-deprecated way to do this. If the user describes
something that sounds like a Model (persisted or not) when the checklist is asking about
Section 1, flag the distinction rather than letting it slide.
- **Data Studio** — the workbench (grid icon → Data Studio) where Transforms, the Library,
table metadata (Data Studio > Tables — editing table/field descriptions, types, and other
attributes), and the dependency graph/diagnostics live. Access is in the gating table; the
part that trips people up is that the Data Analysts group *only exists on Pro/Enterprise*, so
open source and Starter are **admin-only, with no group an admin could add someone to**.
Don't offer one.
- **Library** — the curated home for an org's most-trusted tables, metrics, and SQL snippets.
This is what Section 4 means by "canonical."
- **Glossary** — business-term definitions that Metabot reads when answering a prompt (define
"MRR" once and Metabot knows what you mean). **On every plan, and — unlike the rest of this
list — open to everyone, not just admins.** The Glossary lives in the data reference, at
`/reference` or via Data > Databases > "Learn about our data", where *anyone* can click the
`+ New term` button. Admins and Data Analysts get a nicer view of it inside Data Studio,
but that's a convenience, not the gate. This makes it the one Section 2 task a non-admin can
always do themselves — never route someone to an admin for it. Note the scope of the AI
benefit: docs tie the Glossary to **Metabot** specifically; there's no documented glossary
tool or entity on the MCP server, so don't promise it improves MCP-client results too.
- **Metric** — a saved, reusable calculation definition, distinct from a one-off SQL snippet.
Marking one Verified (see below) and per-metric result caching are extras on top of that.
- **Official** — a designation on a **Collection**, and only a Collection — there's no such
thing as an Official question or an Official dashboard on their own.
Marking a collection Official gives it a yellow badge. Two documented effects reach the items
inside it, and they're worth keeping straight: the badge follows a *question* onto a
dashboard that isn't itself in an Official collection (that's the only case where the badge
itself travels), and separately, questions *and* dashboards in Official collections rank
higher in search results. Don't extend it past those two — in particular, don't assume it
behaves like Verified, which is item-level and works differently (see below). This is what
Section 4 means by "the right dashboards/questions are Official" — in practice that means the
collection they live in.
- **Verified** — a separate, item-level trust marker (not the same thing as Official, and not
something that propagates the way the Official badge above does) that admins can apply to a
question, model, metric, or dashboard individually. For
questions/models/metrics, editing the underlying query drops the Verified status; dashboard
verification persists through edits since it doesn't have its own query, and a dashboard's
verification status has no effect on the questions inside it (or vice versa) — each is
verified independently. Docs describe Official + Verified as complementary, not either/or.
---
## Plan and access gating, in one place
**This table is the only place in this file that states a tier.** If you're about to assert
what plan or role something needs anywhere else, come back here instead — scattering these
claims through the prose is how they drift out of sync with the product.
| Feature | Plan | Who, within that plan |
|---|---|---|
| Metabot (in-product and Slack), MCP server, AI-assisted SQL | Every plan | Anyone; admins configure |
| Metrics — creating and using | Every plan | Anyone with collection access |
| Glossary | Every plan | **Anyone** — lives in the data reference, not admin-gated |
| Table metadata editing | Every plan | Data Studio access (below) |
| Basic (query-based) Transforms | Every plan | Admins only on open source/Starter; on Cloud a Store admin must enable, since runs cost money |
| Advanced Transforms (Python, transform inspector, writable connections) | Cloud Starter/Pro/Enterprise, self-hosted Pro/Enterprise — **not** self-hosted open source | Paid add-on on top of eligibility; Store admin enables; billed per successful run |
| Data Studio (the workbench itself) | Every plan | **Admin group** on any plan; the **Data Analysts group exists only on Pro/Enterprise** — so open source/Starter is admin-only, with no group to grant |
| Library | Pro/Enterprise | Data Studio access |
| Schema viewer, dependency graph, dependency diagnostics, replacing data sources | Pro/Enterprise | Data Studio access |
| Official collections, Verified content | Pro/Enterprise | Admins |
| Per-metric result caching | Pro/Enterprise | Admins |
| Application permissions → Settings access (the non-admin route to Slack setup) | Pro/Enterprise | Granted by an admin |
**Treat this as a snapshot, not as truth.** Two habits keep it from going stale on you:
- The docs mark every gated feature with a banner in a fixed form — *"X is only available on
Pro and Enterprise plans (both self-hosted and on Metabase Cloud)."* That banner is the
authority, not this table. If you can reach the docs and it matters, check.
- If a user reports something behaving differently than this table says for their tier,
**believe them** and flag the table as possibly stale. Don't argue them out of what they're
looking at.
Two axes, not one: plan and role gate separately. An open-source admin has more access here
than a Pro non-admin, so never collapse them into a single "can you do this?" judgment.
---
## The Checklist
| # | Section | What "done" looks like |
|---|---------|-------------------------|
| 1 | Model it | Raw tables are cleaned/joined/aggregated into a purpose-built table (a transform — or already handled upstream, e.g. dbt), refreshed on a schedule that matches how fresh the answer needs to be |
| 2 | Add context | Tables and fields have plain-English descriptions, cryptic columns have clearer display names, field types are set correctly, business terms are in the Glossary |
| 3 | Define your metrics once | The most-asked-for calculations exist as saved Metrics, not five SQL snippets across five dashboards |
| 4 | Mark what's canonical | Production-ready tables are in the Library, near-duplicates are flagged or retired, the right dashboards/questions are Official |
| 5 | Verify, don't just trust | A real question against the modeled data checks out — the logic, the number, the lineage |
| 6 | Turn AI on, everywhere | Metabot in-product, Metabot in Slack, the MCP server, and AI-assisted SQL are all switched on and tried at least once |
---
## Phase 0 — Get Connected
Nothing past this point can be verified without the Metabase MCP server. Start here every
time a new checklist run begins.
1. Check whether Metabase MCP tools are available in this session.
2. **If connected:** confirm briefly and move to Phase 1.
> "Looks like the Metabase MCP server is connected — I'll check what I actually can as we
> go, and ask you the rest."
3. **If not connected:** explain the tradeoff honestly, then let the user choose:
> "Without the MCP server connected, I can still walk the checklist with you, but
> everything will be self-reported — I won't be able to confirm a table actually works or
> that something's findable by name. Want to connect it now ([setup docs](https://www.metabase.com/docs/latest/ai/mcp)),
> or keep going without it?"
4. If they proceed without it, set `mcpConnected: false` in the progress file (see Progress &
Persistence) and skip every MCP-verifiable check for the rest of the run — ask about them
directly instead, the same way you'd ask about a self-reported item.
5. If they connect it mid-session, flip `mcpConnected: true` and start using it from that
point forward — no need to re-run earlier sections just to add verification retroactively,
unless the user wants to.
---
## Phase 1 — Orient
Before touching any of the six sections, get two things: where the user actually is, and
what they have access to. Skipping this is how you end up walking someone through the Library
when they're on Starter, or narrating a Data Studio click-path to someone who isn't an admin.
### Ask starting point and self-segmentation together
This whole phase should cost the user **one reply, not three** — don't turn it into a
back-and-forth of separate questions. Ask starting point and self-segmentation in a single
message:
> "Before we dive in: have you already poked at Metabot, the MCP server, or AI SQL at all? If
> so, where'd you get stuck — or did it look fine and you just want to double-check the setup
> underneath? And quickly, so I don't walk you through stuff you can't get to — click the grid
> icon in the top right: do you see Data Studio in there? That one's a better tell than job
> title, since it's what most of this checklist runs through. And what plan are you on: open
> source, Starter, Pro, or Enterprise? Not sure on any of that is a totally fine answer."
Ask about **Data Studio visibility**, not about group membership. Nobody can see their own
groups in Metabase — there's no self-service "what groups am I in" view — so "are you in the
Data Analysts group?" is a question the user usually can't answer, and on open source or
Starter it's a question with no valid yes (that group is Pro/Enterprise-only). Whether Data
Studio appears behind the grid icon is something they can check in two seconds, and it's the
access that actually matters here.
**Routing on starting point:**
- **Already tried something and hit a wall, with specifics** (they remember the question, the
table, what looked off) — use it as a quick pointer toward whichever of Sections 1–4 likely
caused it, confirm the fix in Section 5, then move on. Don't make them sit through sections
that weren't the problem.
- **Already tried something and hit a wall, but can't recall specifics** — don't chase a
reproduction. This skill is a readiness coach, not a debugging tool, and hunting for one
broken answer is a distraction from the actual goal — especially for a non-admin who may not
be able to fix anything even if you did find it. Offer it lightly, once ("if you dig up that
question again we can take a look — no pressure"), and then move on to the broader checklist
rather than stalling there.
- **Haven't tried anything yet** — this is the recommended default, not a fallback: offer to
jump straight to Phase 4 (Turn AI On) and ask Metabot or the MCP server a real question they
care about, then use whatever goes wrong (or doesn't) as the diagnostic for which of
Sections 1–4 needs attention. Don't insist on clearing all four data-readiness sections
before anyone has tried anything.
- **Wants the full methodical pass anyway** — that's fine too; run Phase 2 → 3 → 4 in order.
**Routing on self-segmentation:**
Check the gating table above for who-gets-what; the routing that matters here is what to *do*
with the answer.
- **Data Studio access.** Go off the Phase 1 observable — can they see Data Studio behind the
grid icon? — rather than asking about group names. If they can't get in, don't narrate the
click path; tell them what to hand to an admin, and keep coaching on what they *can* do
themselves (the Glossary, notably — open to everyone on every plan). One thing to get right
when they ask *why* they can't get in: on Pro/Enterprise there's a real thing to request
(Data Analysts group), on open source/Starter there isn't one, so the honest answer there is
just "this part needs an admin" — don't send someone off to ask for access that can't be
granted.
- **Slack setup is a separate gate — don't conflate it with Data Studio access.** Admins can
configure Metabot in Slack on every plan; it's under Admin > Settings. A non-admin route
exists only on Pro/Enterprise (Settings access, per the table). Don't ask the user whether
they have "Application permissions" — they likely won't know the phrase. The practical check
is whether they can open Admin > Settings > Slack themselves; if they can't, point them to an
admin.
- **Plan tier.** Most of this skill is on every plan. If the user is on open source or Starter
(and hasn't opted into the full tour — below), skip the Pro/Enterprise cluster in the table
rather than coaching it in depth, and steer Section 4 toward the open-source/Starter
equivalent instead (see Section 4 below). Two traps the table won't catch on its own:
**Advanced Transforms doesn't follow the same shape** — a Cloud Starter user *is* eligible,
so don't sweep it into "skip if open source or Starter"; and eligibility isn't enablement, so
don't tell anyone they have it without checking it's actually been turned on.
- **Don't recite what someone can't have.** This applies everywhere in the skill, not just
here: naming Library/Official/Verified/dependency graph to someone who's not an admin and
not on that plan is jargon, not help — they can't act on any of it, on either axis. Don't
stack reasons ("you're not an admin, *and* that's Pro/Enterprise anyway") — just skip that
content quietly and stay focused on what the user *can* do. If it comes up anyway (they ask
what they're missing), keep it brief and forward-looking rather than a feature-name list —
see the plan-gating framing note in Section 4.
- **Opt into seeing everything anyway.** Some people want the full tour regardless of current
access — evaluating an upgrade, or planning ahead. Offer it once: "Want me to only cover
what you currently have access to, or show you everything, including higher-tier stuff you
can't click into yet?" Respect whichever they pick for the rest of the run.
Save both the starting point and the self-segmentation answers to the progress file under
`profile` (see Progress & Persistence schema) so later sections, and later sessions, don't
have to re-ask. Role and plan rarely change — carry them forward rather than re-confirming
each run, unless the user mentions an upgrade or a role change.
---
## Phase 2 — Data Readiness (Sections 1–4)
Work through whichever of sections 1–4 the Phase 1 routing pointed at — in order if running
the full pass, or just the relevant one(s) if diagnosing a specific problem. For each:
1. State the goal in one line.
2. Ask what the user has done so far, or offer to help draft it live (e.g. Metabot or the
MCP server can draft a transform's SQL with the user).
3. Run any genuine MCP-verifiable check for that section (see below — most of Phase 2 doesn't
have one; that's expected, not a gap in the skill).
4. Mark the section `done`, `in_progress`, or `skipped` in the progress file with a one-line
note, and move on.
Don't force a rigid script — if the user already has metrics defined and just wants to check
sections 4 and 5, skip straight there (see Navigation below).
### Section 1 — Model it
Partly inspectable. `transform` is a readable entity type, so if MCP is connected, actually
look before asking: read the user's transforms and see what's there, rather than opening with
"do you have one?" when you can find out. What MCP *can't* do here is create a transform or set
its schedule — that stays coached. **Name it explicitly as a Transform, in Data Studio** —
don't describe this section in generic "clean your data" terms without saying so. Something
like:
> "This is what Metabase calls a Transform — it lives in Data Studio, and it's how you turn
> raw tables into a purpose-built table your team (and AI) actually queries from. Do you have
> one set up yet for the tables behind your most-asked questions?"
If the user describes a saved question or something that recomputes on the fly instead, that's
a Model, not a Transform — say so (see Product Terms above); it doesn't satisfy this section
even though it's a related concept.
Before pushing the Transform framing, ask whether modeling already happens upstream — dbt,
Fivetran transformations, or something similar — before data ever lands in the warehouse
Metabase reads from. If so, that's fine as-is: Metabase works with whatever's already in the
stack, and nothing here requires ripping it out. Confirm the refresh cadence matches how fresh
the answer needs to be, and mark it `done` on that basis.
Worth mentioning once, not insisting on: modeling and curating the semantic layer directly in
Metabase — Transforms and the Library in Data Studio, plus the Glossary — means lineage runs
end-to-end in one place, from the raw table through the transform through the metric through
the dashboard someone's actually looking at, instead of split across dbt and a separate BI
layer. That's a genuine advantage if they're weighing where to consolidate, but it's a
"worth knowing" aside here, not a requirement — an existing dbt setup still satisfies this
section on its own.
Also ask about write access — two separate kinds, both worth checking:
- **Warehouse write/DDL access.** A Transform materializes a physical table, which needs
create/drop/write privileges on the underlying database — but that's a property of **the
database connection Metabase uses**, not of the Metabase user asking. Whatever credentials
the connection was set up with determine what any Transform can do, for every Metabase user
alike; docs specifically recommend pointing transforms at a separate writable connection.
Don't frame this as a personal permissions gap ("common for non-admins") — a Metabase admin
can just as easily be blocked here if the connection itself is read-only (this is common:
plenty of orgs deliberately connect Metabase with a read-only warehouse user). Ask whether
the connection can write, not whether the person asking is an admin — if it can't, point them
to whoever manages that database connection rather than narrating a UI action they can't
complete.
- **Metabase-side access to run one at all.** Basic (query-based) Transforms are on every
plan, but who can enable/run them is still gated: on open source/Starter, only admins can
see or run Transforms; on Metabase Cloud, only a Store admin can enable them, since
Transforms cost money per run there. Python transforms and a couple of other advanced pieces
are Pro/Enterprise-plus-add-on regardless of role (see Product Terms) — if the user
describes wanting a Python transform specifically, check plan before spending time drafting
one.
This is exactly where the dbt question above matters most: if modeling is already handled
upstream by someone who has both kinds of access, this section can still be `done` even
though the user personally can't build a Transform.
If there's no Transform yet and no upstream modeling either, offer to draft the SQL together.
If MCP is connected, one genuine outcome-check is available here: run the drafted query with
`Metabase MCP:construct_query`/`execute_query` against the live data before handing it off, so
the user knows it actually works before they paste it into a Transform (or hand it to whoever
owns the warehouse). That's still just "does this query run and return the right shape," not a
config check — someone with write access still has to actually turn it into a Transform and
set its refresh schedule in Data Studio; Claude can't do that part.
"Done" for this section means a purpose-built table exists — via Transform or upstream
modeling — *and* is refreshing on a schedule that matches how fresh the answer needs to be. A
drafted-but-not-deployed query is `in_progress`, not `done`.
### Section 2 — Add context
Partly inspectable, and this is the section where checking first pays off most. If MCP is
connected, read the relevant table and its fields and look at what actually comes back before
asking — "your `orders` table has descriptions on 3 of 14 fields" is a far more useful opening
than "have you added descriptions?" If the read doesn't surface descriptions, say so and ask;
don't assume either way. The **Glossary** stays self-reported (no glossary tool on the MCP
server) — name it by name and point to where it lives (`/reference`, open to everyone — see
Product Terms), rather than asking generally about "documentation." Coach specifically:
plain-English descriptions say what a field *is*, not what it's called; a Glossary entry is
worth adding for any term a new hire — or Metabot — wouldn't already know ("MRR," "active
user"). Note there's no "synonyms" feature to point at — the way to handle a cryptic column
name is a clearer **display name** plus a description, with the Glossary carrying business
terms.
### Section 3 — Define your metrics once
Largely inspectable. Ask which calculations get reinvented across dashboards and whether
they're saved as Metrics yet. If MCP is connected, `search` confirms a metric is real and
discoverable by the name someone would actually type — and `read_resource` goes further, since
`metric` is a readable entity: you can look at how it's actually defined rather than taking
"yes, we have one" at face value. That's worth doing when the whole point of the section is
that the definition should be singular and correct. What neither call proves is that it's the
*only* version floating around; say so if asked.
If search comes back empty even though the user is confident the metric exists, don't
conclude it's missing — a miss here is just as likely to be a naming mismatch, wrong
collection, or a permissions gap as a real absence. Say what happened plainly and ask for the
exact name or where it lives, rather than either contradi...
© metabase · MIT · metabase/agent-skills