grandamenium Onboarding
This skill runs on first boot or when explicitly triggered. It is the only thing you should do until it is complete.
Step 1: Check onboarding status
[[ -f "${CTX_ROOT}/state/${CTX_AGENT_NAME}/.onboarded" ]] && echo "ONBOARDED" || echo "NEEDS_ONBOARDING"
If already ONBOARDED, skip to normal session start. Do not re-run onboarding unless the user explicitly requests it.
Step 2: Read ONBOARDING.md
cat ONBOARDING.md
This file contains the full onboarding protocol for your specific agent role. Follow every step exactly. Do not improvise.
Step 3: What onboarding establishes
Onboarding must complete all of the following before you are considered functional:
| Item | File written |
|---|---|
| Your name, role, emoji, and identity | IDENTITY.md |
| Your behavior, autonomy rules, and mode | SOUL.md |
| Your current goals and focus | GOALS.md |
| User preferences and context | USER.md |
| Guardrails and patterns to avoid | GUARDRAILS.md |
| Telegram bot connected and tested | .env (BOT_TOKEN, CHAT_ID) |
| Crons configured and running | config.json |
| .onboarded flag written | $CTX_ROOT/state/$CTX_AGENT_NAME/.onboarded |
Step 4: Mark complete
When all steps in ONBOARDING.md are done:
mkdir -p "$CTX_ROOT/state/$CTX_AGENT_NAME"
touch "$CTX_ROOT/state/$CTX_AGENT_NAME/.onboarded"
Then notify the user via Telegram that you are online and ready.
If Onboarding Is Interrupted
If a session crash or restart interrupts onboarding mid-way:
- Check which steps completed (look at which files exist)
- Resume from the first incomplete step
- Do NOT restart from the beginning if some steps already completed
- Re-run
/onboardingif needed to trigger this skill again
Critical Rules
- Do NOT send a Telegram message claiming you are online until onboarding is complete
- Do NOT set up crons until IDENTITY.md and GOALS.md are written
- Do NOT start processing user requests until
.onboardedis written - The user is waiting — be efficient, but do not skip steps