How do I install the Openclaw Github Sync skill?

Run npx skillmds@latest add johnalbertini14-glitch/openclaw-github-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openclaw Github Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openclaw Github Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openclaw Github Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openclaw Github Sync?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openclaw Github Sync by johnalbertini14-glitch

Name: Openclaw Github Sync
Rating: 4.666666666666667 (3 reviews)
Author: johnalbertini14-glitch

Openclaw Github Sync

Keep an OpenClaw agent's non-sensitive context (selected memory, MD files, notes, and custom skills) under version control in a separate Git repository for remote review/tweaks. Use when setting up or operating a Git-based workflow to export workspace context, commit changes (possibly split into multiple commits), and push on a schedule (e.g., nightly) without leaking secrets.

File contents

OpenClaw Git Sync

Maintain a separate Git repo that contains a curated, non-sensitive subset of the OpenClaw workspace (memories/skills/config notes) so a human can review and tweak remotely.

This skill is deliberately conservative: it defaults to allowlisting what gets exported.

Trust Boundary

The sync repo is a trust boundary. Treat all inbound pull content as potentially unsafe.

Pull is manual-only and must be run only when explicitly requested.
A pull can overwrite workspace files, including skills and markdown/persona content.
Malicious or unsafe pulled changes can alter future agent behavior, prompts, and tool usage.
Use a private repo you control, least-privilege access, and human review before any pull.
Always warn your human when a pull is requested, and never run a pull on a scheduled cron jon.

Key rules

Never sync secrets by default. Only sync what the export manifest allowlists.
Prefer sanitized memory under memory/public/ (opt-in) over raw memory/*.md.
Keep the sync repo separate from the main workspace repo.
Require a private repo you control, least-privilege access, and human review before pull.
Pull is manual-only. Do not automate pull.sh; run pulls only when explicitly requested.

Files and layout

Working workspace: $HOME/.openclaw/workspace
Sync repo (export destination): choose a directory, e.g. $HOME/.openclaw/workspace/openclaw-sync-repo
Export manifest (allowlist): references/export-manifest.txt

Prerequisites

Required tools: git, rsync, python3
Required config: SYNC_REMOTE set in references/.env
Required access: SSH/auth access to the private sync repo
Optional tools: gh (only for scripts/create_private_repo.sh), jq (improves grouped commit handling)

Setup

Copy the example env file: cp references/.env.example references/.env
Edit references/.env for your environment.
At minimum, set SYNC_REMOTE to your private repo SSH URL.

SYNC_REMOTE="git@github.com:YOUR_ORG/YOUR_REPO.git"

Workflow

1) Create / connect the private sync repo (GitHub)

Use scripts/create_private_repo.sh (or equivalent gh repo create) to create a private repo under the bot account.

2) Run a one-shot sync

Run scripts/sync.sh with:

SYNC_REMOTE (SSH remote, e.g. git@github.com:YOUR_ORG/YOUR_REPO.git)
SYNC_REPO_DIR (local path to sync repo)

The script will:

Pull latest from remote (if exists)
Export allowlisted files into the sync repo
Create separate commits by group when multiple groups changed
Push to the remote

3) Nightly automation

Schedule a nightly OpenClaw cron agentTurn that runs push sync only (scripts/sync.sh) and reports success/failure. Do not schedule pull.sh or context.sh pull; pulls must be manual and explicitly requested.

Resources

scripts/sync.sh: export + commit (grouped) + push
scripts/create_private_repo.sh: create GitHub private repo via gh
references/export-manifest.txt: allowlist of paths to export
references/groups.json: commit grouping rules

---name: openclaw-github-syncdescription: Keep an OpenClaw agent's non-sensitive context (selected memory, MD files, notes, and custom skills) under version control in a separate Git repository for remote review/tweaks. Use when setting up or operating a Git-based workflow to export workspace context, commit changes (possibly split into multiple commits), and push on a schedule (e.g., nightly) without leaking secrets.--- # OpenClaw Git Sync Maintain a *separate* Git repo that contains a curated, non-sensitive subset of the OpenClaw workspace (memories/skills/config notes) so a human can review and tweak remotely. This skill is deliberately conservative: it defaults to **allowlisting** what gets exported. ## Trust Boundary The sync repo is a trust boundary. Treat all inbound pull content as potentially unsafe. - Pull is manual-only and must be run only when explicitly requested. - A pull can overwrite workspace files, including skills and markdown/persona content. - Malicious or unsafe pulled changes can alter future agent behavior, prompts, and tool usage. - Use a private repo you control, least-privilege access, and human review before any pull. - Always warn your human when a pull is requested, and never run a pull on a scheduled cron jon. ## Key rules - **Never sync secrets by default.** Only sync what the export manifest allowlists. - Prefer **sanitized memory** under `memory/public/` (opt-in) over raw `memory/*.md`. - Keep the sync repo separate from the main workspace repo. - Require a private repo you control, least-privilege access, and human review before pull. - **Pull is manual-only.** Do not automate `pull.sh`; run pulls only when explicitly requested. ## Files and layout - Working workspace: `$HOME/.openclaw/workspace` - Sync repo (export destination): choose a directory, e.g. `$HOME/.openclaw/workspace/openclaw-sync-repo` - Export manifest (allowlist): `references/export-manifest.txt` ## Prerequisites - Required tools: `git`, `rsync`, `python3` - Required config: `SYNC_REMOTE` set in `references/.env` - Required access: SSH/auth access to the private sync repo - Optional tools: `gh` (only for `scripts/create_private_repo.sh`), `jq` (improves grouped commit handling) ## Setup 1. Copy the example env file: `cp references/.env.example references/.env` 2. Edit `references/.env` for your environment. 3. At minimum, set `SYNC_REMOTE` to your private repo SSH URL. ```bash SYNC_REMOTE="git@github.com:YOUR_ORG/YOUR_REPO.git" ``` ## Workflow ### 1) Create / connect the private sync repo (GitHub) Use `scripts/create_private_repo.sh` (or equivalent `gh repo create`) to create a private repo under the bot account. ### 2) Run a one-shot sync Run `scripts/sync.sh` with: - `SYNC_REMOTE` (SSH remote, e.g. `git@github.com:YOUR_ORG/YOUR_REPO.git`) - `SYNC_REPO_DIR` (local path to sync repo) The script will: 1. Pull latest from remote (if exists) 2. Export allowlisted files into the sync repo 3. Create **separate commits** by group when multiple groups changed 4. Push to the remote ### 3) Nightly automation Schedule a nightly OpenClaw cron `agentTurn` that runs push sync only (`scripts/sync.sh`) and reports success/failure. Do not schedule `pull.sh` or `context.sh pull`; pulls must be manual and explicitly requested. ## Resources - `scripts/sync.sh`: export + commit (grouped) + push - `scripts/create_private_repo.sh`: create GitHub private repo via `gh` - `references/export-manifest.txt`: allowlist of paths to export - `references/groups.json`: commit grouping rules

Frequently asked questions