sync-workspaces

Sync local and remote workspaces with Motoko framework changes.

1|1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/joshuacook/motoko --skill sync-workspaces
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-workspaces
Source: https://github.com/joshuacook/motoko/tree/main/.claude/skills/sync-workspaces
Command: npx skills add https://github.com/joshuacook/motoko --skill sync-workspaces

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates syncing of local and remote workspaces with the Motoko framework, ensuring tachikoma skills, schemas, and configs stay aligned across environments.

Core Features & Use Cases

  • Targeted sync: Copy tachikoma skills from motoko to workspaces.
  • Remote workflow: Push and pull changes to/from VM workspaces.
  • Conflict guidance: Provide steps to resolve divergences.

Quick Start

Run sync-workspaces to copy skills and coordinate updates across local and remote workspaces, then verify consistency.

Frequently Asked Questions about sync-workspaces

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

FAQPage Schema
How do I sync Motoko workspace changes across local and remote environments?

Sync workspaces by copying tachikoma skills from your motoko framework into each workspace's .claude/skills directory, then committing and pushing changes via git. The Skill handles local paths like ~/working/* and remote paths like /opt/workspaces/josh/*, automatically coordinating updates across environments and reporting results.

Can I automate syncing Motoko framework updates to multiple workspaces?

Yes. Sync-workspaces automates copying tachikoma skill files to multiple local and remote workspaces, applying git commits and pushes in batch, and optionally updating MCP configs. It removes manual repetition when framework changes need distribution across your workspace fleet.

What happens when workspace sync detects conflicts between local and remote changes?

The Skill identifies divergences and provides conflict resolution steps in its final report. You receive explicit guidance on which files conflict and how to reconcile them before completing the sync across all workspaces.

Do I need git and gcloud configured before syncing workspaces?

Yes. Git is required for committing and pushing tachikoma skill updates locally; gcloud is required for remote synchronization to VM workspaces. Both must be authenticated and configured in your environment before running the sync.

How does workspace sync coordinate with remote VM environments?

After local sync completes, the Skill uses gcloud to push changes to remote VM workspaces at specified paths, ensuring tachikoma skills, schemas, and MCP configs stay aligned between your local machine and remote infrastructure.