skill-sync-workflow

Synchronize shared global skills across multiple gateways via Git.

12|3|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/baibairui/WoClaw --skill skill-sync-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-sync-workflow
Source: https://github.com/baibairui/WoClaw/tree/main/.codex-runtime/home/.codex/skills/skill-sync-workflow
Command: npx skills add https://github.com/baibairui/WoClaw --skill skill-sync-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow addresses the challenge of keeping shared global skills consistent across multiple gateway runtimes by centralizing them in a Git-backed registry and automating synchronized deployment.

Core Features & Use Cases

  • Centralized management of shared skills in a versioned registry.
  • Publish-ready synchronization to multiple gateway targets with dry-run support and per-gateway targeting.
  • Supports explicit path mappings and safe rollback in case of failures.

Quick Start

Install and configure the shared skill registry, then run the publish flow to deploy to the selected gateways.

Frequently Asked Questions about skill-sync-workflow

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

FAQPage Schema
How do I synchronize shared global skills across multiple gateways using Git?

You can synchronize shared global skills across multiple gateways by centralizing them in a Git-backed registry and executing an automated push-publish workflow with per-gateway targeting and dry-run support.

What is a Git-backed skill registry and when do I need it for workflow automation?

A Git-backed skill registry is a centralized, versioned repository for shared global skills. You need it when managing workflow automation across multiple gateway runtimes to ensure consistent deployment and synchronized updates.

Can I target specific gateways like opt-gateway or gateway-a during a skill publish?

Yes, the publish workflow supports per-gateway targeting, allowing you to selectively deploy shared global skills to specific environments such as opt-gateway, gateway-a, or gateway-a-codex-gateway.

How do I test a skill deployment safely without affecting the live gateways?

You can test skill deployment safely by using the workflow's dry-run capability. This allows you to validate path mappings and per-gateway targeting configurations before executing the actual synchronized publish.

Are gateway-private and agent-private local skills included in the synchronization workflow?

No, the synchronization workflow explicitly excludes gateway-private and agent-private local skills. It only coordinates and deploys shared global skills to maintain separation of private configurations.