Agent Skills › catlog22/Claude-Code-Workflow › skill-simplify

skill-simplify

GitHub

用于简化SKILL.md文档内容，通过三阶段流程分析功能清单、应用优化规则并验证完整性。旨在去除冗余描述性内容，同时确保所有功能性代码和逻辑不被丢失或篡改。

.claude/skills/skill-simplify/SKILL.md catlog22/Claude-Code-Workflow

触发场景

simplify skill optimize skill skill-simplify

安装

npx skills add catlog22/Claude-Code-Workflow --skill skill-simplify -g -y

更多选项

非标准路径

npx skills add https://github.com/catlog22/Claude-Code-Workflow/tree/main/.claude/skills/skill-simplify -g -y

不安装直接使用

npx skills use catlog22/Claude-Code-Workflow@skill-simplify

指定 Agent (Claude Code)

npx skills add catlog22/Claude-Code-Workflow --skill skill-simplify -a claude-code -g -y

安装 repo 全部 skill

npx skills add catlog22/Claude-Code-Workflow --all -g -y

预览 repo 内 skill

npx skills add catlog22/Claude-Code-Workflow --list

SKILL.md

Frontmatter

{
    "name": "skill-simplify",
    "description": "SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functionality lost. Triggers on \"simplify skill\", \"optimize skill\", \"skill-simplify\".",
    "allowed-tools": "AskUserQuestion, Read, Write, Edit, Bash, Glob, Grep"
}

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