Skip to content

Recipes

A recipe is the shortest path from something you already have to a course your LMS can import. Each one is a single copy-paste prompt plus a single attachment — no terminal, no JSON, no file paths. You paste the prompt into your AI assistant (with OELTKit connected), attach the file, and let the conversation do the rest: it scaffolds the course, fixes its own validation findings, and hands you a .oeltcourse file (and, when you ask, the LMS package).

The conversation is the interface. You don’t pick “SCORM 1.2 or 2004?” — you say which LMS you use (or nothing, and get a safe default). Validation findings come back as plain-language fix offers, not error codes. Mastery thresholds, cmi5, and theming exist when you ask for them, never in the default flow.

Under the hood every recipe walks the same path:

  1. Start — scaffold a course with sensible defaults (targets SCORM 1.2 + web, default theme, sensible tracking).
  2. Build — turn your source material into pages and interactions.
  3. Check — validate; the assistant repairs anything the validator flags.
  4. Ship — export a .oeltcourse file you keep, and package a .zip for your LMS when you’re ready.