claw-sync-all

Run the scheduled sync wrapper to repair OpenClaw mirror drift.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/Walliiee/agent-harness --skill claw-sync-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claw-sync-all
Source: https://github.com/Walliiee/agent-harness/tree/main/skills/claw-sync-all
Command: npx skills add https://github.com/Walliiee/agent-harness --skill claw-sync-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reliable, observable way to repair and maintain OpenClaw workspace, config, and state mirrors when they drift out of sync.

Core Features & Use Cases

  • Scheduled mirror sync: Runs the underlying sync workflow through a thin launchd or cron trigger so the task stays predictable.
  • Operational observability: Ensures sync work is executed via the shared skill wrapper for consistent logging and auditing.
  • Repair-oriented use case: Use it when mirrored workspace data, configuration, or state needs to be restored after drift or partial failure.

Quick Start

Ask the agent to run the claw-sync-all skill to repair the OpenClaw mirror sync state through the approved wrapper.

Frequently Asked Questions about claw-sync-all

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

FAQPage Schema
How do I repair OpenClaw workspace and config mirror drift?

To repair OpenClaw workspace and config mirror drift, run the scheduled sync wrapper through the claw-sync-all skill. This restores mirrored workspace data, configuration, and state after partial failure while maintaining consistent logging and auditing.

Can I use launchd or cron for scheduled mirror sync maintenance?

Yes, you can use launchd or cron for scheduled mirror sync maintenance. This skill runs the underlying sync workflow through a thin launchd or cron trigger to keep OpenClaw workspace, config, and state mirroring predictable and observable.

What is OpenClaw state mirroring and when does it need manual recovery?

OpenClaw state mirroring synchronizes workspace data and configuration across mirrored agent environments. It needs manual recovery when drift or partial failure occurs, requiring execution through the shared skill wrapper to preserve controlled sync scope.

Does OpenClaw sync require a shared skill wrapper for observability?

Yes, OpenClaw sync requires execution through the shared skill wrapper to preserve observability, auditability, and controlled sync scope. Bypassing the wrapper removes consistent logging and limits repair effectiveness for mirrored environments.

What are the limitations of manual sync recovery for mirrored agent environments?

The main limitation of manual sync recovery is that it must run through the approved shared skill wrapper to preserve observability and auditability. Without this controlled sync scope, OpenClaw mirror state repairs may lack consistent logging.