How do I install the File Sync skill?

Run npx skillmds@latest add agentscope-ai/file-sync-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is File Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with File Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is File Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published File Sync?

agentscope-ai (@agentscope-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

File Sync by agentscope-ai — Agent Skill

Name: File Sync
Author: agentscope-ai

File contents

File Sync (OpenHuman Worker)

Sync agent config files

When your coordinator notifies you that your config has been updated (e.g., skill update, model switch), pull the latest from MinIO:

mc mirror --overwrite "${AGENTTEAMS_STORAGE_PREFIX}/agents/${AGENTTEAMS_WORKER_NAME}/" /home/openhuman/.openhuman/agent-config/

Hot reload caveats:

OpenHuman Core reloads SOUL.md on the next message — no restart needed
Skill changes in /home/openhuman/.openhuman/skills/ are picked up on the next message as well
Changes that affect config.toml (Matrix channel, LLM provider) require a container restart — your coordinator handles this when needed

Automatic background sync:

Background sync runs every 60 seconds as a fallback
Most file changes are picked up without manual sync

Sync task / shared files

The shared/ directory is automatically mirrored from MinIO at startup and every sync cycle. No manual pull is needed.

Task and project files are at:

Local path (auto-synced)
`shared/tasks/{task-id}/`
`shared/projects/{project-id}/`

# Read the spec (already synced locally)
cat /home/openhuman/.openhuman/shared/tasks/{task-id}/spec.md

# Push your results back to MinIO (push is still manual)
bash /home/openhuman/.openhuman/skills/file-sync/scripts/push-shared.sh tasks/{task-id}/ --exclude "spec.md" --exclude "base/"

The push-shared.sh script automatically detects your team and pushes to the correct MinIO path.

When to use:

When you finish work: push results back to MinIO using push-shared.sh
When told files have been updated urgently: run the manual mc mirror command above

Always confirm to the sender after push completes.

Example workflow:

# Coordinator assigns task: "New task [st-01]. Please file-sync and read shared/tasks/st-01/spec.md"
# Pull latest (if needed)
mc mirror --overwrite "${AGENTTEAMS_STORAGE_PREFIX}/agents/${AGENTTEAMS_WORKER_NAME}/" /home/openhuman/.openhuman/agent-config/

# Read the spec
cat /home/openhuman/.openhuman/shared/tasks/st-01/spec.md

# ... do the work ...

# Push results
bash /home/openhuman/.openhuman/skills/file-sync/scripts/push-shared.sh tasks/st-01/ --exclude "spec.md" --exclude "base/"

# Confirm to coordinator
"Task complete. Results pushed to MinIO."

---name: file-sync-3description: Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).---# File Sync (OpenHuman Worker)## Sync agent config filesWhen your coordinator notifies you that your config has been updated (e.g., skill update, model switch), pull the latest from MinIO:```bashmc mirror --overwrite "${AGENTTEAMS_STORAGE_PREFIX}/agents/${AGENTTEAMS_WORKER_NAME}/" /home/openhuman/.openhuman/agent-config/```**Hot reload caveats:**- OpenHuman Core reloads `SOUL.md` on the next message — no restart needed- Skill changes in `/home/openhuman/.openhuman/skills/` are picked up on the next message as well- Changes that affect `config.toml` (Matrix channel, LLM provider) require a container restart — your coordinator handles this when needed**Automatic background sync:**- Background sync runs every 60 seconds as a fallback- Most file changes are picked up without manual sync## Sync task / shared filesThe `shared/` directory is automatically mirrored from MinIO at startup and every sync cycle. No manual pull is needed.Task and project files are at:| Local path (auto-synced) ||---|| `shared/tasks/{task-id}/` || `shared/projects/{project-id}/` |```bash# Read the spec (already synced locally)cat /home/openhuman/.openhuman/shared/tasks/{task-id}/spec.md# Push your results back to MinIO (push is still manual)bash /home/openhuman/.openhuman/skills/file-sync/scripts/push-shared.sh tasks/{task-id}/ --exclude "spec.md" --exclude "base/"```The `push-shared.sh` script automatically detects your team and pushes to the correct MinIO path.**When to use:**- When you finish work: push results back to MinIO using `push-shared.sh`- When told files have been updated urgently: run the manual mc mirror command aboveAlways confirm to the sender after push completes.**Example workflow:**```bash# Coordinator assigns task: "New task [st-01]. Please file-sync and read shared/tasks/st-01/spec.md"# Pull latest (if needed)mc mirror --overwrite "${AGENTTEAMS_STORAGE_PREFIX}/agents/${AGENTTEAMS_WORKER_NAME}/" /home/openhuman/.openhuman/agent-config/# Read the speccat /home/openhuman/.openhuman/shared/tasks/st-01/spec.md# ... do the work ...# Push resultsbash /home/openhuman/.openhuman/skills/file-sync/scripts/push-shared.sh tasks/st-01/ --exclude "spec.md" --exclude "base/"# Confirm to coordinator"Task complete. Results pushed to MinIO."```

Frequently asked questions

File Sync