What problem does it solve?
Coordinating files across Leaders, Workers, and requester channels in a multi-agent team is error-prone: agents may expose object storage internals, confuse Matrix room files with shared workspace paths, or publish deliverables to the wrong location. This Skill defines the conventions and tool usage for TeamHarness shared file operations.
Core Features & Use Cases
- Shared Path Conventions: Standardizes project files under
shared/projects/{project-id}/ and task specs, deliverables, and results under shared/tasks/{task-id}/, with clear Leader/Worker ownership boundaries.
- Filesync Operations: Provides explicit
list, pull, and push actions for synchronizing shared workspace state before reading or after writing.
- Artifact Publication: Uses
artifact publish_file to turn workspace files into Matrix room files, with support for target/roomId and parentEventId threading, while refusing sensitive paths by default.
- Use Case: A Worker finishes a task, writes outputs under
shared/tasks/{task-id}/, lists them as deliverables in taskflow submit_task, and the Leader later publishes shared/projects/{project-id}/result.md to the Matrix room for the requester.
Quick Start
Use the file-sharing skill to pull the shared state for task-001, write the deliverables under shared/tasks/task-001/, and publish the result file to the Matrix room.