linux-windows-sync

Sync files from a WSL directory to a Windows Cyclone-SS repository using rsync.

1|Updated Feb 6, 2026

Search Tags:#devops #windows #repository sync #rsync #wsl #file lifecycle

Ready to run

npx skills add https://github.com/williamsforeal/Cyclone-SS --skill linux-windows-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: linux-windows-sync
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/global-skills/_deferred/linux-windows-sync
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill linux-windows-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reduce the friction of keeping files consistent between a WSL workspace and a Windows-side Cyclone-SS checkout, preventing missed updates and duplicate work.

Core Features & Use Cases

Rsync-based cross-environment synchronization: Mirrors a defined folder from WSL to the Windows repo using reliable file transfer semantics.
Lifecycle integration with related bridge skills: Designed to be used alongside an openclaw bridge so agent files follow the full lifecycle across environments.
Use Case: You modify agent assets or configuration inside WSL and need them to appear in the Windows Cyclone-SS repo so your Windows tools and workflows immediately see the changes.

Quick Start

Tell the AI: "Prepare the linux-windows-sync rsync plan for syncing /mnt/openclaw-micro-team/ into the Windows Cyclone-SS repo, and list the exact inputs and outputs required before writing the final SKILL.md."

Frequently Asked Questions about linux-windows-sync

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

FAQPage Schema

How do I sync files between a WSL directory and a Windows repository?▼

Syncing files between a WSL workspace and a Windows repository requires rsync-compatible rules with clearly specified source and destination paths. It mirrors a defined folder to prevent missed updates and duplicated manual copying in developer workflows.

What is rsync-based cross-environment synchronization for WSL and Windows?▼

Rsync-based cross-environment synchronization mirrors a defined folder from WSL to a Windows Cyclone-SS repository using reliable file transfer semantics. It ensures agent assets or configuration authored in WSL become available to Windows-side tooling.

How do I prepare an rsync plan for syncing my WSL workspace to a Windows checkout?▼

You prepare an rsync plan by specifying exact source and destination paths and documenting required inputs and outputs. The plan defines the rsync-compatible rules needed before writing the final synchronization configuration.

Does WSL to Windows file synchronization require any external dependencies?▼

WSL to Windows file synchronization requires rsync-compatible rules, clearly specified source and destination paths, and documented external dependency requirements. It does not rely on external dependencies beyond the standard rsync toolset.

When do I need to sync WSL repository files to Windows?▼

You need to sync WSL repository files to Windows when you modify agent assets or configuration inside WSL and need them to appear in the Windows Cyclone-SS repo so your Windows tools and workflows immediately see the changes.

Can I use this synchronization approach alongside an openclaw bridge?▼

Yes, this synchronization approach is designed to be used alongside an openclaw bridge so agent files follow the full file lifecycle across environments. It integrates lifecycle management with related bridge skills.