Install
Identify the communication type then load the matching file from examples/Who it's for
internal-comms is for people asked to write internal copy: status reports, updates for leadership, 3P updates, company newsletters, FAQ, incident notes, project progress, and the like. It is a set of resources for writing in the company's usual format, not a tool for external press releases.
The tighter fit: you already know this is an internal document and can name the type. The official order is to identify the comms type first, then load the matching guide from examples/ and write to that file's format and tone. Named guides include examples/3p-updates.md, examples/company-newsletter.md, examples/faq-answers.md, and examples/general-comms.md when the match is not clear.
It does not fit being an installer. The guide gives no install command and does not say that copying it into some directory makes it usable. If the current assistant cannot yet load these guides by type, the existing guide stops here; do not reverse-engineer an install path from the page address. It also does not fit forcing a “generic official-sounding piece” when the type is unclear without asking first.
First try in 3 minutes
The official first path is to start an internal draft, not to install. The guide page is
https://raw.githubusercontent.com/anthropics/skills/main/skills/internal-comms/SKILL.md
Follow only the steps on that page. Do not write an install phrase that never appears.
Prerequisite: the current assistant can already work as internal-comms, and you have practice material that will not go outside, for example this week's Progress / Plans / Problems. There is no install command, so the “location” is the draft in this conversation, not a guessed skill directory.
Low-risk first task: ask clearly for a 3P update, and say draft first, do not send. The assistant should identify the type as 3P, then load examples/3p-updates.md. Do not let it hand in a final draft before it names which guide it will follow. Success signal: it names 3P (Progress, Plans, Problems) and starts drafting to that guide, instead of writing an external newsletter or an incident report.
After writing, review only in the conversation. The guide does not write steps for sending to email or chat tools, so the first try stops at “type is correct, draft is readable.” If what you want is not 3P, say the real type and let it identify again.
Use cases
Case 1: Write 3P or another named internal type. Applicable types also include company newsletter, FAQ, status report, update for leadership, project update, and incident notes. Matching guides are examples/3p-updates.md, examples/company-newsletter.md, examples/faq-answers.md, and so on. This fits when you can already match one of those. The guide does not list each file's heading levels in this text, so you can only “load the file first, then write to the file.” If the assistant never names a guide, ask it to load first. The guide page is still
https://raw.githubusercontent.com/anthropics/skills/main/skills/internal-comms/SKILL.md
Case 2: Ask first when the type does not match, or fall back to a general draft. examples/general-comms.md is for other content that does not match clearly. If even that file is a poor fit, the guide requires asking for the expected format or more context, not inventing a new template. This fits when you want an internal notice whose name is not on the list above. The guide does not write a question list; the first time, answer format, audience, and length, then let it draft. Until the format is confirmed, do not treat it as text ready to blast to a group.
Boundaries
No install command: do not treat the page path as an installer. Use boundary: for internal comms; named types are 3P, company newsletter, FAQ, status report, leadership update, project update, and incident notes. Flow boundary: identify the type first, then load a guide from examples/. If it does not match, ask, or use examples/general-comms.md. File boundary: the only guide names you can check are the ones above; do not invent filenames. The guide does not write how to hook into a real company template library, and does not write send or publish steps; a draft is not already sent.