hermes-memory-migration

Restore Hermes memory and skills from a GitHub backup repository.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/shiftrepo/aws --skill hermes-memory-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-memory-migration
Source: https://github.com/shiftrepo/aws/tree/main/HermesAgent/skills/skills/devops/hermes-memory-migration
Command: npx skills add https://github.com/shiftrepo/aws --skill hermes-memory-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restores Hermes Agent memory and skills from a GitHub backup repository to onboard a new instance or recover lost knowledge.

Core Features & Use Cases

  • Import MEMORY.md, USER.md, and SKILL.md from HermesAgent backups to restore memories and skills.
  • Safely merge backup entries with the current knowledge base while preserving critical live data.
  • Validate repository structure and selectively restore only missing or outdated entries to minimize drift.

Quick Start

Clone the backup repository and run the memory-migration tool to restore HermesAgent memories and skills.

Frequently Asked Questions about hermes-memory-migration

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

FAQPage Schema
How do I restore Hermes agent memory and skills from a GitHub backup?

To restore Hermes memory and skills from a GitHub backup, clone the repository and run the memory-migration tool. It imports MEMORY.md, USER.md, and SKILL.md files to onboard new instances or recover lost knowledge safely.

Can I selectively restore missing or outdated Hermes memories from a backup repository?

Yes, you can selectively restore missing or outdated Hermes memories. The tool validates the repository structure and merges backup entries with the current knowledge base while preserving critical live data to minimize drift.

What do I need to migrate HermesAgent backups from GitHub?

Migrating HermesAgent backups requires a GitHub Personal Access Token (PAT), repository access, and a defined HermesAgent backup structure storing memories under HermesAgent/memories and skills under HermesAgent/skills.

How does the Hermes memory migration handle existing live data during restoration?

During Hermes memory restoration, the tool safely merges backup entries with the current knowledge base. It preserves critical live data and validates the repository structure to ensure safe, auditable restores without overwriting active records.

What is the best way to onboard a new Hermes instance with existing memory and skills?

The best way to onboard a new Hermes instance is restoring from a GitHub backup repository. This process imports existing MEMORY.md, USER.md, and SKILL.md files to seamlessly transfer knowledge and skills to the new deployment.

Are there limitations when restoring Hermes skills from a GitHub repository?

Restoring Hermes skills is limited to deployments using the specific HermesAgent backup structure, requiring skills to be located under HermesAgent/skills/skills/.../SKILL.md and memories under HermesAgent/memories for successful validation.