What problem does it solve? Articles on documentation portals often get rejected as "not written for humans" or "AI slop" because they bury the answer, invent unsearchable terms, hide what was not measured, and print numbers no command can reproduce. This Skill encodes six editorial rules, learned from four real rewrites of one article, that make a post readable, searchable, and falsifiable. ## Core Features & Use Cases - Conclusion-first structure: Enforces a shape where the title states today's conclusion, the first screen carries the answer with numbers, and the author's post-mortem moves to the end. - Terminology and honesty rules: Requires accepted searchable terms glossed once at first use, a mandatory section naming what was never measured, and negative results shown beside positive ones. - Verifiable numbers: Every number must name the command or file that prints it, and a checker script (scripts/check-post.sh) validates shape, first-screen caps, term glosses, and border sections. - Use Case: Rewriting a study write-up that was returned as "a small article about nothing" — restructure it so the answer leads, all nine measurements appear, and an 11-item "what we did not measure" section closes the knowledge boundary. ## Quick Start Ask the agent to write or repair a documentation portal article using the write-post rules, then run scripts/check-post.sh on the resulting file to verify its structure.
