一键在 Manus 中运行任何 Skill

agenter-collaboration

星标0

分支0

更新时间2026年4月30日 13:27

Coordinate in shared rooms without breaking role boundaries or repeating already-claimed ownership. Use this when multiple users or avatars share one room.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

jixoai

jixoai/agenter

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

agenter-collaboration

Use this skill when you are collaborating in a shared room such as a project room.

Quick start:

Read the latest room messages.
Identify who owns the missing fact or decision.
Use the exact room protocol or prefix required by that room.
If you already own the next artifact or contract, leave the room and do that private work next.
Return with one protocol-shaped room reply only when shared truth changed.
If a prior room message is invalid, send a corrected replacement.

Key laws:

Room messages are durable shared truth.
Stay inside your role boundary.
Keep a single source of truth for shared contracts and ownership.
Do not rewrite artifact ownership toward your own specialty when another role is the better fit.
Claim ownership once. Do not repost the same "I will handle X" after the room already knows.
Once ownership is clear, the next useful move is often workspace or terminal work, not another acknowledgement in the room.
Another participant's acknowledgement does not by itself mean you need to answer again.
Re-enter the room when shared truth actually changed: you need a narrow dependency, you must correct a shared fact, you are handing off an artifact or contract, or you are delivering the final result.
A room message that claims a local URL, API, or "ready" state is shared truth, not a plan. Do not post that claim until the exact promised URL or path already works now.
Private reminders are coordination hints, not shared truth; they usually mean some shared-room work is still unresolved.
If the room is waiting on a final protocol reply, terminal success alone is not enough; post the shared-room message before you consider the work finished.

References:

references/shared-room-protocols.md: room protocol usage, ownership boundaries, and correction patterns

同仓库更多 Skills

同仓库

develop-agenter

jixoai/agenter

Repo-specific development workflow for agenter. Use when implementing, reviewing, or archiving changes in this repository, especially for OpenSpec work, release tooling, Studio UI, Storybook DOM tests, viewport/browser walkthroughs, worktree discipline, or repo-level docs/spec updates.

2026-06-270

agenter-runtime

jixoai/agenter

Orient yourself inside the runtime shell. Use this first when you need to choose between root tools, shell CLI, and deeper skill docs.

2026-06-010

create-agenter-app

jixoai/agenter

Create or update Agenter app packages, including first-party repo apps under apps/* and community agenter-app-* packages with peerDependencies.agenter compatibility.

2026-06-010

note

jixoai/agenter

Record, query, and maintain avatar-private raw notes through NoteSystem. Use when durable activity evidence, user corrections, terminal habits, ShellAssistant continuity, references, tags, or rename-safe note facts should be captured without turning them into distilled memory.

2026-06-010

agenter-workspace

jixoai/agenter

Inspect mounted real paths and choose the correct absolute cwd. Use this when path authority is unclear.

2026-05-310

agenter-terminal

jixoai/agenter

Create and drive durable terminal sessions. Use this when work needs a long-lived or interactive process; killed-terminal recovery is an explicit forensic path.

2026-05-310

name	agenter-collaboration
description	Coordinate in shared rooms without breaking role boundaries or repeating already-claimed ownership. Use this when multiple users or avatars share one room.

agenter-collaboration

Use this skill when you are collaborating in a shared room such as a project room.

Quick start:

Read the latest room messages.
Identify who owns the missing fact or decision.
Use the exact room protocol or prefix required by that room.
If you already own the next artifact or contract, leave the room and do that private work next.
Return with one protocol-shaped room reply only when shared truth changed.
If a prior room message is invalid, send a corrected replacement.

Key laws:

Room messages are durable shared truth.
Stay inside your role boundary.
Keep a single source of truth for shared contracts and ownership.
Do not rewrite artifact ownership toward your own specialty when another role is the better fit.
Claim ownership once. Do not repost the same "I will handle X" after the room already knows.
Once ownership is clear, the next useful move is often workspace or terminal work, not another acknowledgement in the room.
Another participant's acknowledgement does not by itself mean you need to answer again.
Re-enter the room when shared truth actually changed: you need a narrow dependency, you must correct a shared fact, you are handing off an artifact or contract, or you are delivering the final result.
A room message that claims a local URL, API, or "ready" state is shared truth, not a plan. Do not post that claim until the exact promised URL or path already works now.
Private reminders are coordination hints, not shared truth; they usually mean some shared-room work is still unresolved.
If the room is waiting on a final protocol reply, terminal success alone is not enough; post the shared-room message before you consider the work finished.

References:

references/shared-room-protocols.md: room protocol usage, ownership boundaries, and correction patterns