plain-language-summarylisted

# Plain-Language Summary ## Core Rule A plain-language summary makes the work **accessible to a non-specialist without distorting the science**. Two failure modes, equally bad: jargon that locks the reader out, and *false simplification* that turns a calibrated finding into a stronger, cleaner claim than the paper makes. **Simpler wording must never become a stronger claim.** "reduces invalid tool calls on our benchmark" is allowed; "stops AI from making mistakes" is not — it dropped the scope, dropped the calibration, and overstated the result. The PLS is bound by the same cardinal rule as the manuscript (`CLAUDE.md → Source-Grounded Writing`): every statement traces to what the paper actually establishes, with its scope intact. Removing the hedge to read smoothly is overclaim; inventing a relatable number ("works 9 times out of 10") the paper does not report is fabrication. Plain does not mean loose. This skill rewrites for a general reader. It does not change the contribution or any reported quantity — those are fixed by the manuscript. ## When to Use Invoke with `/plain-language-summary` when: - A journal requires a plain-language summary, significance statement, or lay abstract. - A funder, institutional press office, or grant report needs a non-specialist description. - You want a general-audience version of the work that still passes a specialist's accuracy check. State the audience if it matters: `/plain-language-summary funder`. The default is an educated gen