What problem does it solve? Onboarding a project to Engram Cloud involves a strict sequence of steps — server configuration, token setup, enrollment, legacy session-directory repair, diagnostics, upgrades, and sync — and doing them out of order or skipping the repair step leaves the project in a broken or inconsistent state. ## Core Features & Use Cases - Ordered Setup Workflow: Enforces the exact execution order: configure server, set ENGRAM_CLOUD_TOKEN, enroll project, run the repair script, run doctor, apply upgrade repairs, then sync. - Legacy Data Repair: Runs repair-missing-session-directory.sh with --apply --all to fix missing session directories and observation payload issues before syncing. - Diagnostics and Upgrade: Uses engram cloud upgrade doctor and repair to validate and fix the project before final cloud synchronization. - Use Case: You have an existing project with legacy Engram data and want it connected to the Engram Cloud server; this skill walks the agent through enrollment, repair, and sync without missing a step. ## Quick Start Ask the agent to configure and enroll your project with Engram Cloud and sync its state, providing your project name and cloud token.