Make any SCORM package editable
The content of a locked package, rebuilt as a native Juno course with its quiz.
- For
- L&D
- Routine
- When needed
- Needs
- Juno only
- You approve
- every draft
What you get
Before
Security basics 2023
Security basics 2023
SCORM package
Updated Mar 4, 2024
After
Security basics 2026
Security basics 2026
Course
Updated Sep 28

Phishing in practice
Interactive lesson
Updated Sep 28
The prompt
Paste it into Claude or ChatGPT. It asks its questions in one message, then starts from what you already have in Juno.
Works in Claude, ChatGPT, and GitHub Copilot
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.
What your assistant will ask 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
How it runs
- 01
Connect
Juno and the tools below
- 02
Answer
its questions in one message
- 03
Check
the draft or the report it builds
- 04
Approve it
Nothing is published, assigned, or sent before that.
What it connects
- JunoRequired
Your assistant reads these tools and does the work in Juno.
Teams that use it
Journey Plays that go with it
Bring your Storyline and Rise courses into Juno
Imported once, edited in plain words; links, assignments, and versions stay.
OnceChange one fact in every SCORM package
A rename, logo, or rule change, fixed across your library with one approval.
When it happensSort the library before you move it
Decide what to keep, merge, rebuild, or retire before the migration.
Once



























