Oclaw Hermes

OpenClaw × Hermes × DeerFlow 三位一体智能体桥接方案 - 实现 mflow 记忆流同步、智能体集群协作、深度研究链和专家蒸馏。让 OpenClaw、Hermes、DeerFlow 的边界，成为你能力的延伸。

This package appears to be a substantial bridge/orchestration project that will create local databases, write files under your home directory, and run Docker containers that connect to local and remote services. However, the registry metadata incorrectly claims no required environment variables or config paths while the SKILL.md, docker-compose.yml, and scripts clearly require multiple API keys and will persist memory data. Before installing: 1) do not supply high-privilege tokens (e.g., full cloud credentials); create least-privilege/test tokens instead; 2) review the .env.example and every script for endpoints and persistence locations (~/.openclaw, ~/.hermes, ~/.oclaw-hermes); 3) inspect the Docker images (nousresearch/hermes, bytedance/deerflow) you will pull—prefer pinned image digests and official images; 4) run in an isolated environment or VM first (to avoid leaking secrets or contaminating your real home config); 5) confirm the repository source and maintainership (the registry lists source unknown but SKILL.md references a GitHub repo); and 6) if you need this functionality, ask the author to correct the registry metadata (declare required env vars and config paths) and to provide a minimal test mode that doesn't auto-persist or auto-publish. The mismatches raise enough concern to pause installation until you verify secrets, image provenance, and the exact runtime behavior.

Type: OpenClaw Skill Name: oclaw-hermes Version: 3.0.0 The oclaw-hermes bundle is a comprehensive integration framework designed to bridge OpenClaw with the Hermes memory system and DeerFlow multi-agent orchestration. Its core functionality involves a 'Memory Flow' (mflow) engine that captures, categorizes, and synchronizes conversation history and 'expert' insights across platforms using local SQLite storage and configurable API endpoints. While the scripts utilize high-privilege capabilities such as file system access (writing to ~/.oclaw-hermes), network requests (syncing to local/remote services), and shell execution (checking service status via subprocess), these actions are transparently documented and strictly serve the stated purpose of the architecture. The presence of hardcoded Windows file paths in some scripts suggests a specific development environment rather than malicious intent.