update-workspace

Update PhantomOS workspaces to newer releases while preserving operator data.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Largo2z9/phantomos --skill update-workspace-largo2z9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-workspace
Source: https://github.com/Largo2z9/phantomos/tree/main/.skills/skills/update-workspace
Command: npx skills add https://github.com/Largo2z9/phantomos --skill update-workspace-largo2z9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky PhantomOS workspace upgrades by applying release changes while preserving operator data, brand information, credentials, and learnings.

Core Features & Use Cases

  • Release Update Orchestration: Detects installed and target versions, builds update chains, and applies release manifests in order.
  • Safe Migration Handling: Identifies breaking schema changes, delegates migrations when required, and enforces backups, rollback paths, and validation checks.
  • Use Case: A PhantomOS operator can upgrade an existing workspace to a newer release while keeping brand assets, custom extensions, and operational context intact.

Quick Start

Ask the AI to update the PhantomOS workspace to the latest available version while preserving all operator data.

Frequently Asked Questions about update-workspace

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

FAQPage Schema
How do I upgrade a PhantomOS workspace without losing operator data and credentials?

To upgrade a PhantomOS workspace without losing operator data, the Skill detects installed and target versions, builds an update chain, and applies release manifests while preserving brands, credentials, and operational state.

How does workspace migration handle breaking schema changes during a version update?

Workspace migration handles breaking schema changes by identifying them, routing migrations when required, and enforcing backups with rollback paths to ensure data integrity during the version update.

Can I rollback a PhantomOS workspace upgrade if the release manifest fails validation?

Yes, you can rollback a PhantomOS workspace upgrade because the Skill enforces validation workflows and rollback support, ensuring failed updates safely revert the workspace to its previous state.

What is the best way to synchronize workspace templates during a PhantomOS release update?

The best way to synchronize workspace templates during a PhantomOS release update is through the Skill's orchestrated release manifest application, which applies version detection and template synchronization in sequence.

Does PhantomOS workspace versioning support preserving custom extensions and learnings across releases?

Yes, PhantomOS workspace versioning supports preserving custom extensions and learnings across releases by applying controlled file updates that explicitly protect operator state and operational context from being overwritten.

When should I not use an automated workspace update orchestration for my PhantomOS environment?

You should not use automated workspace update orchestration without first ensuring migration safeguards are in place, as breaking schema changes require delegated migrations and enforced backups to prevent data loss.