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 |
Pre-load (before execution)
- Codebase docs: If
.workflow/codebase/ARCHITECTURE.md exists, read for project context
- Specs:
maestro load --type spec --category coding — load coding conventions
- Wiki knowledge:
maestro search "skill design optimization" --json — top 5 entries as prior context
- All optional — proceed without if unavailable
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 |
1---2name: skill-simplify-23description: SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functionality lost. Triggers on "simplify skill", "optimize skill", "skill-simplify".4---56# Skill Simplify78Three-phase pipeline: analyze functional inventory, apply optimization rules, verify integrity.910**Phase Reference Documents** (read on-demand):1112| Phase | Document | Purpose |13|-------|----------|---------|14| 1 | [phases/01-analysis.md](phases/01-analysis.md) | Extract functional inventory, identify redundancy, validate pseudo-code format |15| 2 | [phases/02-optimize.md](phases/02-optimize.md) | Apply simplification rules, fix format issues |16| 3 | [phases/03-check.md](phases/03-check.md) | Verify functional integrity, validate format |1718## Pre-load (before execution)19201. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for project context212. **Specs**: `maestro load --type spec --category coding` — load coding conventions223. **Wiki knowledge**: `maestro search "skill design optimization" --json` — top 5 entries as prior context234. All optional — proceed without if unavailable2425## Input Processing2627```javascript28const targetPath = input.trim()29const targetFile = targetPath.endsWith('.md') ? targetPath : `${targetPath}/SKILL.md`30const originalContent = Read(targetFile)31const originalLineCount = originalContent.split('\n').length32```3334## TodoWrite Pattern3536```javascript37TodoWrite({ todos: [38 { content: `Phase 1: Analyzing ${targetFile}`, status: "in_progress", activeForm: "Extracting functional inventory" },39 { content: "Phase 2: Optimize", status: "pending" },40 { content: "Phase 3: Integrity Check", status: "pending" }41]})42```4344## Core Rules45461. **Preserve ALL functional elements**: Code blocks with logic, agent calls, data structures, routing, error handling, input/output specs472. **Only reduce descriptive content**: Flowcharts, verbose comments, duplicate sections, examples that repeat logic483. **Never summarize algorithm logic**: If-else branches, function bodies, schemas must remain verbatim494. **Classify code blocks**: Distinguish `functional` (logic, routing, schemas) from `descriptive` (ASCII art, examples, display templates) — only descriptive blocks may be deleted505. **Merge equivalent variants**: Single/multi-perspective templates differing only by a parameter → one template with variant comment516. **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 present527. **Validate pseudo-code**: Check bracket matching, variable consistency, structural completeness538. **Quantitative verification**: Phase 3 counts must match Phase 1 counts for functional categories; descriptive block decreases are expected5455## Error Handling5657| Error | Resolution |58|-------|------------|59| Target file not found | Report error, stop |60| Check FAIL (missing functional elements) | Show delta, revert to original, report which elements lost |61| Check WARN (descriptive decrease or merge) | Show delta with justification |62| Format issues found | Report in check, fix in Phase 2 |
catlog22