メニュー
Use for TeamHarness shared workspace paths, explicit filesync operations, and shared project/task artifact boundaries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
Use when TEAMS.md Communication Contract needs detailed routing: Channel / Room Selection Protocol, Requester Report Delivery Protocol, or Message Tool Protocol. It resolves current session vs Team Room vs assignment room vs requester reply_route vs external channel, and explains when to use the message MCP tool. Do not use it to choose Quick Task or Project Work, create rooms, delegate tasks, check results, or accept project state.
Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.
Use only after Project Work mode is selected, before TeamHarness projectflow calls, project DAG or Loop planning, ready-node resolution, iteration recording, project files, result acceptance, or project progress updates.
Use only after Project Work mode is selected, when a TeamHarness Leader delegates ready project nodes, writes task specs, checks Worker results, and routes completion or blocker messages.
Use when a TeamHarness Worker or remote member receives an assigned task, acknowledges it, executes it, submits a result, or reports blockers.
| name | teamharness-file-sharing |
| description | Use for TeamHarness shared workspace paths, explicit filesync operations, and shared project/task artifact boundaries. |
Use shared workspace paths in task specs and team messages.
Project files belong under shared/projects/{project-id}/. Task specs,
deliverables, and results belong under shared/tasks/{task-id}/.
Do not expose object storage internals in human-facing messages. Use TeamHarness filesync tools for explicit shared file operations.
Use these paths in task specs and team messages:
shared/projects/{project-id}/meta.json
shared/projects/{project-id}/plan.md
shared/projects/{project-id}/result.md
shared/tasks/{task-id}/meta.json
shared/tasks/{task-id}/spec.md
shared/tasks/{task-id}/workspace/
shared/tasks/{task-id}/result.md
The Leader owns project files and task specs. Workers own task workspaces, deliverables, and submitted results.
Use filesync when you need an explicit shared file operation.
List a concrete shared directory:
{
"action": "list",
"path": "shared/projects/demo-project-001"
}
Pull before reading remote shared state:
{
"action": "pull",
"path": "shared/tasks/task-001"
}
Push after writing project-level files:
{
"action": "push",
"path": "shared/projects/demo-project-001"
}
Do not ask humans or Workers to inspect storage bucket names, access keys, or
provider-specific prefixes. Use shared/... paths in all visible coordination.