platelisted

# plate Plating is the last look before the dish leaves the kitchen: nothing goes out with a thumbprint on the rim. This skill is that final pass over a single piece of outward-facing writing. It catches the things that leak the author's machine, identity, or internal world, and enforces the writing conventions, before the words are published where they cannot be unpublished. This is per-artifact prose hygiene. It is the companion to publish-readiness, which gates a whole repo and its git history; reach for that one for source trees and commit history, this one for the thing you are about to paste into a post, PR, or commit. ## What to scan for Run every check against the artifact text. Report each hit with its location and a concrete replacement. ### 1. Infrastructure and identity leaks - **Internal hostnames and machine names.** Personal box names, lab hostnames, anything that is not a public, intentional reference. Replace with a generic placeholder or the public project name. A cold agent will not know the user's machine names: ask for them, or flag any internal-looking host (`*.local`, mDNS names, lab-style or pet-name hosts, non-public domains) for confirmation rather than letting it pass. - **Private IPs.** RFC 1918 ranges (`10.`, `172.16-31.`, `192.168.`). Replace with documentation ranges: RFC 5737 (`192.0.2.x`, `198.51.100.x`, `203.0.113.x`) or RFC 2544 (`198.18.x`). A scanner that blocks all private ranges will also flag a "fake" `192.168.x` placeholder, that