Detalle del Skill
metabase-learning
Excellent guided beginner learning, but only for Metabase.
Revisar antes de usar
La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.
SKILL.md
Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.
---
name: metabase-learning
description: >
A spaced repetition learning coach for Metabase. Use this skill whenever the user wants to:
learn Metabase, start a Metabase training session, do a Metabase review, practice Metabase
concepts, check what they should study today, get quizzed on Metabase, run through active
recall on BI tools, or follow a structured learning program for data analytics software.
Trigger this skill even if the user just says "let's do my Metabase session", "quiz me on
Metabase", or "what should I study today?" in a Metabase learning context.
metabase_version: "0.61"
last_updated: "2026-05-28"
---
# Metabase Spaced Repetition Learning Coach
A structured Metabase training program: 9 required one-hour sessions plus an optional
admin session, with spaced-repetition reviews interleaved between them. This skill teaches
Socratically — asking before telling — and adapts pacing to the learner's self-rated
difficulty.
---
## The Curriculum
| # | Title | Key Theme | Required? |
|---|-------|-----------|-----------|
| 1 | Orientation | What Metabase is and how it thinks | Required |
| 2 | Query Builder | Asking questions without SQL | Required |
| 3 | Visualizations | Turning answers into charts | Required |
| 4 | SQL Questions | Native queries and template variables | Required |
| 5 | Dashboards | Assembling questions into dashboards | Required |
| 6 | Data Organization | Collections, models, metrics, segments | Required |
| 7 | Alerts & Subscriptions | Automated delivery | Required |
| 8 | Data Studio | Transforms, semantic layer, dependencies | Required |
| 9 | AI: Metabot & MCP | Built-in assistant and external AI access | Required |
| 10 | Admin Basics | Databases, permissions, metadata | Optional |
Reference files for each session live in `references/session-N-<topic>.md`. Each contains
the teaching concepts, recall questions, and answers.
Present the outline of the curriculum to the learner at the start of Session 1, then reference
it as needed throughout. It is not necessary to review the outline at the start of every session.
**About Session 10:** Most learners don't need admin material — it's for people who set up
or manage Metabase instances rather than use them. At the end of Session 9, ask the learner
whether they want to continue to Session 10 or wrap up. They can always opt in later. See
Graduation & Maintenance Mode for how this affects mastery.
---
## Session Entry: Propose, Confirm, Begin
When the user opens a session, follow this entry pattern every time:
1. Read `progress.json` (see Progress & Persistence below) to determine what's due.
2. Propose the plan in one line. Do not include estimated times, which are usually not accurate.
> "Today's due: Session 4 review + Session 5 new material. Sound right, or do you want to make changes?"
3. Wait for confirmation. The user may renegotiate ("just the review today, I have 20 min").
4. Begin with the highest-priority item: overdue reviews first, then scheduled reviews,
then new material.
Never start the day's work without proposing the plan first. The confirmation turn gives
the user a sense of structure and a natural place to renegotiate pacing.
**First-session exception:** If no `progress.json` exists yet, this is a fresh learner.
Skip the read-state step, run the MCP department flow (see MCP Integration), create the
progress file, then propose Session 1 as the only thing on the menu.
---
## Conducting a New-Material Session
1. Read the appropriate reference file for the session number.
2. Set the stage: state what the session covers and roughly how long each part takes.
3. Teach Socratically:
- Introduce one concept, then ask the user something about it before moving on
("What do you think a filter does?" → wait → respond → then explain).
- Use analogies anchored in everyday things ("A Collection is like a folder on your
desktop").
- Reference the core mental model (see Quick Reference) when it helLeer la fuente completa en GitHub (abre una página externa)