hnh-backup

Back up Claude workspace configurations to a GitHub repository with sanitized credentials.

3|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/huynguyenh/skills --skill hnh-backup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hnh-backup
Source: https://github.com/huynguyenh/skills/tree/main/skills/hnh-backup
Command: npx skills add https://github.com/huynguyenh/skills --skill hnh-backup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents the loss of your valuable Claude workspace configurations, skills, and memory by securely backing them up to a GitHub repository, while automatically removing sensitive credentials and device-specific information.

Core Features & Use Cases

  • Automated Backup: Backs up essential Claude files including custom skills, global rules, and memory indexes.
  • Credential Sanitization: Automatically strips API tokens, secrets, and sensitive paths before committing to the repository.
  • Use Case: After a productive session, you can simply say "backup my Claude setup" to ensure all your custom configurations and work are safely stored and synchronized to your GitHub repository, ready for use on any machine.

Quick Start

Use the hnh-backup skill to back up your Claude workspace to GitHub.

Frequently Asked Questions about hnh-backup

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

FAQPage Schema
How do I back up Claude workspace configurations to GitHub?

Backing up Claude workspace configurations to GitHub involves verifying authentication, pulling the target repository, copying custom skills and global rules, then committing and pushing the sanitized files to keep your setup version-controlled.

Does backing up Claude skills to a repository expose API tokens?

Backing up Claude skills to a repository does not expose API tokens, because a Python-based sanitization script automatically strips secrets, email addresses, and device-specific paths before committing files to the remote repository.

What is the best way to synchronize Claude memory indexes across machines?

The best way to synchronize Claude memory indexes across machines is to push them to a GitHub repository. The backup process updates README.md and MEMORY.md indexes automatically during the commit, allowing easy access on any machine.

Do I need Python to automate Claude workspace backups?

Yes, you need Python installed, because the backup process relies on a Python-based sanitization script to remove sensitive credentials and device-specific paths before pushing your Claude workspace configurations to GitHub.

What limitations exist when sanitizing sensitive paths for GitHub backups?

A known limitation is that sanitization strictly removes API tokens, email addresses, and device-specific paths. You should review the committed files if your workspace contains unconventional sensitive formats that the sanitization script may not anticipate.