メニュー
Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/agentscope-ai/AgentTeams --skill teamharness-organizationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when a Leader maintains durable TeamHarness project state for Quick Task or Project Work: create_quick_project, create_project, plan_dag, plan_loop, ready_nodes, resolve_project, accept_task_result, project completion, and requester report state. Do not use to create Matrix task rooms or send messages.
Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use agentteams-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.
Use for standalone Matrix admin requests (register users, create rooms, manage membership, upload files). Also use when you need to send a file to the admin via Matrix media upload. Do NOT use for Worker/project creation — those handle Matrix operations internally.
SOC 職業分類に基づく
SKILL.md を表示中
| name | teamharness-organization |
| description | Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work. |
Use this skill to reason about team roles and responsibility boundaries.
Leader owns planning, delegation, acceptance, and requester reporting. Workers own assigned task execution. Remote members participate as invited local agents or humans. Manager owns control-plane operations.
Do not let a Worker silently become project owner. Do not let a remote member act like a controller-managed Worker unless the team explicitly models that role.
Leader owns:
Worker owns:
shared/tasks/{task-id}/spec.mdshared/tasks/{task-id}/result.mdRemote member owns only the work explicitly assigned to that member. Treat remote members as participants, not controller-managed runtime resources.
Manager owns control-plane operations such as creating workers, changing model configuration, deploying teams, and managing runtime state. TeamHarness skills must not instruct agents to call control-plane APIs.
Never write secrets, credentials, tokens, authorization headers, or live runtime
state into TEAMS.md, project files, task specs, task results, or Matrix
messages. If a task needs credentialed access, refer only to the approved
credential name or environment variable name, not its value.