mirror of https://git.openapi.site/https://github.com/desirecore/market.git synced 2026-09-05 23:43:58 +08:00

Files

Yige 2891f9dc06 feat(skills): 补全团队管理操作规范 (#92 )

## 中文

### 变更
- 将 manage-teams 升级到 1.3.0，并设置最低客户端版本 10.0.108
- 补齐 ManageTeam 全部 14 个 action 的用途、参数与风险边界
- 增加创建前检查、工作目录选择、Smart 成员路由、组织更新、头像、团队仓库、远程同步与失败恢复流程
- 明确远程操作必须经过 ManageTeam 的原因是供应链校验与审批，而不是假设 Agent 永远拿不到凭据
- 保持 disable-model-invocation: true，只在需要管理团队时按需加载

### 测试
- uv run --quiet scripts/i18n/test_validate_i18n.py
- uv run --quiet scripts/i18n/validate-i18n.py
- uv run --quiet scripts/i18n/translate.py --check
- git diff --check

## English

### Changes
- Upgrade manage-teams to 1.3.0 and require client 10.0.108
- Cover all 14 ManageTeam actions with their parameters and risk
boundaries
- Add preflight checks, workdir selection, Smart member routing,
organization updates, avatars, team repositories, remote
synchronization, and failure recovery
- Clarify that remote operations must use ManageTeam for supply-chain
validation and approval, not because Agents can never access credentials
- Keep disable-model-invocation: true so the Skill is loaded only when
team management is needed

### Tests
- uv run --quiet scripts/i18n/test_validate_i18n.py
- uv run --quiet scripts/i18n/validate-i18n.py
- uv run --quiet scripts/i18n/translate.py --check
- git diff --check

2026-08-25 18:32:03 +08:00

11 KiB

Raw Blame History

name, description, version, type, risk_level, status, disable-model-invocation, tags, metadata, market

name

description

version

type

risk_level

status

disable-model-invocation

manage-teams Skill

L0: One-line Summary

Use ManageTeam to inspect, create, and govern Agent teams, with the required checks before organizational changes or remote synchronization.

L1: When to Use

Use a team when:

multiple Agents need sustained collaboration around one task and a shared team workdir;
a stable supervisor, membership, or parent-child organizational structure is required;
a team repository must be published, installed, or synchronized.

Do not create a team when:

one expert is needed once: use Delegate(mode="sync" | "async");
several experts only need to provide one-off opinions: use Delegate(mode="fan-out");
the work is temporary file exploration: use a Worker instead of creating a lasting organization.

A team defines organization, shared directories, and governance. Actual work is still dispatched to members with Delegate.

L2: Execution Specification

1. Inspect Before Mutating

If teamId is unknown, call ManageTeam(action="list") first.
Before modifying, disbanding, or synchronizing a team, call ManageTeam(action="get", teamId=...) and verify its name, type, supervisor, members, local repository directory, and remote state.
Never guess a path under ~/.desirecore; use only the absolute repository path returned by get.
list can filter by parentTeamId. With tree=true, teamId selects the subtree root and parentTeamId is ignored.

2. Action Reference

action	Purpose	Key parameters and notes
`list`	List teams or an organization tree	`parentTeamId?`, `tree?`, `teamId?`
`get`	Inspect one team and its repository path	`teamId`
`create`	Create an ephemeral team	`name` or `task`; `supervisor?`, `members?`, `memberRouting?`, `parentTeamId?`, `workdirMode?`
`add_member`	Add one member	`teamId`, `agentId`
`add_members`	Add members in a batch	`teamId`, `members`
`remove_member`	Remove one member	`teamId`, `agentId`
`remove_members`	Remove members in a batch	`teamId`, `members`
`set_supervisor`	Replace the supervisor	`teamId`, `agentId`
`update`	Partially update team configuration	`teamId`; supports `name/type/isolation/parentTeamId/description/avatar/avatarImage`
`promote`	Promote an ephemeral team to persistent	`teamId`; one-way and never implicit
`disband`	Disband a team	`teamId`; explain impact and confirm unless explicitly requested
`fork_team`	Install a team from a remote repository	`url`; `name?`, `installMembers?`; enters approval
`push`	Push a local team to its connected remote	`teamId`; enters approval
`pull`	Pull and validate a team from its connected remote	`teamId`; enters approval

3. Create a Team

Before creation:

Every Agent in supervisor and members must already exist. Verify IDs with ManageAgent(action="list" | "get"); create or install a missing Agent through its corresponding Agent Skill before creating the team.
The DesireCore core Agent, desirecore, cannot be a supervisor. When the core Agent initiates creation, it must explicitly choose a regular Agent as supervisor.
Normally do not add desirecore as a member. Reach core capabilities through Delegate instead.
One Agent may supervise only one team. If the intended supervisor already leads another team, assign a successor there first.

Choose the workdir mode deliberately:

merged (default): the shared team directory is primary while member and global workdirs remain available;
team_only: exposes only the shared team directory, for high-reliability work where every member must operate on the same project. It does not delete member workdir configuration.

Use memberRouting to express routing intent without pinning a Provider or model:

{
  "supervisor-agent": {
    "tier": "flagship",
    "requiredCapabilities": ["reasoning"],
    "reasoning": "high"
  },
  "member-agent": {
    "tier": "balanced"
  }
}

keys must belong to the selected supervisor or members;
Agents using a fixed model must not appear in memberRouting;
omitted Smart members retain their current routing profile; the concrete Provider/model is resolved when that member executes work.

Example:

{
  "action": "create",
  "name": "Contract Review Project",
  "supervisor": "legal-lead",
  "members": ["contract-reviewer", "risk-analyst"],
  "task": "Review contracts continuously and consolidate risks",
  "workdirMode": "team_only"
}

4. Change Organization and Configuration

Prefer batch member actions to avoid observable intermediate states.
set_supervisor uses agentId; first verify that the Agent does not already supervise another team.
update is a patch: omitted fields remain unchanged.
parentTeamId: null detaches the team and makes it top-level; an empty string is invalid.
type only allows ephemeral → persistent. Repeating the current value is idempotent; use promote for an explicit upgrade.
isolation: soft uses shared session isolation; hard uses independent Agent copies.
description is the marketplace-facing team description, not the task supplied at creation.

Use a declared avatar with:

{
  "action": "update",
  "teamId": "team-id",
  "avatar": { "char": "CR", "color": "purple" }
}

For an image avatar, use avatarImage.source with dc-media://<mediaId>, a bare mediaId, or an image path inside the workdir. PNG/JPEG/WebP are supported. Do not pass an HTTP(S) URL or base64. Remove the image with { "remove": true }; remove and source are mutually exclusive.

5. Team Lifecycle

Disband an ephemeral team after its project is complete so the organization does not accumulate stale teams.
Use promote only for an explicit long-term collaboration requirement; promotion is one-way.
disband removes the team organization and repository. Execute directly when the user explicitly requested it; otherwise show the get result and confirm the intended target first.

6. Team Repository and Remote Synchronization

The team directory is a Git repository containing governance data such as team.json, member locks, and shared/rules.md.

For local Git work:

obtain the absolute repository path with get;
run status/log/diff/add/commit/tag with Bash in that directory;
after the local commit is complete, call ManageTeam(action="push").

Remote fork_team/push/pull must go through ManageTeam because it enforces team Schema validation, roster consistency, the core-Agent supervisor prohibition, workspace types, out-of-bounds symlink checks, and approval. Do not bypass those controls with raw git push/pull. This rule is not based on an assumption that Agents can never access credentials.

push/pull require a remote connected through the client. If none is configured, ask the user to connect or publish the team in team settings.
Locally created and forked teams do not inherit a directly pushable remote configuration by default.
fork_team defaults to installMembers=true; a same-ID local Agent that has diverged from its lock is protected and skipped rather than overwritten.
pull may replace local team configuration. Inspect local state first and identify the target remote in the approval card.

7. Dispatch and Finish

After team creation, dispatch work to the supervisor or members with Delegate:

one member: Delegate(target=..., mode="sync" | "async", teamId=...);
several members: Delegate(targets=[...], mode="fan-out", teamId=...);
prefer team members for sustained collaboration; a one-off outside opinion does not require membership.

Report the team name and ID, type, supervisor and members, workdir mode, organizational changes, and whether remote operations completed. Never expose credentials or a remote URL containing a token.

8. Failure Recovery

Agent does not exist: verify the ID; create or install the Agent, then retry.
Core Agent cannot supervise: explicitly choose a regular Agent as supervisor.
Supervisor already leads another team: run set_supervisor on the existing team before retrying.
Remote not configured: ask the user to connect a remote in client team settings; do not guess a hidden API.
Local content changed or conflicts exist: obtain the directory with get, inspect Git state, preserve user changes, and only then decide whether to commit, pull, or retry.
If this Skill is missing or disabled, the minimal operation may still be executed from the ManageTeam action/parameter Schema and tool error messages. Never bypass the tool by editing AgentFS directly.

11 KiB Raw Blame History