desirecore/market
2
0
Fork 0
mirror of https://git.openapi.site/https://github.com/desirecore/market.git synced 2026-07-23 05:43:48 +08:00
Code Issues Packages Projects Releases Wiki Activity

perf(skills): 智能体 CRUD 四技能提示词改写压缩（功能不变，~65%） (#56)

Browse Source 
## 摘要 / Summary

### 中文

四个智能体管理技能（create/update/delete/discover-agent）改用 `ManageAgent`
内置工具后，正文与工具契约大量重叠——ManageAgent 的 description + params 已**常驻每次 query
的上下文**，声明了五个 action 语义、参数约束、权限硬边界、错误语义、字段级合并、确认行为、list/get
返回格式；技能正文里再复述即冗余。本次对四技能做**强改写·语境融合**压缩：

- 与工具契约重复的说明（参数/权限/错误码/确认行为/成功返回话术）**改写融入对应流程步骤**（如错误处理表 → 阶段一句、确认行为 →
阶段一句），不再照抄、不再表格化。
- 装饰性 ASCII 流程框图 → 一行文字流程；update 内部两张重复更新表 → 合并；YAML
元数据块（diff_metadata/context_handoff）融入流程；冗长示例（create 三份 JSON、update 附录 4
示例、discover ASCII 卡片）就地精简为代表示意。
- **不外置 references、不净删除任何内容**：所有决策/领域/交互意图完整保留——领域匹配表、persona/principles
的 L0/L1/L2 生成规范、update 两路径分流与字段级合并 vs 整体替换、防幻觉改名、回滚流程、discover
需求维度与无匹配衔接 create 等核心一字未丢。

zh 正文合计 **26542 → 9196 字符（降 ~65%）**；中英双份同步改写、逐段对齐，重算 i18n
source_hash（validate-i18n 通过）。版本 create 2.5.1 / update 3.1.2 / delete
2.5.1 / discover 2.6.1，manifest 1.2.12。

### English

After the four agent-management skills adopted the `ManageAgent` builtin
tool, their bodies heavily duplicated the tool contract — ManageAgent's
description + params are **resident in every query's context** (action
semantics, param constraints, permission hard-boundaries, error
semantics, field-level merge, confirmation behavior, list/get return
formats). This PR compresses all four via **aggressive rewrite +
contextual fusion**: contract-duplicating text is rewritten into the
relevant flow steps (not copied, not tabularized), decorative ASCII flow
boxes become one-line text, update's two duplicate tables are merged,
YAML metadata blocks are folded in, and long examples are trimmed in
place to representative sketches. **No references externalization, no
net deletion** — every decision/domain/interaction intent is preserved
(domain matching table, persona/principles L0/L1/L2 generation spec,
update's two-path split and field-level-merge-vs-full-replace,
anti-hallucination rename, rollback flow, discover's need dimensions and
create hand-off). zh bodies total **26542 → 9196 chars (~65% down)**;
both locales rewritten and aligned, i18n source hashes recomputed
(validate-i18n passes). Versions bumped, manifest 1.2.12.
This commit is contained in:
yi-ge
2026-07-19 15:16:43 +08:00
committed by GitHub
parent 64d295a489
commit d52e61e041
13 changed files with 302 additions and 1804 deletions
Download Patch File Download Diff File Expand all files Collapse all files

191
skills/delete-agent/SKILL.md
View File

@@ -1,7 +1,7 @@
---
name: delete-agent
description: 安全删除指定的智能体及其关联数据。删除前会验证智能体状态，支持可选地删除所有会话历史。Use when 用户需要删除不再使用的智能体。
version: 2.5.0
version: 2.5.1
type: meta
risk_level: high
status: enabled
@@ -12,7 +12,7 @@ tags:
- meta
metadata:
author: desirecore
updated_at: '2026-07-18'
updated_at: '2026-07-19'
i18n:
default_locale: en-US
source_locale: zh-CN
@@ -24,16 +24,16 @@ metadata:
short_desc: 安全删除智能体及其关联数据，支持多重确认与可选历史清理
description: 安全删除指定的智能体及其关联数据。删除前会验证智能体状态，支持可选地删除所有会话历史。Use when 用户需要删除不再使用的智能体。
body: ./SKILL.zh-CN.md
source_hash: sha256:6b971559e1d4ccc0
source_hash: sha256:7037971bb67e0953
translated_by: human
en-US:
name: Delete Agent
short_desc: Safely delete an Agent and its associated data, with multi-step confirmation and optional history cleanup
description: Safely delete a specified Agent and its associated data. Verifies the Agent's state before deletion and optionally removes all session history. Use when the user needs to delete an Agent that is no longer in use.
body: ./SKILL.md
source_hash: sha256:6b971559e1d4ccc0
source_hash: sha256:7037971bb67e0953
translated_by: ai:claude-fable-5
translated_at: '2026-07-18'
translated_at: '2026-07-19'
market:
icon: >-
<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0
@@ -55,186 +55,53 @@ market:
required_client_version: 10.0.90
---
# delete-agent Skill
# delete-agent skill
## L0: One-line Summary
## L0: One-Sentence Summary
Safely delete a specified Agent and its associated data, including filesystem, in-memory state, and optionally session history.
Safely delete a specified Agent and its associated data (filesystem, in-memory state, optional conversation history).
## L1: Overview and Use Cases
## L1: Overview
### Capability Description
Meta-skill: list candidates → confirm intent (irreversible) → ask whether to delete history → execute via `ManageAgent(action='delete')`. Its value is what the tool can't give: candidate filtering with status guidance, and intent confirmation before deletion. The tool guarantees the multi-way refusals (core agent / self / active state) and team cascading.
delete-agent is a **Meta-Skill** that empowers DesireCore to safely delete other Agents. It runs full pre-flight checks and state validation through the in-process builtin tool **ManageAgent**, and cleans up all associated data.
## L2: Detailed Spec
### Use Cases
Flow: list deletable Agents → confirm intent and target → ask whether to delete history → execute → receipt.
- The user wants to clean up Agents that are no longer in use
- Delete temporary Agents created for testing or experimentation
- Free up storage space by deleting old Agents and their history
- The user explicitly asks to "delete" or "remove" a particular Agent
### Stage 1: List Candidates
### Core Value
- **Safety**: multiple rejection rules at the tool layer ensure that core Agents, the caller itself, or active Agents are never deleted by mistake
- **Completeness**: cleans up filesystem, in-memory state, message subscriptions, and all associated data, and handles team cascading
- **Recoverability**: session history is preserved by default, with the option to delete it
## L2: Detailed Specification
### Execution Flow
When the user hasn't named a specific Agent, fetch the list with `ManageAgent(action='list')` and group by status: `offline` / `error` are safe to delete; `online` / `busy` / `recovery` are marked "stop first" (the tool will refuse them) and excluded from the rest of the flow. For details, use `ManageAgent(action='get', id)`. E.g.:
```
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ List target │ ──→ │ Confirm │ ──→ │ Ask about │
│ Agents │ │ intent/target│ │ options │
└──────────────┘ └──────────────┘ │ (delete runs?)│
└──────────────┘
│
↓
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Return result│ ←── │ Execute │ ←── │ Inform that │
│ and receipt │ │ ManageAgent │ │ a popup will│
│ │ │ │ │ appear │
└──────────────┘ └──────────────┘ └──────────────┘
Deletable: Legal Advisor (legal-assistant, offline), Test Bot (test-bot, offline)
Stop first: Data Analyst (data-analyst, online)
```
### Phase 1: List Deletable Agents
### Stage 2: Confirm Intent
**Trigger condition**: the user expresses intent to delete but does not specify a particular Agent
Confirm the target Agent (name/ID) with the user, **explicitly state it is irreversible** (config, skills, tools will be permanently deleted), show basic info, and wait for confirmation.
**Operation**:
### Stage 3: Ask About Deletion Options
- Call `ManageAgent(action='list')` to fetch the list of all Agents
- Filter Agents whose status is `offline` or `error` (safe to delete)
- Annotate Agents whose status is `online`/`busy`/`recovery` (must be stopped first, otherwise the tool will reject them)
- To view detailed information about a specific Agent, call `ManageAgent(action='get', id='<agent-id>')`
Ask whether to also delete all of the Agent's conversation history: yes → `deleteRuns=true`; no → `deleteRuns=false` (default, omittable, keeps history).
**Output example**:
### Stage 4: Execute Deletion
```
Deletable Agents:
1. Legal Advisor Assistant (legal-assistant) - status: offline
2. Test Bot (test-bot) - status: offline
Currently active Agents (must be stopped before deletion):
- Data Analyst (data-analyst) - status: online
```
### Phase 2: Confirm User Intent and Target
**Confirmation points**:
- The Agent name/ID specified by the user
- Explicitly inform that deletion is irreversible
- Display the Agent's basic info for the user to confirm
**Dialog example**:
```
You are about to delete the Agent "Legal Advisor Assistant" (legal-assistant).
⚠️ Warning: this operation is irreversible. All configuration, skills, and tools of this Agent will be permanently deleted.
Confirm deletion? (yes/no)
```
### Phase 3: Ask About Deletion Options
**Question content**:
```
Do you also want to delete all session history of this Agent?
- Yes: delete the Agent and all of its conversation records
- No: keep session history; delete only the Agent itself
Default option: No (keep history)
```
**Parameter mapping**:
- User chooses "Yes" → `deleteRuns=true`
- User chooses "No" → `deleteRuns=false` (default, can be omitted)
### Phase 4: Inform About the Tool-level Confirmation
The delete action of `ManageAgent` **always triggers a user confirmation popup at the tool layer**, so there is no need to repeat a second confirmation prompt at the skill layer. However, before the call you should inform the user:
```
About to delete the Agent "Legal Advisor Assistant" (legal-assistant), with a scope of the Agent + session history (if chosen by the user).
The system will show a confirmation window; please confirm the execution in the popup.
```
### Phase 5: Execute the Deletion (ManageAgent tool)
**Tool call**:
Before the call, tell the user "the system will pop up a confirmation window; please confirm there" (delete is force-confirmed at the tool layer). Execute:
```
ManageAgent(action='delete', id='legal-assistant', deleteRuns=true)
```
**Parameters**:
After confirmation the deletion completes, including team cascading: a team whose supervisor is the target is disbanded; membership is removed where the target is a member.
- `id`: the target Agent ID (required)
- `deleteRuns`: `true` to also delete all session history; `false` (default) to keep history, can be omitted
### Stage 5: Receipt
The tool shows a user confirmation popup before executing; once confirmed, it completes the deletion, including team cascading: a team where the target is the leader is automatically disbanded, and a target that is a member is automatically removed.
From the tool's return (cleaned paths, deleted run count, memory-cleanup details), produce a user-friendly report (no internal paths), e.g. "✅ Deleted XXX; cleaned filesystem / scheduler / subscriptions / MCP / N conversation records / team cascade".
### Phase 6: Return the Operation Result
### Deletion Scope and Boundaries
**Successful receipt handling**: the tool returns the deletion result, including fields such as the cleaned paths, the number of deleted sessions, and in-memory state cleanup details. Generate the report from these.
**Result report template**:
```
✅ Agent "Legal Advisor Assistant" successfully deleted
Cleanup details:
- Filesystem: 2 directories deleted
- Scheduler: all scheduled tasks stopped
- Message subscriptions: 3 subscriptions canceled
- MCP connection: closed
- Session history: 5 records deleted
- Team cascading: the target's team has been disbanded / the target has been removed from its team (if applicable)
```
## State Validation and Error Handling
### Pre-deletion State Check
When listing Agents in Phase 1, filter by the status returned from `ManageAgent(action='list')`:
| Status | Deletable? | Phase 1 Display |
| ------------------------------ | ----------- | ------------------------------ |
| `offline` / `error` | ✅ Yes | Listed under "Deletable" |
| `online` / `busy` / `recovery` | ❌ Stop first | Annotated "must be stopped"; not entered into the subsequent flow |
> Agents in an active state (online/busy/recovery) are directly rejected by the delete action of `ManageAgent`. Prompt the user to stop the Agent manually in the UI, or wait until it finishes its current task before deleting.
### Error Semantics Returned by the Tool
`ManageAgent(action='delete', ...)` returns a clear error in the following cases; use them to explain the situation to the user and suggest next steps:
| Rejection Scenario | Trigger Condition | Handling |
| ------------------ | ------------------------------------------------------------- | ------------------------------------- |
| Core Agent rejected | The target is a core Agent (desirecore/core/bound UUID) | Inform the user that core Agents cannot be deleted |
| Self-deletion rejected | The target is the caller itself | Inform the user that an Agent cannot delete itself |
| Active state rejected | The target is in `online`/`busy`/`recovery` state | Prompt the user to stop the Agent in the UI first |
| Not found | No Agent exists for the target ID | Inform the user the Agent has already been deleted or the ID is wrong |
## Deletion Scope
| Category | Content Deleted | Condition |
| ------------ | -------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| **Always deleted** | AgentFS directory (config, persona, rules, skills, tools, memory), user preference data, in-memory state (scheduler, queue, message subscriptions, MCP connection), registry entries | Unconditional |
| **Optionally deleted** | Session history, topic index | `deleteRuns=true` |
| **Team cascading** | Target is the leader → its team is disbanded; target is a member → removed from the team | Automatic |
| **Preserved** | Data of other Agents, user configuration, global settings, market cache | — |
## Permission Requirements
- Uses the in-process builtin tool `ManageAgent` to list, query, and delete Agents
- The delete action is a high-risk operation; the tool layer will force a user confirmation popup
## Dependencies
- The in-process builtin tool `ManageAgent` (`action='list' | 'get' | 'delete'`)
- **Always deleted**: AgentFS directory (config/persona/rules/skills/tools/memory), user preference data, in-memory state (scheduler/queue/message subscriptions/MCP connections), registry entry. **Optionally deleted** (`deleteRuns=true`): conversation history and topic index. **Team cascade** (automatic): supervisor → disband team, member → remove. **Kept**: other Agents, user config, global settings, market cache.
- Explain tool refusals to the user with a next step: the core agent (desirecore / core / bound UUID) cannot be deleted; the caller can't delete itself; active state (online/busy/recovery) needs stopping in the UI first or waiting until idle; a non-existent ID means the Agent is already gone or the ID is wrong.
- Always done via `ManageAgent` (`action='list' | 'get' | 'delete'`); delete is a high-risk operation and is force-confirmed at the tool layer.