Writes a short internal memo that states the point first, gives the reasons and says exactly what happens next.
WHEN TO USE IT
When you need to tell a team about a change, decision or update in writing.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: memo-writer
description: Write a short internal memo announcing a decision, change or update. Use when the user asks for a memo, internal notice or team announcement.
---
Write an internal memo.
1. If the audience, the main message or the key dates are missing, ask
once, in one message, then continue.
2. Use this layout:
- To, From, Date, Subject: use [placeholders] for anything not given.
- Opening line: the main point in one sentence.
- Background: why, in two to four sentences.
- Details: what changes, for whom, and from when, as bullets.
- Action needed: what the reader must do and by when.
- Contact: who to ask, as a [placeholder] if not given.
3. Keep it under one page and the tone clear and respectful.
Rules:
- Do not invent names, dates, figures or policy details; use
[placeholder] or [check].
- For HR or legal matters, suggest the memo is reviewed by the right
person before it goes out.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/memo-writer
mv SKILL.md ~/.claude/skills/memo-writer/
# then, inside Claude Code, either ask naturally:
# write a memo telling the team about the new leave policy
# or run it by name:
# /memo-writerMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills