Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Security

ai-readiness-checklist

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 · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add metabase/agent-skills --skill ai-readiness-checklist

About this skill


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

Read the complete source ↗