skills.rest
netanel-abergel
netanel-abergelCOMMUNITY
Explore all skills by this author →
GitHub

git-backup

Back up OpenClaw workspace files to a GitHub repository.

5|1|Updated Apr 1, 2026
Search Tags:#automation#git#github#workspace#backup#cron#personal-access-token
One-click install
npx skills add https://github.com/netanel-abergel/pa-skills --skill git-backup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-backup
Source: https://github.com/netanel-abergel/pa-skills/tree/main/skills/git-backup
Command: npx skills add https://github.com/netanel-abergel/pa-skills --skill git-backup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a reproducible way to back up an OpenClaw agent workspace to a GitHub repository, ensuring important memory and configuration files are committed and stored off-host.

Core Features & Use Cases

  • Automatic token discovery: Searches git remotes, environment variables, credential files, and shell configs to locate a GitHub Personal Access Token or prompts the owner to provide one.
  • Repo initialization & push: Creates a GitHub repo via the API if missing, initializes git, configures remotes, commits the workspace, and pushes changes.
  • Scheduled and on-demand backups: Includes a recommended cron configuration for periodic silent backups and explicit guidance to exclude secrets via .gitignore.
  • Use Case: After updating MEMORY.md, SOUL.md, or installed skills, run this Skill to immediately persist those changes to a private GitHub repo for recovery and auditing.

Quick Start

Run the git-backup skill to push your OpenClaw workspace to your GitHub repository using a Personal Access Token with repo scope.

Frequently Asked Questions about git-backup

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

FAQPage Schema
How do I back up my agent workspace to a GitHub repository?▼

To back up an agent workspace to a GitHub repository, you need a Personal Access Token with repo permissions. The process initializes git, commits workspace files, and pushes changes to a remote repository for off-host storage and recovery.

What is needed to automate scheduled git backups for my workspace?▼

Automated scheduled git backups require a valid GitHub Personal Access Token, network access, and a cron configuration. You also need careful .gitignore rules to prevent committing secrets during periodic silent pushes.

Can I create a new GitHub repository automatically when pushing a workspace backup?▼

Yes, if a repository is missing, the backup process can automatically create a private GitHub repository via the API using your Personal Access Token, then configure remotes and push the committed workspace files.

How does the system find a GitHub Personal Access Token for backups?▼

The backup system discovers a GitHub Personal Access Token by searching git remotes, environment variables, credential files, and shell configs. If no token is found, it prompts the owner to provide one for repository access.

What limitations should I consider when committing workspace files to git?▼

When committing workspace files to git, you must configure .gitignore carefully to avoid pushing secrets. The backup also requires git and network access, relying on a valid Personal Access Token with appropriate repo scope.

Related Skills

Explore More Software Engineering Skills→
jleechanorgjleechanorg

github-auth

Configure GitHub authentication for Git and gh CLI via HTTPS tokens or SSH keys.

Official
Intermediate
haJ1thaJ1t

auto-changelog

Generate CHANGELOG.md from git commit history using Conventional Commits.

Community
Advanced
bolander72bolander72
2

vault-sync

Sync an OpenClaw workspace to a private Git repository with deterministic commits.

Community
Advanced
ramirlmramirlm

clawdbot-backup

Automate backup, restore, and synchronization of ClawdBot configurations.

Community
Intermediate