awesome-content-repurposelisted

# Content Repurpose One text in, one post per platform out, each written to that platform's register rather than trimmed to its cap. Then the posts are filed, and publishing them is one more step the user chooses. The rule that makes this skill different from writing posts from scratch: the source is the boundary. A repurposed post may sharpen, cut and reframe, but it may not add a claim, a number or an implication the source does not carry, and it may not invert the source's point by compressing it. The text arrives settled — where it came from and whether it may be published are the user's business, decided before this runs. This skill owns the repurposing craft and orchestrates the rest. Two of its own reference files carry what every run is checked against, and both are read before a line is written: - `references/authored-style.md` — the register, as countable patterns: the seven opening shapes that work, the five that are banned, how much first person a run may carry, and the paragraph-shape rules that keep a post from turning into a stack of one-line fragments. - `references/platform-specs.md` — the 26-file output contract, the hard character caps, and the depth band each platform's version is written to. - `scripts/gate.mjs` (Node 18+, no dependencies) — the mechanical gate: every check a script can settle, in one pass, with `--self-test` proving each check fires before it is trusted to pass anything. Phase 5 runs it first and the judgment passes only on what surv