OpenClaw Spacesuit

A comprehensive OpenClaw workspace framework providing session protocols, memory system, git workflow, safety rules, priority triage, communication handoffs,...

Jonathan Tsai@jontsai

Install

openclaw skills install @jontsai/spacesuit

openclaw-spacesuit

A framework scaffold for OpenClaw workspaces.

Metadata

Field	Value
Name	`spacesuit`
Version	`0.4.0`
Author	jontsai
License	MIT
Category	framework
Tags	workspace, scaffold, conventions, memory, git-workflow

Description

The Spacesuit is a batteries-included framework layer for OpenClaw workspaces. It provides:

Session startup protocol — security-first file loading order
Memory system — daily logs + curated long-term memory with commit discipline
Git workflow — mandatory pre-commit checks, worktree conventions, parallel agent coordination
Safety rules — pre-action checklist, destructive-action guards, stand-down protocol
Priority system — P0–P5 triage for tasks and incidents
Cross-platform handoffs — structured context transfer between Slack/Discord/Telegram
Heartbeat framework — proactive periodic checks with state tracking
Decision logging — mandatory audit trail for architectural decisions
Meta-learning framework — expert-first research methodology (Dunning-Kruger aware)
Security baseline — secret transmission policy, prompt injection defense, data classification

Installation

bash

# First-time install (creates workspace files with markers)
bash scripts/install.sh --workspace /absolute/workspace

# Upgrade existing workspace (replaces only SPACESUIT sections)
bash scripts/upgrade.sh --workspace /absolute/workspace

Requires Bash 4+; default macOS Bash 3 is unsupported. Registry downloads may\nomit Makefiles, so use the explicit script commands above. Unmarked files remain\nuntouched unless --adopt-unmarked is deliberately selected after a dry run.\nSee release and rollback instructions.\n\n## How It Works

OpenClaw reads hardcoded filenames from the workspace root (AGENTS.md, SOUL.md, etc.). Since we can't change that loading behavior, Spacesuit uses section-based merging:

Framework content is wrapped in  /  markers
On upgrade, only the content between markers is replaced
Everything outside the markers (your customizations) is preserved

Files Managed

File	Base Content	User Content
`AGENTS.md`	Session protocol, memory, git, safety, priorities	Channel mappings, tool configs, personal rules
`SOUL.md`	Core personality scaffold	Personal vibe, human-specific tone
`TOOLS.md`	Tool organization guidance	Actual tool configs, credentials refs, API details
`HEARTBEAT.md`	Check framework & state tracking	Specific checks to run
`IDENTITY.md`	— (template only)	Name, avatar, personality
`USER.md`	— (template only)	All about your human
`MEMORY.md`	Long-term memory structure	Project notes, personal context
`SECURITY.md`	Full security baseline	Contact-specific alert channels
`Makefile`	— (template only)	Gateway management targets

Upgrade Path

bash

# See what would change
bash scripts/upgrade.sh --workspace /absolute/workspace --dry-run

# Apply upgrade
bash scripts/upgrade.sh --workspace /absolute/workspace

# Check version
cat version.txt