Internal Comms

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — None. Installing this skill needs no account, no key and no payment, and using it needs nothing either: it is a set of writing formats. If I have tools like Slack, Drive, email or a calendar already connected, its guidelines may suggest reading my own context from them; otherwise the agent asks me for the content. Install "Internal Comms" for me. It helps write internal communications in the formats bundled in its examples folder: 3P updates (Progress, Plans, Problems: short, data-driven team updates with a strict three-section format), company newsletters (grouped bullet summaries of company-wide news), FAQ answers (the questions many employees are asking, with short sourced answers), and a general format for anything else (ask about audience, purpose and tone first, then write clearly with the most important information first). The main file identifies the communication type and loads the matching guideline file; for status reports, leadership updates, project updates and incident reports it routes to the closest of these formats, and asks for clarification when nothing matches. Repository: https://github.com/anthropics/skills (the skill is the whole skills/internal-comms/ folder at the pinned commit: SKILL.md, LICENSE.txt and the examples/ folder, 6 files in total) Pinned version: install the code at commit dbd4588f9e1033efb41dad4bef2f7947c8993d44 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/anthropics/skills into a temporary folder, check out commit dbd4588f9e1033efb41dad4bef2f7947c8993d44, and copy the skills/internal-comms/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - LICENSE.txt: SHA-256 bc6b3af2f331cbc7fb0da1344efb2cbe5877a31498b4d70dbc7000f3405a1362 - SKILL.md: SHA-256 067b7587a344a928fc6534ef66b1bcd591fc7c26d207ea7ca3334aeb678d6475 - examples/3p-updates.md: SHA-256 087e4363c0f3513728a7e695eeb9ead5c3ecd12a4681b59340691180e65b68fc - examples/company-newsletter.md: SHA-256 30f81cfbdb03858a006169c72169024089c7c5d3d32611d337782da4f38c86b5 - examples/faq-answers.md: SHA-256 5ecd3356cd6666937f2ebefa753253edfdbdca15e368d07baf398bfcced72484 - examples/general-comms.md: SHA-256 4d3a4bb198a77626bcf018e96b2b45a2dbabed172d4ade0fcd70d23ae8a47a47 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 6 files: SKILL.md, LICENSE.txt (Apache-2.0) and four guideline files under examples/ (3p-updates, company-newsletter, faq-answers, general-comms). There is no script, no code and no configuration in it; it is writing guidance only. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. - At use time, the skill itself sends nothing and publishes nothing: it drafts a communication in the requested format. Its guidelines suggest gathering context from tools I already connected (Slack, Drive, email, calendar) or directly from me; any sending of the finished text is done by me, through my own channels. - Do not write any communication, do not read any connected tool, and do not use the skill in any way during this install: using it is a separate step that only starts when I actually ask for an internal communication. 3. When I say "yes, install", install it as a skill: copy the whole internal-comms folder into the agent's skills directory, in a folder named exactly "internal-comms", keeping its 6 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: internal-comms), the 6 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: nothing is needed from me — no account, no key, no setup; the finished text is always sent by me, not by the skill; using the skill is a separate step that only starts when I ask for it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.