技能精简

其他社区

作者仓库星标 2,029
作者仓库 Claude-Code-Workflow

解读按原文结构重写，命令、链接、术语均保留；右侧可核对作者原始 SKILL.md

方法与流程

Input Processing：原文以此为独立章节。

适用与边界

当前原文没有单列适用场景。
Core Rules：Preserve ALL functional elements: Code blocks with logic, agent calls, data structures, routing, error handling, input/output specs Only reduce descriptive content: Flowcharts, verbose comments, duplicate sections, examples that repeat logic

原文中的明确线索

要点：「Phase Reference Documents」、「Preserve ALL functional elements」、「Only reduce descriptive content」、「Never summarize algorithm logic」、「Classify code blocks」、「Merge equivalent variants」、「Fix format issues」、「Validate pseudo-code」
文件与命令：${targetPath}/SKILL.md、Phase 1: Analyzing ${targetFile}、functional、descriptive

流狐整理：以上内容来自当前 SKILL.md 的章节与原词；未补写作者没有声明的工具、兼容性或能力。

Skill Simplify

Three-phase pipeline: analyze functional inventory, apply optimization rules, verify integrity.

Phase Reference Documents (read on-demand):

Phase	Document	Purpose
1	phases/01-analysis.md	Extract functional inventory, identify redundancy, validate pseudo-code format
2	phases/02-optimize.md	Apply simplification rules, fix format issues
3	phases/03-check.md	Verify functional integrity, validate format

Input Processing

const targetPath = input.trim()
const targetFile = targetPath.endsWith('.md') ? targetPath : `${targetPath}/SKILL.md`
const originalContent = Read(targetFile)
const originalLineCount = originalContent.split('\n').length

TodoWrite Pattern

TodoWrite({ todos: [
  { content: `Phase 1: Analyzing ${targetFile}`, status: "in_progress", activeForm: "Extracting functional inventory" },
  { content: "Phase 2: Optimize", status: "pending" },
  { content: "Phase 3: Integrity Check", status: "pending" }
]})

Core Rules

Preserve ALL functional elements: Code blocks with logic, agent calls, data structures, routing, error handling, input/output specs
Only reduce descriptive content: Flowcharts, verbose comments, duplicate sections, examples that repeat logic
Never summarize algorithm logic: If-else branches, function bodies, schemas must remain verbatim
Classify code blocks: Distinguish functional (logic, routing, schemas) from descriptive (ASCII art, examples, display templates) — only descriptive blocks may be deleted
Merge equivalent variants: Single/multi-perspective templates differing only by a parameter → one template with variant comment
Fix format issues: Nested backtick template literals in code fences → convert to prose; hardcoded option lists → flag for dynamic generation; workflow handoff references → ensure execution steps present
Validate pseudo-code: Check bracket matching, variable consistency, structural completeness
Quantitative verification: Phase 3 counts must match Phase 1 counts for functional categories; descriptive block decreases are expected

Error Handling

Error	Resolution
Target file not found	Report error, stop
Check FAIL (missing functional elements)	Show delta, revert to original, report which elements lost
Check WARN (descriptive decrease or merge)	Show delta with justification
Format issues found	Report in check, fix in Phase 2

流狐档案作者与许可取自来源；运行、权限和网络为流狐检测或估算

流狐分类: 通用
作者声明 Agent: 未找到明确声明；不据此推断已兼容或已测试
静态检查: 88 / 100 · 启发式扫描，不代表运行安全
作者 / 版本 / 许可: @catlog22 · 未声明 license
流狐 Token 估算: 低消耗
流狐接入估算: 需简单配置
是否需要外部 API Key: 未发现要求
检测到的系统要求: 未声明
底层运行要求: 未声明
检测到的文件与系统行为: 只读
允许写入 / 修改
Shell 执行
检测到的网络行为: 仅限本地
安装命令数: 无（仅作为资料）

档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。

需要注意： 未限定 allowed-tools，默认拥有全部工具权限。

输出预览 skill-simplify.preview

作者没有在当前 SKILL.md 中定义固定输出样例。

SKILL.md SKILL.md

# Skill Simplify

Three-phase pipeline: analyze functional inventory, apply optimization rules, verify integrity.

**Phase Reference Documents** (read on-demand):

| Phase | Document | Purpose |
|-------|----------|---------|
| 1 | [phases/01-analysis.md](phases/01-analysis.md) | Extract functional inventory, identify redundancy, validate pseudo-code format |
| 2 | [phases/02-optimize.md](phases/02-optimize.md) | Apply simplification rules, fix format issues |
| 3 | [phases/03-check.md](phases/03-check.md) | Verify functional integrity, validate format |

## Input Processing

```javascript
const targetPath = input.trim()
const targetFile = targetPath.endsWith('.md') ? targetPath : `${targetPath}/SKILL.md`
const originalContent = Read(targetFile)
const originalLineCount = originalContent.split('\n').length
```

## TodoWrite Pattern

```javascript
TodoWrite({ todos: [
  { content: `Phase 1: Analyzing ${targetFile}`, status: "in_progress", activeForm: "Extracting functional inventory" },
  { content: "Phase 2: Optimize", status: "pending" },
  { content: "Phase 3: Integrity Check", status: "pending" }
]})
```

## Core Rules

1. **Preserve ALL functional elements**: Code blocks with logic, agent calls, data structures, routing, error handling, input/output specs
2. **Only reduce descriptive content**: Flowcharts, verbose comments, duplicate sections, examples that repeat logic
3. **Never summarize algorithm logic**: If-else branches, function bodies, schemas must remain verbatim
4. **Classify code blocks**: Distinguish `functional` (logic, routing, schemas) from `descriptive` (ASCII art, examples, display templates) — only descriptive blocks may be deleted

…

证据边界与执行链路

作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。

章节    -> Input Processing → TodoWrite Pattern → Core Rules → Error Handling
要点    -> Phase Reference Documents · Preserve ALL functional elements · Only reduce descriptive content · Never summarize algorithm logic · Classify code blocks · Merge equivalent variants · Fix format issues · Validate pseudo-code
文件/命令 -> ${targetPath}/SKILL.md · Phase 1: Analyzing ${targetFile} · functional · descriptive
内容 SHA-256 -> be4705fbf1ec