技能进化
- 作者仓库星标 479
- 作者仓库 UniClipboard
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @UniClipboard · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步——收集背景信息
完整阅读引用的 SKILL.md。查看当前对话以确定: 出了什么问题或发现了什么(事件/发现) 根本原因(为什么会发生) 修复或模式(正确的方法是什么)
第 2 步——对学习内容进行分类
确定需要哪种类型的更新: 类型 · 描述 · 示例新规则 · 根本没有覆盖的模式/反模式 · 禁止异步中的`.entered()` 规则细化 · 现有规则需要警告或边缘情况 · 当参数包含特征对象时需要 `skip_all` 新示例 · 正确/不正确的代码模式来说明现有规则 · `async {}.instrument(span).await` 用于匹配臂
第 3 步 — 起草更新
按照以下原则编写建议的添加内容: 匹配现有样式 - 相同的标题级别、表格格式、代码块约定 将其放在所属的位置 - 靠近相关内容,而不是在末尾随机附加 引导规则,然后是原因,然后是示例 添加反模式时包括正确和禁止的模式
第四步——应用和总结
使用新内容编辑 SKILL.md。向用户呈现摘要:
# Skill Evolve
Turn real-world experience into durable skill knowledge.
## When to Use
User invokes this skill after completing work that revealed a gap, pitfall, or new pattern not yet captured in an existing SKILL.md. Typical trigger: `/skill-evolve @path/to/SKILL.md`
## Procedure
### Step 1 — Gather Context
1. Read the referenced SKILL.md in full.
2. Review the current conversation to identify:
- **What went wrong or was discovered** (the incident/finding)
- **Root cause** (why it happened)
- **The fix or pattern** (what the correct approach is)
- **Why the existing skill didn't prevent it** (the gap)
### Step 2 — Classify the Learning
Determine which type of update is needed:
| Type | Description | Example |
| ---------------------- | ---------------------------------------------------------- | --------------------------------------------------- |
| **New Rule** | A pattern/anti-pattern not covered at all | `.entered()` in async is forbidden |
| **Rule Refinement** | Existing rule needs caveats or edge cases | `skip_all` needed when params include trait objects |
| **New Example** | Correct/incorrect code pattern to illustrate existing rule | `async {}.instrument(span).await` for match arms |
| **Checklist Addition** | New review checkpoint | "`.entered()` held across `.await`? FORBIDDEN" |
| **Section Expansion** | Existing section needs a new subsection | Adding async lifecycle patterns to spawn section |
### Step 3 — Draft the Update
Write the proposed additions following these principles:
- **Match the existing style** — same heading levels, table formats, code block conventions
- **Place it where it belongs** — near related content, not appended randomly at the end
- **Lead with the rule, then the why, then the example**
- **Include both CORRECT and FORBIDDEN patterns** when adding anti-patterns
- **Keep it concise** — skills are reference material, not tutorials
### Step 4 — Apply and Summarize
1. Edit the SKILL.md with the new content.
2. Present a summary to the user:
```
## Skill Evolution Summary
**Skill**: <skill name>
**Trigger**: <what happened that revealed the gap>
**Update type**: <New Rule | Rule Refinement | New Example | Checklist Addition | Section Expansion>
**What was added**:
- <bullet summary of each change>
**Section(s) modified**: <list of modified section numbers/names>
```
## Quality Gates
Before applying the update, verify:
- [ ] The new content does NOT duplicate existing rules (check the full SKILL first)
- [ ] The new content is grounded in a real incident from this conversation (not hypothetical)
- [ ] Code examples compile conceptually (correct syntax, realistic types)
- [ ] The learning is **generalizable** — useful beyond this one specific case
- [ ] If adding a FORBIDDEN pattern, a CORRECT alternative is shown alongside it
## Anti-Patterns for This Skill
- **Don't bloat**: If the learning is too narrow or one-off, suggest the user add it to memory instead of a skill
- **Don't rewrite**: Evolve the skill incrementally. Don't restructure or rewrite existing sections unless they are wrong
- **Don't speculate**: Only add patterns that were validated in practice during this conversation
- **Don't duplicate**: If the fix was specific to one codebase and not transferable, it belongs in CLAUDE.md, not a skill
章节与文件索引
按说明文件中的顺序排列。
何时使用
第 1 步——收集背景信息
第 2 步——对学习内容进行分类
第 3 步 — 起草更新
第四步——应用和总结
文件/命令 -> /skill-evolve @path/to/SKILL.md · .entered() · skip_all · async {}.instrument(span).await · .await
内容校验值 -> 2b372d3a3e2b
当前原文的自动摘译,尚未人工审校。
何时使用
用户在完成发现现有 SKILL.md 中尚未捕获的差距、陷阱或新模式的工作后调用此技能。典型触发:
/skill-evolve @path/to/SKILL.md