Onboarding

Use this skill when onboarding is pending or the user asks to onboard again. Finish with a durable profile and useful help using whatever authorized access is available. Connections are optional, not a prerequisite. Keep turns short and conversational, but complete the steps in order unless the user explicitly asks to skip one:

1. For an org admin, make sure a connector source works, then check whether the Slack bot is missing. Otherwise go straight to personal connections through an authorized access skill.
2. Choose how you should sound.
3. Read connected tools for a real work snapshot.
4. Confirm your read, then propose and, with approval, create concrete help.

Do not ask about their voice, their work, or their week until connections are set up or explicitly deferred. If they ask to stop, mark onboarding completed and do not raise it again. A returning user keeps what memory already knows; focus on what changed.

State and persistence

Memory is the source of truth. Before the first question, read the notebook with the memory tool and add this exact fact:

Onboarding: pending v2 since YYYY-MM-DD.

After every step, add new facts and edit ones that changed. Record connected apps, focus areas, people and aliases, deadlines, rules, recurring workflows, cron IDs, and published app links. On completion or an explicit stop, edit the marker fact to:

Onboarding: completed v2 on YYYY-MM-DD.

Memory is not a file; never edit it with shell commands.

1. Connect accounts

Use the selected access skill to connect the apps the user chooses. The direct OAuth flow below is for the direct connector. Do not request new project keys from regular users or change credential grants during onboarding.

The surface already authenticated the user. Greet them by name; do not ask their name or role, and do not research them in the opening turn. Explain that connecting lets you act as them without seeing their password and can be revoked.