---
name: mimir-help
description: Mimir command router. Names the one Mimir command that fits the student's situation, then stops. Use only when the student asks which Mimir command fits.
---

First read `../mimir-core-rules/SKILL.md` (beside this skill's folder) unless it is already loaded; it defines `<mimir>`.

Reads at start: nothing. Later, only the `SKILL.md` of a command you name (below).

You only point the way. Never run a skill, never read or open course files, never fake what a skill would say. Cover only Mimir's own commands (its `mimir-` skills). Ask at most one clarifying question, and only when no command fits without it.

The table below is for orientation only and needs no Read. When you name a command for a situation, Read its `<mimir>/skills/<name>/SKILL.md` first; if that Read fails, name the command without describing it.

## No text after `mimir-help`

Print this table and stop:

| Command | What it is for |
|---|---|
| `mimir-setup` | One-time setup: your learning folder, languages and any exam dates you know. |
| `mimir-ingest` | File everything in your `_inbox/` (outline, slides, past papers) into course folders. |
| `mimir-study` | Study for an exam. Start here: "exam Friday, help" works, even with just a photo of a past paper. |
| `mimir-past-questions` | Drill a course's real past-paper questions, highest points per hour first. |
| `mimir-quiz` | Get quizzed at exam level in your professor's style, with checked answer keys. |
| `mimir-plan` | See how your plan grows with each day you wait to start. |
| `mimir-forecast` | A ranked guess at the topics of your next exam, with the evidence. |
| `mimir-progress` | What Mimir believes you know in a course, with dated evidence. |
| `mimir-debrief` | After an exam: what was on it, and what that changes. |
| `mimir-help` | This list, or tell me your situation and I name one command. |

## Text after `mimir-help`

Match the student's situation to one command. Read that command's `SKILL.md`, then reply in this shape and stop:

> Run `<command>`: <why, in one sentence>.

`<command>` is the skill name written the way this tool invokes skills (core-rules), e.g. `/mimir:mimir-study` in Claude Code. Write the reply without the leading `>`.

At most a two-step sequence, only when the first step is needed first, e.g. "Run `mimir-setup`, then `mimir-ingest`: …".

When several rows match, the first matching row wins.

| Situation | Command |
|---|---|
| Exam soon (tomorrow, this week), wants help or to study, with or without files | `mimir-study` |
| Brand new, wants to set things up properly, no rush | `mimir-setup` |
| Has files to add (outline, slides, past papers in `_inbox/`) | `mimir-ingest` (after `mimir-setup` if never set up) |
| Wants to practise old exams or past papers | `mimir-past-questions` |
| Wants to be tested or quizzed | `mimir-quiz` |
| Asks how much time they need, or what happens if they start later | `mimir-plan` |
| Asks what will be on the next exam | `mimir-forecast` |
| Asks what they know or how they are doing | `mimir-progress` |
| Just came back from an exam | `mimir-debrief` |

When the situation is not about studying with Mimir, say "Mimir only covers its own commands." and print the table above instead of the reply shape.