Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Centralizes multi-agent file storage by routing all file operations through a designated File Master agent using SSH to a Synology NAS or any SSH-accessible...
Centralizes multi-agent file storage by routing all file operations through a designated File Master agent using SSH to a Synology NAS or any SSH-accessible...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Centralize file storage across your multi-agent team using a Synology NAS (or any SSH-accessible storage). One agent acts as File Master β all others route file requests through it.
Multi-agent setups generate files across multiple workspaces. Without centralized storage: Files get lost between agent sessions No backup strategy Agents duplicate work No single source of truth
Designate one agent as File Master. All file operations go through this agent via sessions_send. The File Master manages: SSH connection to NAS Folder structure per agent File storage and retrieval Cross-agent file sharing
ββββββββββββ sessions_send ββββββββββββββ SSH βββββββββββ β Agent A β βββββββββββββββββββΊ β FILE MASTER β βββββββββββΊ β NAS β β (Finance)β "store invoice.pdf" β (Tech Lead) β β β ββββββββββββ ββββββββββββββ βββββββββββ β ββββββββββββ sessions_send β SSH β Agent B β βββββββββββββββββββΊ β β (Sales) β "get sales report" βΌ ββββββββββββ βββββββββββββββ β _agents/ β β βββ agent-a/ β β βββ agent-b/ β β βββ agent-c/ β β βββ _shared/ β βββββββββββββββ
Synology NAS (any model) or any Linux server with SSH SSH access with key-based auth VPN or Tailnet (recommended) for secure remote access
SSH_HOST="user@your-nas-ip" # Create agent folders (customize agent names to match your team) ssh $SSH_HOST "mkdir -p ~/_agents/{coordinator,techops,finance,sales,marketing}" # Create shared folders ssh $SSH_HOST "mkdir -p ~/_shared/{config,templates}" # Create agent directory file ssh $SSH_HOST 'cat > ~/_shared/config/agent-directory.json << EOF { "agents": { "coordinator": { "role": "Coordinator", "path": "~/_agents/coordinator/" }, "techops": { "role": "File Master", "path": "~/_agents/techops/" }, "finance": { "role": "Finance", "path": "~/_agents/finance/" } }, "shared": "~/_shared/", "basePath": "~/" } EOF'
Add to your File Master agent's AGENTS.md: ## FILE MASTER β Incoming Requests When another agent sends a file request via sessions_send: ### Store a file: ssh USER@NAS-IP "mkdir -p ~/_agents/[agent]/[subfolder]/" # Copy/create file there ### Retrieve a file: ssh USER@NAS-IP "cat ~/_agents/[agent]/[file]" # Send content back to requesting agent ### Confirm back: sessions_send(sessionKey="agent:[requester]:main", message="Done! File at [path]")
Add to each agent's AGENTS.md: ## File Operations β File Master I do NOT access files directly. ALL file ops go through the File Master: sessions_send(sessionKey="agent:techops:main", message="Store: [details]") sessions_send(sessionKey="agent:techops:main", message="Retrieve: [path]")
~/ βββ _agents/ β βββ coordinator/ # Coordinator files β β βββ journal/ # Daily journals β β βββ tracking/ # Task tracking β βββ techops/ # Tech docs, scripts β β βββ scripts/ β β βββ configs/ β βββ finance/ # Finance β β βββ invoices/ β β βββ contracts/ β β βββ reports/ β βββ sales/ # Sales β β βββ leads/ β β βββ proposals/ β βββ [your-agent]/ # Per-agent storage βββ _shared/ β βββ config/ # Shared configs β β βββ agent-directory.json β βββ templates/ # Shared templates βββ _backups/ βββ memory/ # Memory file backups
# Connect via secure tunnel IP (e.g. WireGuard, ZeroTier, or similar) SSH_HOST="user@10.x.x.x" # Your VPN/Tailnet IP # Test connection ssh $SSH_HOST "echo 'NAS connected!'"
β SSH key-based auth (no passwords in configs) β VPN/Tailnet for encrypted tunnel (no port forwarding needed) β File Master pattern limits SSH access to one agent β Other agents never get SSH credentials β Never store SSH keys in agent SOUL.md or memory files
Security: Only one agent has NAS credentials Consistency: Single point of truth for file locations Audit trail: All file ops logged through one agent Simplicity: Other agents don't need to know SSH commands
Set up a cron job that backs up agent workspaces to NAS: // Cron job config { "schedule": { "kind": "cron", "expr": "0 3 * * *", "tz": "UTC" }, "payload": { "kind": "agentTurn", "message": "Backup all agent workspaces to NAS. For each agent: rsync workspace memory/ folder to NAS _agents/{agent}/memory-backup/. Report any failures." }, "sessionTarget": "isolated" }
# Backup specific agent rsync -avz ~/.openclaw/workspace-finance/memory/ user@nas-ip:~/_agents/finance/memory-backup/ # Backup all agents (customize list to your team) for agent in coordinator techops finance sales marketing; do rsync -avz ~/.openclaw/workspace-$agent/memory/ user@nas-ip:~/_agents/$agent/memory-backup/ done
SSH connection refused: β Check VPN/Tailnet status β is NAS online and connected? β Verify SSH service running on NAS (Synology: DSM β Control Panel β Terminal & SNMP) Permission denied: β SSH key not added: ssh-copy-id user@nas-ip β NAS home folder not enabled (Synology: DSM β User β Advanced β Enable home service) Slow transfers: β Use direct VPN connection (not relayed) β Consider compression: rsync -avz --compress
β Synology (any model with DSM 7+) β QNAP (QTS 5+) β TrueNAS / FreeNAS β Any Linux server with SSH access β Raspberry Pi with external storage
Removed all specific agent/setup references Generalized folder structure and examples Added backup strategy with cron
Initial release
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.