## 中文 - create-agent 2.6.1:最低客户端提高到 10.0.108(smartRouting + avatarImage) - update-agent 3.2.1:最低客户端提高到 10.0.108 - clone-agent 1.0.1:最低客户端提高到 10.0.115(补偿、fixed route 与 Provider ceiling) - action→Skill ID 映射仍不绑定版本 ### 验证 - i18n validator - translation freshness - public information boundary review ## English - create-agent 2.6.1 now requires client 10.0.108 for smartRouting and avatarImage - update-agent 3.2.1 now requires client 10.0.108 - clone-agent 1.0.1 now requires client 10.0.115 for compensation, fixed-route, and Provider-ceiling guarantees - The action-to-Skill-ID mapping remains versionless ### Verification - i18n validator - translation freshness - public information boundary review
5.8 KiB
name, description, version, type, risk_level, status, disable-model-invocation, tags, metadata, market
| name | description | version | type | risk_level | status | disable-model-invocation | tags | metadata | market | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| clone-agent | 完整克隆现有智能体为独立本地副本,并安全处理私有记忆、偏好、关系与团队分发影响。Use when 用户要求复制、克隆或基于现有 Agent 创建独立变体。 | 1.0.1 | meta | medium | enabled | true |
|
|
|
clone-agent Skill
L0: One-Sentence Summary
Clone an existing Agent into an independent local copy while explicitly handling private user data and team distribution impact.
L1: Overview
Use this skill when the user wants to copy an Agent or create an independent variant that keeps the source Agent's persona, principles, skills, and configuration. The clone receives a new ID and UUID. It is not an empty-template create operation and never creates a fork in GitHub, Gitee, or another code hosting account.
L2: Detailed Specification
Flow: decide whether cloning is appropriate → inspect the source Agent → confirm the clone name and private-data choices → call ManageAgent → report the clone's local and distribution properties.
1. Choose Clone or Create
- Use
clonewhen the user wants to retain an existing Agent's persona, rules, skills, and configuration in an independent copy or variant. - Use
create-agentwhen the user wants a new Agent in a similar domain but with independently designed behavior. - Do not recreate an Agent merely to make it “similar”;
createproduces a fresh template and does not inherit the source capability package.
2. Confirm the Source
If the user did not provide an exact ID, call ManageAgent(action='list'); use ManageAgent(action='get', id) when name, status, or description needs verification.
The tool rejects these cases and they must not be bypassed:
- The core
desirecoreAgent cannot be cloned. - An Agent whose routing was fixed by the human model selector cannot be cloned autonomously; ask the user to use the UI.
- The source Agent does not exist.
3. Name and Private User Data
nameis optional; the default is “Source Name (Copy)”.- Private user data is not copied by default. Pass
copyUserDataonly when the user explicitly asks the clone to inherit memory, preferences, or relationship state. copyUserData.memorycopies private memory between the user and the source Agent.copyUserData.preferencescopies user preferences for the source Agent.copyUserData.relationshipcopies the user-Agent relationship profile.
Before enabling any of these fields, explain the exact scope and obtain confirmation. Do not interpret “full clone” as consent to copy private user data.
4. Execute
Basic call:
{
"action": "clone",
"id": "source-agent-id",
"name": "New Copy Name"
}
When private-data copying was explicitly confirmed:
{
"action": "clone",
"id": "source-agent-id",
"name": "New Copy Name",
"copyUserData": {
"memory": true,
"preferences": false,
"relationship": false
}
}
ManageAgent performs a local-only copy, applies both caller and source Provider ceilings, registers the new Agent, and compensates by removing an incomplete clone if registration fails. Never use a git hosting fork, local HTTP API, or direct AgentFS directory copy instead.
5. Receipt and Team Impact
After success, report:
- The new Agent ID and that it is ready for Delegate / ManageTeam.
- Which private-data categories were actually copied; missing source categories are skipped, so trust the tool receipt rather than the request.
- The clone has
localorigin. Adding it to a team makes that teamdistributable=false. If the team must later be published or forked by others, use an Agent published to a remote repository instead.
On failure, follow the tool's exact result. If compensation cleanup also failed, preserve the evidence and clearly request human governance rather than retrying blindly.