workspace-man

# Workspace Manager Use this skill to save a user's workspace state and optionally sync it with Netaverses. ## Use this skill for - Saving progress - Creating checkpoints - Backing up current work - Syncing work across devices - Cloud sync requests ## Do not use this skill for - Editing files - Reviewing code or content in detail - Advanced Git workflows (branches, rebase, conflict resolution) ## Agent rules - Speak in user terms: **save progress**, **checkpoint**, **backup**, **sync**. - Do **not** mention Git, commits, SSH keys, remotes, or ignore rules unless the user explicitly asks. - Prefer local safety first: saving locally is the default; cloud sync is optional. - If setup is missing, handle it for the user instead of asking them to initialize manually. - Always run the commands in the installed skill directory. - Always pass the user's project folder explicitly with `--workspace <path>`; never call this skill without `--workspace`. - If the workspace path is unclear, ask the user to confirm it before running any command. ## First-run setup - If the installed skill directory does not have dependencies yet (for example, `node_modules` is missing or `pnpm start` fails with install-related errors), run `pnpm install` in the installed skill directory once. ## Commands - `pnpm start init --workspace <path>` - Prepares the target workspace folder for this skill - Always works locally - If `NETA_TOKEN` exists, also prepares Netaverses cloud backup - `pnpm start save "<message>" --workspace <path>` - Creates a local checkpoint in the target workspace folder - `pnpm start sync --workspace <path>` - Syncs local and remote state for the target workspace folder - Use only when cloud sync is configured or the user explicitly asks to sync ## Routing guidance Before running any command: 1. Resolve the user's intended project folder. 2. Pass that folder as `--workspace <path>`. 3. If the path is ambiguous, ask a clarification question instead of guessing. Intent mapping: - "Save my work" / "Back this up" / "Create a checkpoint" → `pnpm start save "<summary>" --workspace <path>` - "Sync to the cloud" / "Get my latest work here" / "Sync across devices" → `pnpm start sync --workspace <path>` - If saving fails because the folder is not prepared yet, run `pnpm start init --workspace <path>` first, then retry `save` ## Response guidance - If the user does not provide a save message, write a short, human-readable summary. - If cloud setup is missing or sync fails, explain that the latest work is still saved locally and cloud sync can be done later. - Keep responses short and non-technical.