command-room-onboarding

Automate Command Room onboarding with idempotent JSON writes and four default dashboards.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill command-room-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-room-onboarding
Source: https://github.com/chaletteholdings/command-room-releases-2710/tree/main/command-room/skills/command-room-onboarding
Command: npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill command-room-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the end-to-end Command Room onboarding process, turning a fresh workspace into a living memory with configured dashboards and starter context.

Core Features & Use Cases

  • Orchestrates a first-install onboarding, including optional workspace-ingest, org-tree generation, and seed of memory substrates (entities.json, events.jsonl, aliases.json).
  • Installs four default Layer 1 dashboards to surface essentials like project status, commitments, and relationships.
  • Idempotent execution across re-runs and upgrades, enabling safe re-running without data loss.

Quick Start

Begin onboarding in a fresh workspace, optionally ingest an existing folder, and install the four default dashboards.

Frequently Asked Questions about command-room-onboarding

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

FAQPage Schema
How do I automate workspace onboarding and deploy default dashboards?

Automating workspace onboarding involves running an 8-step sequence that scans connectors, infers the org tree, seeds memory substrates, and deploys four default dashboards. You need a workspace root to start the process.

What is the process for ingesting an existing workspace into a fresh install?

Ingesting an existing workspace is an optional step during the onboarding sequence. The process scans your existing folder structure to seed the data substrate, populating entities, events, and aliases without data loss.

Can I safely re-run onboarding upgrades without losing my current data?

Yes, you can safely re-run onboarding upgrades. The process uses idempotent JSON writes with versioning, ensuring auditable onboarding that can be executed multiple times without overwriting or losing existing data.

Do I need a specific workspace root directory to start the onboarding sequence?

Yes, a workspace root is required to start the onboarding sequence. The 8-step process enforces this prerequisite to correctly infer the org tree and deploy the default Layer 1 dashboards.

What specific files and substrates are generated during automated onboarding?

Automated onboarding generates memory substrates including entities.json, events.jsonl, and aliases.json. These files seed the data substrate to create a living memory with configured dashboards.

Why does onboarding enforce an 8-step sequence instead of manual configuration?

The 8-step sequence ensures reliable, auditable onboarding by orchestrating tasks in order. It automates connector scanning, org-tree generation, and dashboard deployment, preventing configuration errors that manual setup causes.