Audit the academy: stale, missing, duplicated

I want an honest audit of our academy in Juno Journey: what’s stale, what’s missing and what’s duplicated.

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. Which audience matters most (customers, partners, employees)
2. What “stale” means for us (age, product version, low completion)
3. Whether we have a source of truth to compare against, and where
Ask these in one message, then wait for my answers.

In that same first message, also ask me my role and the team I support.

If we do, check it’s connected in this chat; if not, I’ll connect it or upload an export. Don’t guess what’s current. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno.

Read our academy pages and channels and the courses they point to. Give me a table: item, issue (stale, missing, duplicate, broken link), evidence, suggested fix, effort.

This is read-only: don’t edit, archive or unpublish anything. Offer to draft fixes for the top 3; after I approve, save them as drafts and don’t publish until I say so.

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.