trim-language
Installation
SKILL.md
Audit project prose against the tl-01..tl-12 cut-candidate catalog and produce one checklist of removable clauses and sentences for a human to review and delete. This skill is read-only over the reviewed files: it flags, it never edits. Every candidate carries the evidence that its removal loses nothing — a surviving copy elsewhere, or a catalogued filler pattern — so the reviewer can tick and delete with confidence. The state file is for your own resumability, not human review.
Mirror the four phases below in the host's todo tool so the user sees progress.
Non-negotiables (read first)
- Never modify reviewed files. Cut candidates go in the checklist only; a human does the deleting.
- Explicit invocation only. This skill runs when the user invokes
/trim-language— never auto-activate. - Cutting, not rewriting. Every finding is a removal (a full sentence, clause, heading, or filler word). If text needs rephrasing rather than deleting, it is out of scope.
- Classify every finding FALSIFIABLE (cites exact prose Grep can confirm, and for redundancy cites where the meaning survives) or OPINION (audience fit or over-explanation — interpretation-dependent, no external surviving copy to point to).
- Grep-verify every FALSIFIABLE citation before it enters the draft: the flagged prose in the cited file, and — for redundancy findings — the surviving copy at its cited location. Either miss → drop the finding and count it as a dropped hallucination.
- Conservative bias. A cut ships only if its meaning survives elsewhere or it is catalogued filler, and it survives the load-bearing challenge in Phase 3. When in doubt, don't flag the cut — never delete.
- One output file. The checklist is the single user-facing artifact; your end-of-run reply names only its path, never the state file or intermediate details.