← ClaudeAtlas

prose-passeslisted

Revise non-fiction prose that already exists, in German or English, through three passes in fixed order: jargon, ambiguity, inverted pyramid. Use whenever the user asks to revise, clarify, de-jargonise or de-market existing text: READMEs, documentation, landing pages, reports, slides, proposals, web copy. Triggers include 'überarbeite die README', 'mach das verständlicher', 'kann das jemand ohne Vorwissen lesen', 'make this less marketing-y', 'run an ambiguity pass', 'this reads like AI wrote it'. For writing new prose from scratch, use human-writing instead.
UBA-PSI/psi-writing-skills · ★ 0 · Data & Documents · score 60
Install: claude install-skill UBA-PSI/psi-writing-skills
# Prose passes An editing procedure for text that already exists and was written by someone who knows the subject too well. It does not invent content. Each pass asks one question, and the three questions are separate reads. Run all three even when the request names only one of the problems. The passes feed each other: cutting jargon creates new referents for pass 2 to resolve, and resolving them changes which sentence carries the point in pass 3. A single pass run alone leaves the text in a state the other two were meant to clean up. This skill is the procedure. The rules it applies live next to it, and it loads them at the points where they are needed: - `human-writing`, a sibling skill: AI tells, formatting, and the full versions of the vocabulary and ambiguity rules (sections "Audience and Vocabulary", "The Ambiguity Pass", plus `CHECKLIST.md`). - `references/academic.md`: the same ground recalibrated for papers, theses and funding proposals, where terminology is load-bearing and the panel is mixed. Load it for academic text only. ## Step 0: name the audience, before touching a word Every later judgement is calibrated to this answer, so an unstated audience means you are editing for yourself, and you are never the audience. Ask who the reader is. If you cannot ask, write the assumption down at the top of your report where the reviewer will see it, and proceed. "Lecturers and students who do not build websites" leads to different edits than "developers evalu