teamharness-file-sharing

Manages shared workspace paths, filesync operations, and Matrix room file publication for TeamHarness.

5.5k|677|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill teamharness-file-sharing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teamharness-file-sharing
Source: https://github.com/agentscope-ai/HiClaw/tree/main/plugins/teamharness/skills/team/file-sharing
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill teamharness-file-sharing

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about teamharness-file-sharing

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

FAQPage Schema
How do I share task deliverables in TeamHarness?

Write deliverable files under shared/tasks/{task-id}/ and list them in the deliverables field of taskflow submit_task. Worker deliverables must not use shared/projects/... paths, which are reserved for Leader-owned project files.

How do I publish a workspace file to a Matrix room?

Use artifact publish_file with a workspace-relative path and an explicit Matrix room target or roomId. When publishing after sending a requester report message, pass the returned messageId as parentEventId to thread the file correctly.

What is the difference between shared paths and Matrix room files?

Shared paths under shared/... are durable collaboration state used by Leaders, Workers, and recovery flows. Matrix room files are UI-visible m.file events; the room Files panel only shows published files, not text mentioning a shared path.

Do DingTalk or Feishu requesters receive published room files?

No. Non-Matrix channels like DingTalk, Feishu, and WeChat do not receive artifact publish_file room files. For those requesters, mention the shared/... artifact paths and point them to the shared workspace or platform object-storage view.

When should I use filesync pull and push?

Use filesync pull before reading remote shared state, such as a task directory, and push after writing project-level files. The list action enumerates a concrete shared directory like shared/projects/demo-project-001.

Can I publish sensitive files with artifact publish_file?

No. TeamHarness refuses obvious sensitive paths and text content by default, and reports the outcome in publishedArtifacts. Paths must be workspace-relative, never absolute or escaping the workspace.