Internal comms

Skill shinzoxD/knackbox/skills/writing/internal-comms

Write clear internal company communications — all-hands notes, policy updates, and reorg announcements. Use whenever the user asks for an internal email, Slack company update, org announcement, or memo to the whole company or department.From its SKILL.md

Install

npx -y skills add shinzoxD/knackbox --skill internal-comms

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.3 KB, 202 tokens by cl100k_base, as published. Nobody here has run it

Internal Comms

Internal messages compete with noise. Lead with what changes for the reader, when, and what they should do.

Structure

Subject / Slack title:

Opening (context in 1–2 lines)

What is changing
- …

Why (brief)

What you need to do
- …

Timeline
…

FAQ
…

Owner / questions channel

Rules

No surprise bury: hard news early, humanly.
Do not invent legal/HR policy; use provided facts.
Separate FYI from action-required.
Tone: respectful, specific, jargon-light.
Reorgs: reporting lines and customer impact; avoid gossip framing.
Offer short Slack + longer email variants when useful.

Edge cases

Bad news: acknowledge impact; concrete support paths if given.
Multi-audience: eng vs company-wide versions.
Rumors: stick to confirmed statements only.

What ships with it: 1 file

1.3 KB alongside SKILL.md

benchmarks/

prompts.json1.3 KB