Back to Details

skill-improver

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Skill Improver

Skill 改进器

Overview

概述

This skill guides reflective improvement of skills and processes through structured analysis. Rather than automatically suggesting changes, it provides a framework for mindful reflection to identify high-impact improvements without creating bloat.
The philosophy follows Buddhist "skillful means" (upaya) - developing concrete, practical wisdom through iteration. The goal is harmonious operation between Claude and the user by refining skills to be clearer, more complete, and more efficient.
此技能通过结构化分析，引导用户对Skill与流程进行反思性改进。它不会自动提出修改建议，而是提供一个审慎反思的框架，以识别高价值改进，避免冗余内容。
其理念遵循佛教的“善巧方便”（upaya）——通过迭代培养具体、实用的智慧。目标是通过优化Skill，使其更清晰、更完整、更高效，实现Claude与用户的协作和谐。

When to Use This Skill

使用时机

Use this skill:
  • At the end of a session when significant work has been completed
  • After completing a complex task that involved multiple skills or tools
  • When experiencing repeated friction, confusion, or failures during execution
  • When discovering a workaround or novel pattern that should be captured
  • When the user expresses frustration with a process or skill
  • After successfully navigating a challenging workflow that could be easier next time
Do not use this skill:
  • After every tiny task (reflection should be purposeful, not reflexive)
  • When there's nothing substantial to improve
  • During active work (finish first, then reflect)
使用此技能的场景：
  • 完成大量工作的会话结束时
  • 完成涉及多个Skill或工具的复杂任务后
  • 在执行过程中反复遇到阻碍、困惑或失败时
  • 发现可被固化的变通方案或新颖模式时
  • 用户对某个流程或Skill表示不满时
  • 成功完成具有挑战性的工作流后，希望未来能更轻松地完成时
请勿使用此技能的场景：
  • 完成每一项微小任务后（反思应具有目的性，而非条件反射）
  • 没有实质性改进空间时
  • 正在进行工作时（先完成工作，再进行反思）

Reflection Workflow

反思工作流

1. Identify the Context

1. 明确背景信息

Clearly establish what process or skill is being reflected upon:
  • What was the original goal or request?
  • Which skills were used?
  • What tools and resources were involved?
  • How did the process unfold?
清楚确定正在反思的流程或Skill：
  • 最初的目标或需求是什么？
  • 使用了哪些Skill？
  • 涉及哪些工具和资源？
  • 流程是如何推进的？

2. Apply the Reflection Framework

2. 应用反思框架

Use 
references/reflection_framework.md
to systematically analyze the experience. The framework provides structured questions across five dimensions:
  1. Process Execution - What happened? What worked? What didn't?
  2. Skill Content Analysis - Was the skill clear, complete, efficient, accurate?
  3. Tool and Resource Analysis - Were the right tools available? Did they work well?
  4. Pattern Recognition - Is this a one-time issue or recurring pattern?
  5. Improvement Identification - What specific changes would help?
Load and review the framework:
Read references/reflection_framework.md and work through the relevant questions
使用
references/reflection_framework.md
来系统分析本次经验。该框架从五个维度提供了结构化问题：
  1. 流程执行 - 发生了什么？哪些部分有效？哪些无效？
  2. Skill内容分析 - Skill是否清晰、完整、高效、准确？
  3. 工具与资源分析 - 是否使用了合适的工具？工具的表现如何？
  4. 模式识别 - 这是一次性问题还是反复出现的模式？
  5. 改进方向识别 - 哪些具体变更会有所帮助？
加载并查看框架：
Read references/reflection_framework.md and work through the relevant questions

3. Identify Improvement Patterns

3. 识别改进模式

Consult 
references/improvement_patterns.md
to recognize common issues:
  • Clarity issues (ambiguous descriptions, jargon, vague steps)
  • Completeness issues (missing prerequisites, edge cases, error handling)
  • Efficiency issues (redundant instructions, missing scripts, context bloat)
  • Usability issues (poor discoverability, overwhelming complexity)
  • Structural issues (wrong abstraction level, missing decision trees)
Load and cross-reference patterns:
Read references/improvement_patterns.md to identify which patterns match the observed issues
参考
references/improvement_patterns.md
来识别常见问题：
  • 清晰度问题（描述模糊、术语晦涩、步骤不明确）
  • 完整性问题（缺少前置条件、边缘场景处理、错误处理）
  • 效率问题（冗余指令、缺少脚本、上下文冗余）
  • 易用性问题（可发现性差、复杂度过高）
  • 结构问题（抽象层级不当、缺少决策树）
加载并交叉匹配模式：
Read references/improvement_patterns.md to identify which patterns match the observed issues

4. Formulate Specific Improvements

4. 制定具体改进方案

Based on reflection, create concrete, actionable improvement proposals. Each improvement should include:
  • Skill/Process: Name of what's being improved
  • Issue Observed: Concrete description of the problem
  • Root Cause: Why this happened (what's missing or wrong)
  • Proposed Change: Specific, actionable improvement
  • Impact: High/Medium/Low priority
  • Implementation: Exact files and changes needed
基于反思结果，创建具体、可执行的改进提案。每个改进方案应包含：
  • Skill/流程：待改进对象的名称
  • 发现的问题：对问题的具体描述
  • 根本原因：问题产生的原因（缺失或错误的内容）
  • 建议变更：具体、可执行的改进措施
  • 影响优先级：高/中/低
  • 实施细节：需要修改的具体文件和内容

5. Apply Improvement Principles

5. 遵循改进原则

Before finalizing recommendations, verify they follow skillful means:
Do:
  • Be specific and concrete
  • Show evidence from actual experience
  • Consider cost/benefit ratio
  • Prefer simplification over addition
  • Document principles and "why", not just "what"
Don't:
  • Pile on multiple vague changes
  • Over-engineer solutions
  • Duplicate existing information
  • Spam the user with minor tweaks
在最终确定建议前，验证是否符合“善巧方便”的原则：
需要做到：
  • 具体、明确
  • 提供实际经验中的证据
  • 考虑成本收益比
  • 优先简化而非新增内容
  • 记录原则和“原因”，而非只记录“内容”
请勿：
  • 提出多个模糊的变更建议
  • 过度设计解决方案
  • 重复已有信息
  • 向用户推送大量微小调整

6. Execute Improvements (if appropriate)

6. 执行改进（如适用）

For high-impact improvements:
  • If editing an existing skill, use the skill-creator skill to make changes
  • If creating a new skill is warranted, use the skill-creator skill
  • For process improvements, document the new approach
For lower-impact improvements:
  • Present findings to the user for future consideration
  • Ask if they'd like to implement changes now or later
对于高优先级的改进：
  • 若需编辑现有Skill，使用skill-creator技能进行修改
  • 若需要创建新Skill，使用skill-creator技能
  • 对于流程改进，记录新的操作方式
对于低优先级的改进：
  • 向用户展示发现结果，供未来参考
  • 询问用户是否希望立即或稍后实施变更

Decision Tree: Improve vs Create

决策树：改进还是创建

Sometimes the best improvement is creating a new skill. Use this decision tree:
Create a new skill when:
  • Distinct domain sufficiently different from existing skills
  • Recurring multi-step workflow that happens repeatedly
  • Requires unique scripts, templates, or reference documentation
  • Clear trigger that distinguishes it from other skills
Improve existing skill when:
  • Issue is with clarity, completeness, or organization
  • Missing resources (scripts, references, assets) for existing workflow
  • Same domain, just needs better documentation or tools
  • Edge cases or error handling need addressing
Do nothing when:
  • Issue was a one-time environmental problem
  • Adding documentation would create bloat without value
  • Change would over-engineer a simple process
  • Proposed improvement won't actually be used
有时最佳改进方式是创建新Skill。使用以下决策树：
创建新Skill的场景：
  • 领域与现有Skill差异显著
  • 存在重复出现的多步骤工作流
  • 需要独特的脚本、模板或参考文档
  • 有明确的触发条件，可与其他Skill区分
改进现有Skill的场景：
  • 问题出在清晰度、完整性或组织结构上
  • 现有工作流缺少必要的资源（脚本、参考资料、资源文件）
  • 同一领域内，仅需优化文档或工具
  • 需要处理边缘场景或错误情况
无需操作的场景：
  • 问题是一次性的环境因素导致
  • 添加文档会造成冗余，无实际价值
  • 变更会过度简化流程
  • 建议的改进不会被实际使用

Resources

资源

This skill includes reference documentation to guide the reflection process:
此技能包含参考文档，以指导反思过程：

references/reflection_framework.md

references/reflection_framework.md

Structured framework with questions across five dimensions:
  1. Process Execution
  2. Skill Content Analysis
  3. Tool and Resource Analysis
  4. Pattern Recognition
  5. Improvement Identification
Use this to systematically analyze what happened and identify specific improvement opportunities.
从五个维度提供结构化问题的框架：
  1. 流程执行
  2. Skill内容分析
  3. 工具与资源分析
  4. 模式识别
  5. 改进方向识别
使用此框架系统分析事件经过，确定具体的改进机会。

references/improvement_patterns.md

references/improvement_patterns.md

Catalog of common skill issues and their solutions:
  • Clarity issues (ambiguous descriptions, jargon, vague workflows)
  • Completeness issues (missing prerequisites, edge cases, error handling)
  • Efficiency issues (redundancy, missing scripts, context bloat, missing templates)
  • Usability issues (discoverability, complexity, inconsistent terminology)
  • Structural issues (abstraction level, decision trees, undocumented scripts)
Use this to recognize patterns and find proven solutions.
常见Skill问题及其解决方案的汇总：
  • 清晰度问题（描述模糊、术语晦涩、工作流不明确）
  • 完整性问题（缺少前置条件、边缘场景处理、错误处理）
  • 效率问题（冗余、缺少脚本、上下文冗余、缺少模板）
  • 易用性问题（可发现性差、复杂度高、术语不一致）
  • 结构问题（抽象层级不当、决策树缺失、脚本未文档化）
使用此文档识别问题模式，并找到已验证的解决方案。

Example Usage

使用示例

Example 1: Missing Scripts

示例1：缺少脚本

Scenario: After using the 
pdf-editor
skill to rotate several PDFs, Claude had to rewrite rotation code multiple times due to varying file permissions.
Reflection:
  1. Context: Used pdf-editor skill to rotate PDFs, encountered permission issues
  2. Framework application: Process execution had friction - repetitive code writing, unexpected errors
  3. Pattern recognition: Matches "Missing scripts for repetitive tasks" and "Incomplete error handling"
  4. Improvement formulation:
    • Skill/Process: pdf-editor
    • Issue: Rewrote PyPDF2 rotation code 3 times; permission errors not handled
    • Root Cause: No rotation script; permission handling undocumented
    • Proposed Change: Create 
      scripts/rotate_pdf.py
      with permission handling; add troubleshooting section
    • Impact: High - eliminates code rewriting, prevents permission errors
    • Implementation: Create script, update SKILL.md to reference it
  5. Execution: Use skill-creator to add script and update documentation
场景：使用
pdf-editor
Skill旋转多个PDF文件后，Claude因文件权限不同，不得不多次重写旋转代码。
反思过程：
  1. 背景：使用pdf-editor Skill旋转PDF文件，遇到权限问题
  2. 框架应用：流程执行存在阻碍——重复编写代码、出现意外错误
  3. 模式识别：符合“重复任务缺少脚本”和“错误处理不完整”模式
  4. 改进方案制定：
    • Skill/流程：pdf-editor
    • 问题：重写PyPDF2旋转代码3次；未处理权限错误
    • 根本原因：无旋转脚本；权限处理未文档化
    • 建议变更：创建
      scripts/rotate_pdf.py
      并添加权限处理；新增故障排除章节
    • 影响优先级：高——消除重复编码，避免权限错误
    • 实施细节：创建脚本，更新SKILL.md以引用该脚本
  5. 执行：使用skill-creator添加脚本并更新文档

Example 2: Missing Reference Documentation

示例2：缺少参考文档

Scenario: After creating a Lorn/Clams Casino inspired beat using the 
strudel
skill, user feedback revealed bass tone missed the mark. User corrected: "don't need to encode every iteration" and "bass tone not reminding me of references."
Reflection:
  1. Context: Used strudel skill for dark ambient hip-hop, encountered two issues
  2. Framework application:
    • Process execution: URL encoding was inefficient during iterations
    • Skill content: No guidance for translating artist references into techniques
  3. Pattern recognition: Matches "Vague workflow steps" and "Missing reference documentation"
  4. Improvement formulation:
    • Skill/Process: strudel
    • Issue #1: Encoded URL after every iteration; user said only needed on initial creation
    • Root Cause: Skill said "Always encode after modifications" - too broad
    • Proposed Change: Clarify when to encode (initial only, skip iterations, final if requested)
    • Impact: Medium - prevents unnecessary work
    • Implementation: Update SKILL.md section "Providing Output to the User"
    • Issue #2: No systematic guide for artist characteristics (Lorn, Clams Casino)
    • Root Cause: No reference for common genre/artist styles
    • Proposed Change: Create 
      references/genre-styles.md
      with artist characteristics and Strudel techniques
    • Impact: High - translates user references into concrete implementation
    • Implementation: Create reference file, update SKILL.md to reference it
  5. Execution: Used skill-creator to implement both improvements; user approved both
场景：使用
strudel
Skill制作Lorn/Clams Casino风格的节拍后，用户反馈贝斯音色不符合预期。用户指出：“无需对每次迭代进行编码”以及“贝斯音色未达到参考风格”。
反思过程：
  1. 背景：使用strudel Skill制作黑暗氛围嘻哈音乐，遇到两个问题
  2. 框架应用：
    • 流程执行：迭代过程中URL编码效率低下
    • Skill内容：缺少将艺术家参考转化为技术实现的指导
  3. 模式识别：符合“工作流步骤模糊”和“缺少参考文档”模式
  4. 改进方案制定：
    • Skill/流程：strudel
    • 问题1：每次迭代后都编码URL；用户表示仅需在初始创建时编码
    • 根本原因：Skill中说明“修改后始终编码”——范围过广
    • 建议变更：明确编码时机（仅初始创建时、迭代时跳过、最终按需编码）
    • 影响优先级：中——避免不必要的工作
    • 实施细节：更新SKILL.md中“向用户提供输出”章节
    • 问题2：无系统指导将艺术家特征（Lorn、Clams Casino）转化为技术实现
    • 根本原因：缺少常见流派/艺术家风格的参考文档
    • 建议变更：创建
      references/genre-styles.md
      ，包含艺术家特征和Strudel实现技巧
    • 影响优先级：高——将用户参考转化为具体实现方法
    • 实施细节：创建参考文件，更新SKILL.md以引用该文件
  5. 执行：使用skill-creator实施两项改进；用户已批准

Philosophy: Skillful Means

理念：善巧方便

The goal is harmonious operation through continuous refinement:
  • Concrete over abstract: Prefer working examples to theoretical descriptions
  • Simplicity over completeness: Handle 80% of cases well rather than 100% poorly
  • Clarity over cleverness: Straightforward instructions beat elegant complexity
  • Practical over perfect: Ship useful improvements, iterate continuously
  • Harmonious over comprehensive: Reduce friction, don't add features
Each improvement should make Claude's and the user's life tangibly easier. If it doesn't pass this test, don't recommend it.
目标是通过持续优化实现协作和谐：
  • 具体优先于抽象：优先使用可运行示例，而非理论描述
  • 简洁优先于完整：做好80%的常见场景，胜过勉强覆盖100%的场景
  • 清晰优先于精巧：直白的指令优于复杂的优雅设计
  • 实用优先于完美：推出有用的改进，持续迭代
  • 和谐优先于全面：减少阻碍，而非新增功能
每一项改进都应切实提升Claude和用户的工作体验。如果无法达到此效果，请勿提出该建议。