internal-comms organizes workplace material into a format suited to its audience. It routes requests to guidance for 3P updates, company newsletters, FAQs, or general communications. A weekly update and a policy explanation need different inputs and structures. Be explicit about what happened, what is planned, and what remains unresolved.
Install and invoke
Send these two commands in the Claude Code chat input, one at a time. They are plugin commands, not shell commands for your operating system. The second installs the official collection containing internal-comms.
/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skills
In your project conversation, ask Claude to “use internal-comms” and supply the task or files. The prompt below is an editable starting example. Installing the collection supplies instructions and resources; it does not supply your source material or guarantee that every runtime dependency is installed locally. If the skill is missing, check that its plugin is installed, enabled, and loaded in the current session. Do that before troubleshooting the requested output.
Start with a scoped weekly update
Use internal-comms to write a 3P update for the payments team covering September 14–20.
The audience is engineering leadership and adjacent teams.
I will supply completed work, next-week plans, and blockers.
Use Progress, Plans, and Problems, with one to three sentences per section.
Keep supplied metrics and invent none. Produce a draft without sending it.
Provide the team and reporting dates before listing the material. Separate last week's outcomes from next week's plans. “Released” is different from “still being tested.” For cross-team readers, replace unexplained ticket numbers with enough context to show why the change matters.
The official 3P example favors concise, factual updates. One to three sentences per section should not become one enormous sentence containing every detail. Select the milestone, next priority, and blocker that the audience needs to act on. Supporting detail can remain behind links. If there are no problems, confirm that rather than inventing a concern to fill the section.
Give FAQs authoritative material
For a policy change, try: “Use internal-comms to derive five employee questions from this announcement. Answer only from the announcement and mark anything requiring an owner's response.” The FAQ guidance pairs a short question with a one- or two-sentence answer and encourages links to authoritative announcements, documents, or emails.
Consider employees in different roles instead of focusing only on the requesting team's concerns. Uncertain dates, permissions, and commitments should remain visibly uncertain. An approachable tone does not make an unsupported answer true. Integrations can help retrieve company material, but installing the skill does not authorize them; provide the relevant text when access is unavailable.
Before delivery, check names, reporting periods, owners, metric definitions, and whether the next actions are clear. Ask for a send-ready draft and a separate list of missing information. Actual distribution belongs to your communication workflow. If your company already has a template or preferred tone, supply it at the start: the bundled examples are writing resources, not evidence that the agent knows your organization's internal conventions.
Edit for the actual recipients
The same weekly notes can become an internal team update or a company-wide message. The first needs owners and specific blockers; the second needs impact, risk, and next steps. State who will read the piece and what they already know. Otherwise the agent may copy ticket IDs and internal shorthand into an update that many readers cannot interpret.
Before sending, check the date range, completion state, metric definition, owner, and person being asked for help. Keep “planned for release,” “rolling out,” and “released” distinct. If the material does not establish whether a problem is resolved, leave it unconfirmed and ask its owner; a confident tone is not evidence of completion.
Give an FAQ a responsible escalation path
A policy FAQ should not answer exceptions that the owner has not decided. Sort questions into those answered by the source announcement, those needing a department's confirmation, and those needing a contact path for readers. Write concise answers with authoritative links for the first group and explicit follow-ups for the others. Have the responsible person resolve them before publication. Apply the same rule to metrics and promises in newsletters: unknown facts should remain unknown, however fluent the draft sounds.
If the skill is missing after setup
Adding a marketplace only registers the source. internal-comms is a skill inside a plugin bundle, not the plugin name after /plugin install. A user who tried internal-comms@anthropic-agent-skills got a not-found error. Install example-skills@anthropic-agent-skills as shown above, refresh the session or check that the plugin is enabled, then test it with a small status update.