mcpbeat

Internal Comms

lingxling/internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

This is a copy. The original lives at jayzeedesign/internal-comms.

6k tokens
context cost
the whole folder, loaded on every use
7
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/lingxling/awesome-skills-cn --skill internal-comms

The instruction itself

3 sections, as written by the author

When to use this skill

To write internal communications, use this skill for:

  • 3P updates (Progress, Plans, Problems)
  • Company newsletters
  • FAQ responses
  • Status reports
  • Leadership updates
  • Project updates
  • Incident reports

How to use this skill

To write any internal communication:

  • Identify the communication type from the request
  • Load the appropriate guideline file from the examples/ directory:
  • examples/3p-updates.md - For Progress/Plans/Problems team updates
  • examples/company-newsletter.md - For company-wide newsletters
  • examples/faq-answers.md - For answering frequently asked questions
  • examples/general-comms.md - For anything else that doesn't explicitly match one of the above
  • Follow the specific instructions in that file for formatting, tone, and content gathering

If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.

Keywords

3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms

How to use it

Copy the folder

Take lingxling/internal-comms from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.