Verified:GitHub

workspace-ingest

Ingest legacy workspace data into Command Room JSON substrates with backups.

Updated Aug 27, 2026

Search Tags:#onboarding #audit-logging #data-migration #workspace-ingest #shape-detection #json-substrates #undo-migration

Ready to run

npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill workspace-ingest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workspace-ingest
Source: https://github.com/chaletteholdings/command-room-releases-2710/tree/main/command-room/skills/workspace-ingest
Command: npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill workspace-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The workload of bringing legacy workspaces into the modern Command Room architecture is error-prone and manual. workspace-ingest automates shape detection, data substrate generation, file migration, and safe rollback to deliver a coherent, auditable workspace.

Core Features & Use Cases

Shape detection for v1.x, v2.x, custom-markdown, and generic fallbacks.
Copy-first backup and undo logging to safeguard originals.
Atomic writes of entities.json, events.jsonl, and aliases.json with idempotent behavior.
On-demand file migration into the workspace structure with conflict handling and queues.
Deep integration with onboarding flows (Phase 1-9) and post-ingest reporting.

Quick Start

Point workspace-ingest at the source folder to start ingesting into the new workspace structure.

Frequently Asked Questions about workspace-ingest

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

FAQPage Schema

How do I migrate legacy workspace data into structured JSON substrates?▼

Shape detection automatically identifies v1.x, v2.x, custom-markdown, and generic fallback formats during workspace ingestion. This phased detection mechanism parses source data and generates corresponding JSON substrates without manual configuration.

Can I safely rollback a data migration if something goes wrong?▼

Yes, you can safely rollback a data migration using undo logging. The process implements copy-first backup safeguards and strict safety checks, preserving original data integrity and enabling idempotent operations to prevent corruption.

What is the best way to handle file migration conflicts in a workspace?▼

The best way to handle file migration conflicts is through automated queuing and conflict handling. This ingestion approach processes file migrations into the workspace structure atomically, ensuring idempotent behavior and safe rollback if conflicts arise.

Does workspace ingestion support custom markdown shapes and generic data dumps?▼

Yes, workspace ingestion supports custom markdown shapes and generic data dumps. It applies phased shape detection to parse these formats, converting them into structured JSON data substrates like entities.json and aliases.json with atomic writes.

How do I generate audit logs during a workspace onboarding process?▼

You generate audit logs during workspace onboarding by running the ingestion process with built-in audit trail tracking. It integrates deeply with onboarding flows and produces post-ingest reports detailing the migration and shape detection phases.