onboarding

Initialize analyst agent identity, goals, guardrails, and Telegram connectivity.

88|108|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/grandamenium/cortextos --skill onboarding-grandamenium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboarding
Source: https://github.com/grandamenium/cortextos/tree/main/templates/analyst/.claude/skills/onboarding
Command: npx skills add https://github.com/grandamenium/cortextos --skill onboarding-grandamenium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents an analyst agent from starting normal operations without completing required identity, goals, guardrails, and Telegram setup, reducing misconfiguration and inconsistent behavior.

Core Features & Use Cases

  • First-boot and resume-safe onboarding: Detects whether onboarding is needed, reads the full ONBOARDING.md protocol, and resumes without skipping already completed steps.
  • Writes the required operational files: Creates IDENTITY.md, SOUL.md, GOALS.md, USER.md, GUARDRAILS.md, config.json, and the .onboarded flag, ensuring the agent becomes fully functional.
  • Telegram and cron readiness: Ensures the Telegram bot connection is tested and crons are configured and running before the agent goes live.

Quick Start

In your agent session, run the command /onboarding to complete setup before any other work begins.

Frequently Asked Questions about onboarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an analyst agent for first boot?

Agent onboarding for first boot requires running the setup protocol to establish identity, goals, and guardrails. The process writes required operational files like IDENTITY.md and SOUL.md, and only creates the .onboarded flag after verifying Telegram connectivity.

Can I resume interrupted agent onboarding without restarting completed steps?

Yes, interrupted agent onboarding can be safely resumed. The setup process detects completed steps and continues from where it left off, ensuring no configuration is skipped while avoiding redundant file writes.

What files are required for agent identity setup and guardrails initialization?

Agent identity setup and guardrails initialization require writing IDENTITY.md, SOUL.md, GOALS.md, USER.md, GUARDRAILS.md, and config.json. These operational files define behavioral boundaries before the agent starts normal operations.

Does agent onboarding verify Telegram integration and cron configuration?

Yes, agent onboarding verifies Telegram integration by testing the bot connection and ensures crons are configured and running. This prevents the agent from going live without verified messaging connectivity and scheduled task readiness.

Why does my analyst agent not start normal operations without the .onboarded flag?

The .onboarded flag is created only after the full ONBOARDING.md protocol is followed to completion. This prevents misconfiguration and inconsistent behavior by ensuring the agent cannot bypass identity, guardrails, and Telegram setup.

When should I explicitly request re-onboarding for an analyst agent?

Explicitly request re-onboarding when you need to reset or re-establish agent identity, goals, guardrails, or Telegram connectivity. The onboarding process safely overwrites operational files and re-verifies the complete setup before allowing normal operations.