onboarding

Agent onboarding is automated by checking the current state, reading the onboarding protocol, and establishing identity, bot connectivity, and configuration. This ensures all required files and state initializations are created and validated before normal operations begin.

Agent setup requires creating IDENTITY.md, SOUL.md, GOALS.md, USER.md, GUARDRAILS.md, .env, and config.json. These files establish the agent's configuration, and a .onboarded flag is written to signal successful completion.

Telegram bot integration is handled during the onboarding process by configuring connectivity and setting up cron schedules. This ensures the bot is properly connected and scheduled tasks are initialized before the agent handles any operations.

If onboarding is interrupted, the skill detects the incomplete state and can be triggered again to resume. It validates the existence of required files, bot connections, and the .onboarded flag to prevent misconfigured agents and setup gaps.

Yes, the onboarding routine provides an optional removal step to free up context after the process is complete. Once identity, bot connection, and configuration are validated, you can safely remove the onboarding protocol.

Establishing identity and guardrails before handling tasks prevents misconfigured agents and setup gaps. It ensures the agent operates within defined boundaries and goals, validating required artifacts before normal operation begins.