Maxxing Backup
Configure, run, check or restore the Harness Maxxing memory backup (private GitHub repository), explain what is saved and the secret scanner, and move an installation to a new server. Use when the user mentions backup, restore, losing the server, migration, or the backup check fails.
mkdir -p ~/.claude/skills/maxxing-backup && curl -fsSL 'https://raw.githubusercontent.com/makushingu/harness-maxxing/main/skills/maxxing-backup/SKILL.md' -o ~/.claude/skills/maxxing-backup/SKILL.md
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Maxxing Backup when an AI agent needs a reusable SKILL.md workflow for this job: Configure, run, check or restore the Harness Maxxing memory backup (private GitHub repository), explain what is saved and the secret scanner, and move an installation to a new server. Use when the user mentions backup, restore, losing the server, migration, or the backup check fails.
When not to use it
Skip Maxxing Backup when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/maxxing-backup && curl -fsSL 'https://raw.githubusercontent.com/makushingu/harness-maxxing/main/skills/maxxing-backup/SKILL.md' -o ~/.claude/skills/maxxing-backup/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/maxxing-backup/SKILL.md. For a shared project, commit the folder at .claude/skills/maxxing-backup/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Maxxing Backup skill for this task: Use Maxxing Backup when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptinferred
The skill text mentions ChatGPT or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Memory backup
The most valuable part of the installation is the knowledge in the workspace (CLAUDE.md, memory.md, notes, tasks, extensions, skills). The backup copies a **whitelist** of those files into a git working copy and pushes it to a **private** GitHub repository, daily (default 04:40, server time zone) and on demand.
## What is saved Whitelist (Settings -> Backup, `backup.include` in config.json), default: `**/CLAUDE.md`, `**/memory.md`, `**/NOTES.md`, `tasks.json`, `extensions/**`, `.claude/skills/**`. Never saved: secrets.json, keys, `.env`, credentials, session logs, attachments, project code. Before each commit a **secret scanner** looks for real secret formats (Anthropic/OpenAI keys, GitHub tokens, AWS keys, Slack tokens, private keys…); if one is found the backup **refuses to push** and reports the file: remove the secret (store it in Settings -> Keys) and run again. The push is also refused if the repository is (or became) public.
## Configure (UI wizard: Settings -> Backup) 1. On GitHub create a **fine-grained token**: Repository access = only the backup repo (or "All repositories" if the wizard must create it), permissions **Contents: Read and write**, **Metadata: Read** (+ **Administration: Read and write** only to let the wizard create the repo). 2. Settings -> Backup: repo `owner/name`, token, "create if missing" -> the server checks access and that the repo is private. 3. Run a first backup and check the commit on GitHub.
## Operate ```bash maxxing backup status # repo, private, schedule, last run (at, ok, commit, files, error) maxxing backup run # back up now maxxing doctor # "backup" check warns if the last success is older than 48 h ``` Schedule and whitelist: Settings -> Backup. History: Settings -> Backup -> history.
## Restore - Same server, files damaged: Settings -> Backup -> Restore (or `maxxing backup restore`). Current files are moved to the trash first; only whitelisted files are written. - A single older version of one file: the repo is plain git - browse it on GitHub (history of the file) and copy the content back.
## Move to a new server On the new server run the installer with the restore variables: ```bash curl --proto '=https' --tlsv1.2 -fsSL https://get.harness-maxxing.com | RESTORE_FROM=owner/name RESTORE_TOKEN=<token> bash # no key needed (LICENSE=HM-… for signed releases) ``` (or answer "yes" to the restore question). It installs, initialises an empty workspace, then restores the backup over it. Then: sign in with the new setup link, re-enter secrets that were not backed up (Claude token, Telegram bot token, Keys), re-link Telegram (a bot can only be polled by one server - stop the old one first), re-enable the backup.
## Troubleshooting | Error | Fix | |---|---| | 401 / 403 from GitHub | token expired or lacks Contents: write on that repo -> new token in Settings -> Backup | | repo is public | make it private on GitHub, then run again | | secret detected in `<file>` | remove it from the file (keep only the key name), run again | | non-fast-forward | the repo was edited elsewhere -> `maxxing backup run` again; ask before forcing anything |
Intended uses
- Use Maxxing Backup when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.