dedash

1Remove the em and en dashes standing in for other punctuation inside running prose, one occurrence at a time, and leave every hyphen, range and label separator alone.
2 
3## Goal
4 
5An agent overuses the em dash inside ordinary sentences, where a writer would have reached for a comma, a colon, parentheses or a full stop. Removing those is this skill's whole job. Three characters are easy to confuse and do different work: the hyphen (U+002D) joins compounds and is never a candidate; the en dash (U+2013) marks ranges such as 1990 to 2000 and is a candidate only when it stands in for an em dash; the em dash (U+2014, with the look-alikes U+2015, U+2E3A and U+2E3B) is the usual offender. A dash in a fixed label slot, such as after a bold term opening a list item, after a heading's number or between a name and its tagline, is a typographic separator and stays. The user owns the scope: a passage, field, file, selection or tree. Ask before widening it.
6 
7## Workflow
8 
91. **FIND**: Take the exact scope from the user. From this skill's folder run `node scripts/find.mjs <paths...> [--json]` over it. Input: files or directories. Output: every em and en dash with its file, line, column, code point, slot and line text, then a count per slot that sums to the total; `--json` prints one object with `counts` and `dashes`. Exit codes: 0 no in-sentence dash, 3 one or more, 2 a usage error, which is a broken run: fix the command and run again. A hyphen never appears in the list.
10…