Internal Communications Writer
anthropics/skills
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…
Plan and write the communications for a layoff or restructure with clarity and dignity.
Install Layoff Communication
$ npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills layoff-communication --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/layoff-communication .claude/skills/layoff-communication && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "layoff-communication" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/layoff-communication into .claude/skills/layoff-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "layoff-communication", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/layoff-communicationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills layoff-communication --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/layoff-communication .agents/skills/layoff-communication && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "layoff-communication" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/layoff-communication into .agents/skills/layoff-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "layoff-communication", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills layoff-communication --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/layoff-communication .cursor/skills/layoff-communication && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "layoff-communication" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/layoff-communication into .cursor/skills/layoff-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "layoff-communication", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/layoff-communication--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills layoff-communication --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/layoff-communication .gemini/skills/layoff-communication && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "layoff-communication" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/layoff-communication into .gemini/skills/layoff-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "layoff-communication", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills layoff-communicationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/layoff-communication .github/skills/layoff-communication && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "layoff-communication" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/layoff-communication into .github/skills/layoff-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "layoff-communication", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills layoff-communication --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/layoff-communication .opencode/skills/layoff-communication && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "layoff-communication" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/layoff-communication into .opencode/skills/layoff-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "layoff-communication", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
layoff-communication- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 565 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan and write the communications for a layoff or restructure with clarity and dignity.
- Asked to communicate a layoff
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Write a RIF/redundancy announcement
What it does
Layoff Communication is an agent skill from mohitagw15856/pm-claude-skills. Plan and write the communications for a layoff or restructure with clarity and dignity. Use when asked to communicate a layoff, write a RIF/redundancy announcement, prepare manager talking points for letting people go, or plan workforce-reduction comms. Produces a comms package — sequencing plan, the all-hands/company message, the affected-employee message, a manager guide with talking points, a staying-team message, and an external/press holding line.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Internal communications. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to communicate a layoff
- Write a RIF/redundancy announcement
- Prepare manager talking points for letting people go
- Plan workforce-reduction comms
Example prompts
- “/layoff-communication”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Layoff Communication loads about 1.2k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 565 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 565 words, ~1,162 tokens.
Download SKILL.mdSave it as
.claude/skills/layoff-communication/SKILL.md (or your agent's skills folder).- name
- layoff-communication
- description
- Plan and write the communications for a layoff or restructure with clarity and dignity. Use when asked to communicate a layoff, write a RIF/redundancy announcement, prepare manager talking points for letting people go, or plan workforce-reduction comms. Produces a comms package — sequencing plan, the all-hands/company message, the affected-employee message, a manager guide with talking points, a staying-team message, and an external/press holding line.
Layoff Communication Skill
A layoff is the hardest thing a company communicates, and people remember exactly how it was handled. This skill plans and writes the full set of messages so affected people learn first and with dignity, managers know what to say, and the remaining team isn't left in fear — clear, humane, and consistent across every audience.
Note: this produces communications, not legal advice. Layoffs carry legal/regulatory requirements (notice periods, protected classes, severance, WARN-type rules) that vary by jurisdiction — the output flags where to involve HR and legal counsel and must be reviewed before use.
Working from a brief
Given "we're cutting 15% next week", produce the full package anyway — infer the likely audiences, sequence, and questions, label assumptions, and bracket the specifics (numbers, dates, severance terms) to confirm. Never withhold for missing detail; flag every legally sensitive point for HR/legal review.
Required Inputs
Ask for these only if they aren't already provided (else infer and label):
- The decision — scale, which teams/roles, and the timing.
- The why — the honest business reason (be specific, not euphemistic).
- Support offered — severance, benefits continuation, outplacement, references.
- Logistics — how/when affected people are told, access timing, and who delivers each message.
- Constraints — legal/regulatory requirements and approvals (flag for counsel).
Output Format
Layoff Communications: [company]
1. Sequencing plan — who hears what, from whom, and in what order (affected people first and individually, then the staying team, then external) — with timing so no one finds out via rumour or the wrong channel.
2. Affected-employee message — delivered live where possible, with a written follow-up: clear that their role is ending, the reason, what support they get, exact next steps and dates, and where to get help. Direct, respectful, no false hope, no jargon.
3. Company / all-hands message — the leader's message to everyone: what's happening, why, accountability, care for those leaving, and what comes next for the team. Owns the decision; doesn't hide behind passive voice.
4. Manager guide & talking points — what managers say in the conversations, what to do and avoid, how to answer the hard questions, and how to support both those leaving and those staying.
5. Staying-team message — acknowledges the loss, explains what changes, and rebuilds stability and direction (survivors need honesty, not forced positivity).
6. External / press holding line — a brief, respectful statement if it becomes public.
7. FAQ — the questions everyone will ask (pay, benefits, references, timeline, why-me, why-now) with honest answers.
Show full SKILL.md (167 more words)Show less
Quality Checks
- Affected people are told first, individually, and with dignity — never by mass email or last
- The business reason is stated honestly and specifically, not in euphemism
- Support (severance, benefits, outplacement, references) is concrete and clear
- Managers have actual words and answers, not just "be empathetic"
- The staying team gets honesty and direction, not forced positivity
- Every legally sensitive element is flagged for HR/legal review
Anti-Patterns
- Do not hide behind euphemism ("rightsizing", "graduating talent") — name it plainly and humanely
- Do not let affected people learn via the all-hands, press, or rumour — sequence individuals first
- Do not use passive voice to dodge accountability — leadership owns the decision
- Do not over-promise or give false hope about reversal or rehire
- Do not treat this as legal advice — flag jurisdiction-specific obligations for counsel
Based On
Workforce-change communication practice — dignity-first sequencing, honest rationale, concrete support, manager enablement, and survivor communication.
Example Trigger Phrases
- "Communicate a layoff."
- "Write a RIF/redundancy announcement."
- "Prepare manager talking points for letting people go."
- "Plan workforce-reduction comms."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/layoff-communication of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Layoff Communication next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Layoff Communication this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| My Weekly Reportmeain/dotfiles | 285 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Updatesjtenniswood/espframe | 208 | — | ~527 | Automated safety check: Pass | Custom licence | |
| Updateakseolabs-seo/AK-Threads-booster | 275 | — | ~1.1k | Automated safety check: Notes | MIT |
Similar skills
- Official
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
My Weekly Report
meain/dotfiles
Generate a concise weekly status update in team format. An agent skill from meain/dotfiles.
Updates
jtenniswood/espframe
Summarize user-facing changes made to this project over the last 7 days.
Update
akseolabs-seo/AK-Threads-booster
Check AK-Threads-Booster for upstream GitHub updates, safely fast-forward the local skill repo, or install an opt-in weekly Codex automation that keeps the skill on the latest version.
Weekly Status Report
sgharlow/claude-code-recipes
Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Layoff Communication
What does Layoff Communication do?
Plan and write the communications for a layoff or restructure with clarity and dignity. Layoff Communication is an agent skill from mohitagw15856/pm-claude-skills. Plan and write the communications for a layoff or restructure with clarity and dignity.
When should I use Layoff Communication?
Layoff Communication fits situations like: asked to communicate a layoff; write a RIF/redundancy announcement; prepare manager talking points for letting people go; plan workforce-reduction comms.
How do I install Layoff Communication in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a claude-code`. Or copy the skill folder (skills/layoff-communication in mohitagw15856/pm-claude-skills) into .claude/skills/layoff-communication in your project. Claude Code loads it when a task matches its description.
How do I install Layoff Communication in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a codex`. Or copy the skill folder (skills/layoff-communication in mohitagw15856/pm-claude-skills) into .agents/skills/layoff-communication in your project. Codex loads it when a task matches its description.
Can I use Layoff Communication in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill layoff-communication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/layoff-communication, .gemini/skills/layoff-communication, .github/skills/layoff-communication and .opencode/skills/layoff-communication in your project.
What does Layoff Communication need to run?
SKILL.md names no scripts, command-line tools or credentials: Layoff Communication is instructions for the agent only.
Does Layoff Communication access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Layoff Communication safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Layoff Communication use?
Layoff Communication is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Layoff Communication use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Layoff Communication?
Skills that share tags, products or a category with Layoff Communication: Internal Communications Writer (anthropics/skills, 180k stars), Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars), My Weekly Report (meain/dotfiles, 285 stars) and Updates (jtenniswood/espframe, 208 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Layoff Communication?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.