What problem does it solve? Managing the Mnemosyne memory provider in Hermes Agent involves non-obvious pitfalls: provider-injected tools that are not toolsets, profile databases that silently share storage, consolidation jobs that hang or corrupt recall ranking, and providers that vanish after runtime updates. This Skill provides the operational knowledge to install, configure, consolidate, and repair Mnemosyne correctly. ## Core Features & Use Cases - Installation & Repair: Verify provider status with hermes memory status, repair missing plugin symlinks, and re-verify after every Hermes runtime update. - Profile Isolation: Set explicit per-profile MNEMOSYNE_DATA_DIR paths so cloned or renamed profiles never write into a shared database. - Consolidation Management: Run safe manual or auto sleep cycles, choose the right LLM path (host LLM, remote API, or local GGUF), and avoid known ranking defects in version 3.14.0. - Use Case: After renaming a Hermes profile, recall stops working. The Skill guides you to rewrite the absolute MNEMOSYNE_DATA_DIR path in the profile's .env, restart the gateway, and verify with a write/recall smoke test. ## Quick Start Check whether Mnemosyne is installed and active by running hermes memory status, then follow the Skill's guidance to configure or repair the provider.