
Map the skills each role needs
BETACompetencies and levels are not in the MCP yetCompetencies and expected levels per role, drafted from your job descriptions for you to approve.
- For
- HR
- Routine
- Once, then yearly
- Setup
- Juno + 1 tool
- You approve
- every draft
What you get
My 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 a clear skills map in Juno Journey: for each role, the competencies it needs and the expected level, so plans and reviews have a standard. 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 roles to start with (three is a good start) 3. Where job descriptions or a career framework live (upload, or tell me where) 4. How many levels we use, and what they mean Ask these in one message, then wait for my answers. For the place our job descriptions live, check it is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. Check Juno first for positions, competencies and levels that already exist, and build on them instead of starting over. Draft, for each role, 5 to 8 competencies with the expected level and one sentence on what it looks like in the work. Show me one role first; after I approve, prepare the rest as drafts. Routine: after the first run, offer to repeat this once a year, or when a role changes. 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. This is a draft for me and the role owners to approve. Don't publish or assign anything.
Your AI asks you
- Q1My role and the team I support
- Q2Which roles to start with (three is a good start)
- Q3Where job descriptions or a career framework live (upload, or tell me where)
- Q4How many levels we use, and what they mean
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: Once, then yearly. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- JunoRequired
- Google Drivevia your AI assistant
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

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
See the biggest gaps by team
Teams down the side, skills across the top, the three weakest spots first.
HBETALive viewEvery quarter
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





















