About Writing and Communication
A model can produce fluent prose on request; what it lacks is a process and a format. The skills here supply both, so the writing fits its reader and its company rather than reading like a first draft.
What is here
- doc-coauthoring turns writing a document with Claude into three stages. First Claude gathers context from you. Then it builds the document section by section through brainstorming and edits. Finally it tests the result on a fresh Claude instance that has none of the conversation’s context, to see whether a new reader actually understands it. It suits design docs, technical specs, proposals and decision documents.
- internal-comms gives Claude fixed house formats for company communications: 3P updates (progress, plans, problems), company newsletters, FAQ roundups and general announcements, each with an example file that Claude loads only when that format is asked for.
How to choose
They solve different problems. Use doc-coauthoring when the document is long, matters, and will be read by people who were not in the room; its reader test is the part most writing workflows skip. Use internal-comms when the shape of the message is already decided by your company and the job is to fill it consistently. Its formats are a starting point: the skill is easy to fork and replace with your own templates.
Both are prose-only. They run no scripts and touch nothing on the machine, so they work in a plain chat as well as in Claude Code.