Glossary
65 terms from "Agent Mentor: from first request to export." Look them up when you get stuck; the first mention in the text carries a hover definition.
| Term | Definition | Source |
|---|---|---|
| folder of instruction files | What a skill physically is: a directory your coding agent reads when a request matches, so the same kind of request gets handled the same way every session. | Agent Mentor Skill package entrypoint (intent router) |
| coding agent | An AI assistant that directs its own steps and uses tools to do work — reading and writing files, running programs — rather than only answering questions. | Anthropic: Building Effective AI Agents |
| learning request | Any sentence that asks to learn something — "I want to learn X," "teach me X," "make me a course on X" — which is what activates the skill. | Agent Mentor Skill package entrypoint (intent router) |
| trigger phrase | A required magic wording — which this skill deliberately does not have; the product name exists so you can refer to it, not so you can summon it. | Course-generation workflow contract |
| clarifying questions | The one to three short questions the agent must ask before building when a request names only a topic. | Course-generation workflow contract |
| topic-only request | A request that names the subject and nothing else, which forces the question round because the course's difficulty cannot be set from a topic name. | Course-generation workflow contract |
| four short parts | Topic, starting point, gaps, and goal — the whole specification a course request needs to go straight to generation. | Course-generation workflow contract |
| your starting point | What you already know or use today, which is the input the agent needs to set a course's difficulty. | Course-generation workflow contract |
| goal names an action | The test a goal must pass: it states something you will do, on real material, so someone watching could say "done." | Course-generation workflow contract |
| learner profile | The per-course record of what you know and don't, built from your request, that keeps a named gap from being used as an assumption. | Learner model contract |
| prerequisite | Something a lesson is allowed to assume you already have — and which anything you flagged as unknown may never be. | Course-generation workflow contract |
| user space | The install boundary: the skill's tools go into a folder in your home directory, with no administrator password involved. | Course-generation workflow contract |
| /courses | The path the handed-back link must end in; that page is your local course list, while the bare domain is a product page. | Course-generation workflow contract |
| course reader | The local website that renders generated course files as readable, practice-ready pages, listening only on your own machine. | Course-generation workflow contract |
| local files | Where your reading progress and practice attempts are stored — next to the course on your disk, submitted nowhere. | Course-generation workflow contract |
| numbered footnotes | The citation markers on a lesson's factual claims that lead to the course's own source list. | Course authoring guide (course shape and quality gate) |
| per-course source list | The collected sources gathered for one course, which every footnote in its lessons resolves into. | Course authoring guide (course shape and quality gate) |
| interaction blocks | Short in-lesson checks — pick a judgment, order some steps — that grade themselves on the spot inside the reader. | Course authoring guide (course shape and quality gate) |
| completion criteria | The short checklist under an exercise, specific enough that you can decide pass or fail without a grader. | Course authoring guide (course shape and quality gate) |
| grader | The role nobody fills here: no server, author, or account judges your exercise — the criteria plus your agent are the whole apparatus. | Course authoring guide (course shape and quality gate) |
| explain the mechanism | The rule binding every wrong-answer message: it has to say what you missed and why, never just report that you were wrong. | Course authoring guide (course shape and quality gate) |
| copy-to-agent entry points | The reader's four exits, each scoped to a different kind of trouble, that carry your exact situation and lesson path back to your agent. | Reader drill-down design: three copy-to-agent entry points |
| stuck card | The course-page help card with one fill-in template per situation — stuck on a concept, an error, or an exercise. | When-stuck help card design |
| ask agent about this passage | The chip that appears when you select text in a lesson, copying that sentence word for word along with the lesson path. | Reader drill-down design: three copy-to-agent entry points |
| definition popover | The hover card on a glossary term inside a lesson, carrying a "have the agent teach this" action. | Reader drill-down design: three copy-to-agent entry points |
| go deeper on this lesson | The link at a lesson's end that copies the lesson path plus a deepening request to your agent. | Reader drill-down design: three copy-to-agent entry points |
| quiz me | The plain sentence that starts a review session; "what should I review today" works the same way. | Agent Mentor Skill package entrypoint (intent router) |
| review pool | The set of items a session can draw from: glossary terms of courses with a completed lesson, plus interaction blocks you have actually answered. | Review-course workflow contract |
| glossary of key terms | The per-course term list with sourced one-sentence definitions, which seeds both the review pool and the flashcard export. | Course authoring guide (course shape and quality gate) |
| local learning records | The files next to your course that store what you completed and answered, and that the agent reads to compute what is due. | Review-course workflow contract |
| Leitner system | The scheduling method behind review: items sit in boxes by how well you know them, and each box is revisited at a longer interval. | Wikipedia: Leitner system |
| five boxes with waiting times | The concrete schedule: boxes 1 through 5 with waits of 1, 3, 7, 14, and 30 days; an item is due once its box's wait has elapsed since you last answered it. | Review-course workflow contract |
| fast end | Box 1's neighborhood, where a missed item returns for frequent review regardless of how far it had advanced. | Wikipedia: Leitner system |
| previously missed | The ordering rule inside a session: items you got wrong before are asked first. | Review-course workflow contract |
| recall attempt | Explaining a term in your own words before the standard definition appears — the order that makes review work, never reversed. | Review-course workflow contract |
| variant follow-up | The second, differently framed question you get after missing an interaction block, aimed at the same mechanism. | Review-course workflow contract |
| I forgot | An answer recorded as wrong — deliberately, and with a non-judgmental tone, because the record is scheduling data. | Review-course workflow contract |
| ten items per session | The per-session cap that keeps a backlog from turning review into an hour-long ordeal. | Review-course workflow contract |
| zero-due | The branch where nothing is scheduled today: the agent says you are caught up and reports tomorrow's count instead of inventing questions. | Review-course workflow contract |
| closing report | The fixed session summary: how many items you reviewed, how many right, how many wrong, and how many come due tomorrow. | Review-course workflow contract |
| maintenance request | A plain sentence asking to change an existing course — fix outdated parts, simplify a lesson, add a lesson, health-check the library. | Maintain-course workflow contract |
| announcement sentence | The one-line statement of what will change, which the agent must produce before touching any file. | Maintain-course workflow contract |
| snapshot of the course | The automatic hidden backup taken before any file is edited, which is what makes a later "undo that" possible. | Maintain-course workflow contract |
| quality check | The mechanical script that verifies structure, citations, sources, and glossary before a course counts as delivered — and again after every edit. | Course authoring guide (course shape and quality gate) |
| quality never regresses | The maintenance rule that an edit failing the check gets fixed or rolled back, so a course cannot end up worse than before. | Maintain-course workflow contract |
| undo that | The sentence that restores the most recent snapshot, after which the quality check runs again. | Maintain-course workflow contract |
| review records | The stored review state for each item, tied to names inside the course rather than to positions or content. | Maintain-course workflow contract |
| orphaned records | Review records whose key no longer exists after a rename or deletion, so that slice of your schedule points at nothing. | Maintain-course workflow contract |
| block id | The identifier of an interaction block, and one of the three names a review record can be keyed to. | Maintain-course workflow contract |
| glossary term's exact text | The literal wording of a term, which serves as its review record's key — so rewording it is a rename, not a polish. | Maintain-course workflow contract |
| health-check my course library | The read-only scan across all your courses, reporting which pass the quality check, which have orphaned records, and which are clean. | Maintain-course workflow contract |
| extension lesson | A lesson grown from a deeper question and attached below its parent, used when a chat answer is not enough. | Maintain-course workflow contract |
| three extensions per lesson | The cap on how many extensions one parent lesson may carry; a fourth request is refused. | Maintain-course workflow contract |
| export this course | The unqualified export request, which produces both formats: the printable page and the card file. | Export-course workflow contract |
| printable page | The single self-contained HTML file holding the whole course, openable in a browser with the reader not running. | Export-course workflow contract |
| HTML file | The format of the printable page — a web page saved as a file, rather than a document format. | Export-course workflow contract |
| Save as PDF | The browser print-dialog option that turns the printable page into a PDF. | Export-course workflow contract |
| card file | The exported CSV of the course's glossary, shaped for import into a flashcard app. | Export-course workflow contract |
| plain table file | The everyday reading of CSV: rows and columns as text, which is why any flashcard app can take it. | Export-course workflow contract |
| Anki import | The path that turns the card file into a deck: File, then Import, pick the file, map the fields. | Export-course workflow contract |
| front and back fields | The two sides of a flashcard you assign during import — term on the front, definition on the back. | Export-course workflow contract |
| Anki deck | The imported result — a portable copy of the course's terms, useful exactly where your agent isn't: on your phone, offline. | Export-course workflow contract |
| exports folder | Where exported files land — a per-course folder next to your courses, whose exact path the agent reports. | Export-course workflow contract |
| stale | What an export becomes after you change the course: it is a snapshot of that moment and never updates itself. | Export-course workflow contract |
| re-export | The habit the snapshot rule creates: after every course edit, run the export again and replace the old copy. | Export-course workflow contract |