commslisted

# comms ## Overview My bar for outward text. The reader owes me nothing: not their attention, not a reply, not a merge. So the message earns its own way in — short, specific, honest about what is and isn't true — and then it stops. **Drafts are shown to me and sent by me.** This skill never posts, mails or comments on its own. ## When to use - An email, especially to an institution or someone who did me a favour. - An issue, PR description or comment on a repo **I don't own**. - A follow-up or ping to a maintainer, a researcher, a group. - Release notes, a catalog entry, anything a user reads to decide something. - A reply on a review-bot thread (Copilot, codex, CodeRabbit) in someone's PR. ## What this skill does not own One canonical owner per rule — this one links, it doesn't copy. - **Commit messages, PR titles and bodies** → `eskills:standards`. - **UI strings and in-app copy** → `eskills:ux-bar`. - **Inclusive language**, in every locale → `eskills:standards`, which is the single source for it. It applies to everything here too. ## Rules - **One ask per message.** If there are two, the second one gets ignored — send it later or drop it. A message with no ask at all is fine; say so explicitly ("no need to reply"). - **One ping, then stop.** A follow-up is one short message, once, without urgency manufactured for the occasion. Never a batch of pings across several people or repos on the same day; never a second nudge because the first got no answer. Silen