
Turn a SCORM package into a course anyone can edit
The content of a locked package, rebuilt as a native Juno course with its quiz.
- For
- L&D
- Routine
- When needed
- Setup
- Juno only
- You approve
- every draft
What you get
Example dataBefore
Security basics 2023
SCORM package
Updated March 4, 2024
After
Security basics 2026
Course
Updated September 28, 2026

Phishing in practice
Interactive lesson
Updated September 28, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want an old SCORM package rebuilt as a native course in Juno Journey, so anyone on the team can update it in the editor. Use the Juno Journey connector for anything in Juno. If it isn't connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. My role and the team I support 2. Which package 3. Who the course is for 4. Whether to keep its quiz as is, or rewrite it Ask these in one message, then wait for my answers. Open the package and extract its content: sections, text, images, questions. Tell me what you couldn't read. Propose the course outline from that content, without adding to it, and the quiz. After I approve, build the course and the quiz as drafts. The old package stays as it is until I decide to retire it. Don't publish, assign or notify anyone until I say so.
Your AI asks you
- Q1My role and the team I support
- Q2Which package
- Q3Who the course is for
- Q4Whether to keep its quiz as is, or rewrite it
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
What it connects
- JunoRequired
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Bring your Storyline and Rise courses into Juno
Imported once, then edited in plain words: same link, same assignments, every version kept.
Once
Change one fact in every SCORM package
A rename, a new logo, a changed rule: found and fixed across your library, one approval.
When it happens
Sort the library before you move it
Keep, merge, rebuild or retire: decided before the migration, not after.
Once






















