skills.rest
YuryZZZ
YuryZZZCOMMUNITY
Explore all skills by this author →
GitHub

hmem-sync-setup

Configure cross-device hmem memory sync with AES-256-GCM encryption.

Updated Aug 23, 2026
Search Tags:#cross-device#encryption#setup#server-config#memory-sync#hmem
One-click install
npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-sync-setup-yuryzzz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hmem-sync-setup
Source: https://github.com/YuryZZZ/opencode-global/tree/main/skills/hmem-sync-setup
Command: npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-sync-setup-yuryzzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Set up cross-device memory synchronization for hmem across user devices. It enables encrypted, client-side memory sharing and seamless integration with MCP for automatic syncing.

Core Features & Use Cases

  • Secure client-side encryption (AES-256-GCM) for memory blobs before transmission.
  • Guided onboarding with interactive wizard using hmem-sync connect.
  • Supports first-device setup, additional-device restore, and MCP auto-sync configuration for multi-device workflows.

Quick Start

Run the interactive wizard with hmem-sync connect to securely link devices.

Frequently Asked Questions about hmem-sync-setup

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

FAQPage Schema
Can I restore memory sync when adding an additional device?▼

Memory sync uses client-side AES-256-GCM encryption to secure memory blobs before transmission, ensuring data remains protected during cross-device synchronization.

What encryption does hmem memory sync use for secure data transmission?▼

Memory sync uses client-side AES-256-GCM encryption to secure memory blobs before transmission, ensuring data remains protected during cross-device synchronization.

Does hmem memory sync support MCP auto-sync configuration?▼

Yes, the setup includes MCP auto-sync configuration to enable automatic syncing, providing seamless integration for multi-device memory workflows.

Do I need server configuration for first-device memory sync setup?▼

First-device setup requires configuring server URLs and authentication tokens through the interactive wizard to establish the initial memory synchronization endpoint.

What are the limitations of client-side encrypted memory sync?▼

The setup requires interactive configuration for each device and depends on proper server URL and token management to maintain continuous cross-device memory synchronization.

Related Skills

Explore More Software Engineering Skills→
taxbit-sharedtaxbit-shared

api

Integrate server-side applications with Taxbit REST API endpoints using Bearer token authentication.

Official
Intermediate
BumblebiberBumblebiber
23

hmem-sync-setup

Synchronize hmem memories across devices with zero-knowledge encryption via MCP.

Community
Advanced
bish-xbish-x
2

publish

Convert Markdown brain pages into password-protected HTML documents with AES-256-GCM encryption.

Community
Intermediate
AICodeLionAICodeLion
91

agent-pack-n-go

Clone an OpenClaw Agent across devices via SCP with encrypted transfer and deployment.

Community
Advanced