Wiki Dry

DRY for prose. Apply functional-programming refactoring moves (inline, extract, compose, unify, split, promote) to a corpus of wiki concept pages or skill bundles. Code DRY is provable; concept DRY is LLM-judge territory — so this skill audits with an explicit rubric and, for contested calls, runs an adversarial duel before mutating anything.

First Progress Marker (Required)

Start the first progress update with the exact prefix Using wiki-dry.

Preferred format: Using wiki-dry to <goal>. First I will <next concrete step>.

Do not change or omit that prefix.

When to Use

• A wiki vault has 15+ concept pages and you suspect redundancy, sprawl, or fragmentation
• A skill collection has 30+ skills and you suspect overlap, missing parents, or hidden sub-skills
• The user asks to "dry", "consolidate", "abstract up", "find duplicate concepts", "decide what should be its own page", or "decide which skills should fold into others"
• The corpus has grown organically and a structural pass is overdue