
See the biggest gaps by team
BETAValidated levels are not in the MCP yetTeams down the side, skills across the top, the three weakest spots first.
- For
- HR
- Routine
- Every quarter
- Setup
- Juno + 1 tool
- You approve
- every draft
What you get
Example dataMy Goals

Run my first quarterly business review
Completed 2 / 6 Steps
Leading business reviewsCoursePending PurchaseThe prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want to see where each team stands against the skills its roles need, with the three biggest gaps first. 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 teams and which skills 3. What counts as a gap (below the expected level, or no evidence at all) 4. Whether to add anything from outside Juno, and where Ask these in one message, then wait for my answers. For the source you name, check it is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. Pull levels and completions from Juno. If you can't read them here, I'll upload an export. Never guess anyone's level. Build a heatmap: teams down the side, skills across the top, the three weakest spots called out with a suggested next step. Show sample sizes and grey out cells too small to judge. If this assistant supports artifacts connected to Juno, build it as an interactive artifact that re-reads Juno each time I open it, and say so; otherwise build it static and show the date the data was read. Routine: after the first run, offer to repeat this every quarter. If this assistant can run scheduled tasks, set one up only after I approve it; if not, give me a one-line prompt I can re-run. Don't assign or notify anyone.
Your AI asks you
- Q1My role and the team I support
- Q2Which teams and which skills
- Q3What counts as a gap (below the expected level, or no evidence at all)
- Q4Whether to add anything from outside Juno, and where
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
Routine: Every quarter. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
Live viewLive view: when your assistant supports artifacts connected to Juno, the result is an interactive view that reads Juno again each time you open it.
What it connects
- JunoRequired
- HRISSCIM
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Map the skills each role needs
Competencies and expected levels per role, drafted from your job descriptions for you to approve.
BETAOnce, then yearly
Run a skills check-in, self and manager
Each person rates their level, their manager confirms, and the gaps appear by team.
BETATwice a year
Send a welcome path before day one
The new-hire record starts a short path: paperwork, a welcome video, the first-week plan.
HEvery new hire





















