mirror of
https://git.openapi.site/https://github.com/desirecore/market.git
synced 2026-07-23 05:23:40 +08:00
## 摘要 / Summary ### 中文 #56 的复盘修正。上一轮"强改写压缩"把四技能 L1 的**技术属性、使用场景与交互示范当套话一刀切**，造成实质信息丢失（承诺"意图全保留"但未做到）。本 PR 补回： - **create**：`创建仓库符合 AgentFS v2 规范、git 管理版本（可治理/可追溯）`定位；`基础创建`形态（name+description，description 自动填充 persona L0）；需求收集的**引导问题示例**（"起什么名字？/主要负责什么？"…）；企业部署/开发者原型使用场景。 - **update**：`agent 目录 git 管理版本、历史可追溯`定位 + 使用场景。 - **discover**：使用场景（浏览/新用户/找替代）+ `语义匹配而非关键词搜索`。 - **delete**：使用场景（清理/测试/释放存储）。 根因：L1 混着实质技术属性与营销套话、使用场景是触发判据、引导问题是交互示范，不该按"只留独有信息"一刀切。补回后仍保留结构性压缩（zh 正文合计仍降 ~64%）。版本 create 2.5.2 / update 3.1.3 / delete 2.5.2 / discover 2.6.2，manifest 1.2.13，中英双份同步、重算 source_hash（validate-i18n 通过）。 ### English Post-mortem fix for #56. The previous aggressive compression treated the skills' L1 technical attributes, use cases, and interaction demos as boilerplate and cut them in a blanket way, dropping substantive information (the "all intent preserved" claim wasn't fully met). This PR restores: create's AgentFS-v2 / git-version-management positioning, the "basic create" form (name+description auto-filling persona L0), the requirement-gathering prompt questions, and enterprise/developer use cases; update's git-versioned/traceable positioning and use cases; discover's use cases and "semantic match, not keyword search"; delete's use cases. Root cause: L1 mixed real technical attributes with marketing boilerplate, use cases are trigger cues, and prompt questions are interaction demos — none should have been blanket-cut. Structural compression is retained (zh bodies still ~64% smaller). Versions bumped, manifest 1.2.13, both locales synced, source hashes recomputed (validate-i18n passes).
This commit is contained in:
GitHub
@@ -1,5 +1,9 @@
|
||||
# Changelog
|
||||
|
||||
## [2.5.2] - 2026-07-19
|
||||
|
||||
- 复盘补回改写压缩时误删的实质信息：create 的 AgentFS v2/git 版本管理定位、基础创建（name+description 自动填充 persona L0）、需求收集引导问题示例；update/delete/discover 的使用场景与版本管理定位。功能对齐原始意图，仍保留结构性压缩。
|
||||
|
||||
## [2.5.1] - 2026-07-19
|
||||
|
||||
- 提示词改写压缩，功能不变——与 ManageAgent 工具契约重复的说明、装饰框图、重复表改写融入流程，示例就地精简；不外置、不净删，意图全保留。
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
name: create-agent
|
||||
description: >-
|
||||
通过多轮对话收集需求，调用 ManageAgent 内置工具创建新的 AgentFS v2 智能体，支持自定义 persona 和 principles。Use when 用户要求创建新智能体、培养某领域助手、或快速基于模板生成可治理 Agent。
|
||||
version: 2.5.1
|
||||
version: 2.5.2
|
||||
type: meta
|
||||
risk_level: low
|
||||
status: enabled
|
||||
@@ -26,7 +26,7 @@ metadata:
|
||||
description: >-
|
||||
通过多轮对话收集需求，调用 ManageAgent 内置工具创建新的 AgentFS v2 智能体，支持自定义 persona 和 principles。Use when 用户要求创建新智能体、培养某领域助手、或快速基于模板生成可治理 Agent。
|
||||
body: ./SKILL.zh-CN.md
|
||||
source_hash: sha256:a119427bed3bcd72
|
||||
source_hash: sha256:fa447cd4d5a5b336
|
||||
translated_by: human
|
||||
en-US:
|
||||
name: Create Agent
|
||||
@@ -34,7 +34,7 @@ metadata:
|
||||
description: >-
|
||||
Collect requirements through multi-turn conversation and call the ManageAgent builtin tool to create a new AgentFS v2 Agent, with customizable persona and principles. Use when the user asks to create a new Agent, raise a domain assistant, or quickly produce a governable Agent from a template.
|
||||
body: ./SKILL.md
|
||||
source_hash: sha256:a119427bed3bcd72
|
||||
source_hash: sha256:fa447cd4d5a5b336
|
||||
translated_by: ai:claude-fable-5
|
||||
translated_at: '2026-07-19'
|
||||
market:
|
||||
@@ -68,7 +68,7 @@ Collect requirements through natural-language conversation and call the ManageAg
|
||||
|
||||
## L1: Overview
|
||||
|
||||
Meta-skill: gather requirements over multi-turn conversation → generate persona/principles → land via `ManageAgent(action='create')`. Use it to raise a domain specialist for the user (legal advisor, financial analyst, etc.). Its value is what the tool can't give: domain-tailored persona/principles generation + a pre-create preview confirmation.
|
||||
Meta-skill: gather requirements over multi-turn conversation → generate persona/principles → land via `ManageAgent(action='create')`. Use it to raise a domain specialist (legal advisor, financial analyst), deploy a customized business Agent quickly, or produce a prototype from a template. The created repo conforms to the AgentFS v2 spec and is version-managed by git (governable, traceable). Its value is what the tool can't give: domain-tailored persona/principles generation + a pre-create preview confirmation.
|
||||
|
||||
## L2: Detailed Spec
|
||||
|
||||
@@ -80,7 +80,7 @@ Trigger (any): user explicitly says "create an Agent / make me an assistant"; de
|
||||
|
||||
### Stage 2: Requirement Gathering
|
||||
|
||||
- Required: `name`, `role` (core responsibility), `target_users`, `domain` (specialty).
|
||||
- Required (parenthesized = example prompt question): `name` ("what to name it?"), `role` ("what does it mainly do?"), `target_users` ("who will use it?"), `domain` ("what expertise does it need?").
|
||||
- Optional: `style` (communication tone), `boundaries` (red lines), `language` (default Chinese) — defaults derived from the domain template.
|
||||
- Strategy: prefer inferring from the user's natural description; only ask for missing required fields; at most 2 questions per turn.
|
||||
|
||||
@@ -126,6 +126,7 @@ ManageAgent({
|
||||
```
|
||||
|
||||
- Minimal create needs only `{ "action": "create", "name": "My Assistant" }` (everything else auto-generated).
|
||||
- Basic create `{ "action": "create", "name": "Legal Advisor", "description": "contract review" }` — with just name + description, the description auto-fills persona's L0.
|
||||
- Optional `id` (kebab-case slug; `core` / `desirecore` are reserved core identifiers and cannot be used, including when the slug auto-generated from `name` collides), `config.llm` (llm delta only; sensitive fields like mcp_servers are rejected and must be adjusted via the UI after creation).
|
||||
- The Agent is registered and usable immediately; the returned ID works directly with ManageTeam / Delegate. If the tool errors (already exists / reserved identifier / non-whitelisted config field, etc.), explain the reason and retry after adjusting per the hint.
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@
|
||||
|
||||
## L1：概述
|
||||
|
||||
元技能：多轮对话收集需求 → 生成 persona/principles → `ManageAgent(action='create')` 落地。用于为用户培养某专业领域的数字助手（法律顾问、财务分析师等）。价值在工具给不了的部分：领域化的人格/原则生成 + 创建前的预览确认。
|
||||
元技能：多轮对话收集需求 → 生成 persona/principles → `ManageAgent(action='create')` 落地。用于为用户培养专业领域数字助手（法律顾问、财务分析师）、企业快速部署定制业务 Agent、或基于模板快速创建原型。创建的仓库符合 AgentFS v2 规范、由 git 管理版本（可治理、可追溯）。价值在工具给不了的部分：领域化的人格/原则生成 + 创建前的预览确认。
|
||||
|
||||
## L2：详细规范
|
||||
|
||||
@@ -20,7 +20,7 @@
|
||||
|
||||
### 阶段 2：需求收集
|
||||
|
||||
- 必填：`name`（名称）、`role`（核心职责）、`target_users`（目标用户）、`domain`（专业领域）。
|
||||
- 必填（括号内为引导问题示例）：`name`（"起什么名字？"）、`role`（"主要负责什么工作？"）、`target_users`（"谁会使用它？"）、`domain`（"需要哪些专业知识？"）。
|
||||
- 选填：`style`（沟通风格）、`boundaries`（禁区/红线）、`language`（默认中文）——缺省由领域模板决定。
|
||||
- 策略：优先从用户自然描述推断，只追问未提及的必填项，每轮最多问 2 个。
|
||||
|
||||
@@ -66,6 +66,7 @@ ManageAgent({
|
||||
```
|
||||
|
||||
- 最简创建只需 `{ "action": "create", "name": "我的助手" }`（其余全自动生成）。
|
||||
- 基础创建 `{ "action": "create", "name": "法律顾问", "description": "专注合同审查" }`——只给 name + description，description 会自动填充 persona 的 L0。
|
||||
- 可选 `id`（kebab-case slug；`core` / `desirecore` 为核心保留标识不可用，含 name 自动生成命中的情况）、`config.llm`（仅 llm 增量；mcp_servers 等敏感字段会被拒，需创建后经界面调整）。
|
||||
- 创建后智能体立即在线可用，返回 ID 可直接用于 ManageTeam / Delegate。若工具报错（已存在 / 命中保留标识 / config 非白名单字段等），向用户说明原因并按提示调整后重试。
|
||||
|
||||
|
||||
Reference in New Issue
Block a user