— Skill
Claude Internal Comms
Stop rewriting the same weekly update from scratch — Claude loads your company’s 3P / newsletter / FAQ / incident patterns instead of inventing a new format every Monday.
ClaudeVerifiedAccess: Apache-2.0 skill artifact is free on GitHub; Claude / Claude Code runtime may need your host plan.
- What changes
- Routes internal writing to the right guideline (3P updates, newsletters, FAQs, status/leadership/project/incident reports) so tone and structure match how your org already communicates.
- When
Use Anthropic’s internal-comms skill when the deliverable is an internal company update — 3P (Progress / Plans / Problems), newsletter, FAQ, status report, leadership update, project update, or incident report — and the format should match how your org already writes.
Good fits:
- Monday team 3P with real blockers, not vibes.
- Company newsletter section drafts from a bullet dump.
- FAQ answers that stay on-message.
- Incident or project updates that need a fixed structure.
Skip it for external marketing copy (
marketing-skills), long public docs (claude-doc-coauthoring), or slide decks (claude-pptx).- How to start
- Enable internal-comms from anthropics/skills (example-skills / Apache-2.0). Name the comms type (3P, newsletter, FAQ, incident), dump facts, and ask Claude to follow the matching examples/ guideline.
Copy dock
Ready to adapt. Paste. Run. Use.
Name the format first (3P / newsletter / FAQ / incident) — then dump facts.
EXAMPLE prompt
Attach the internal-comms skill. Type: [3P update | company newsletter | FAQ | status | leadership | project | incident]. Audience: [team / exec / company]. Tone: [direct | calm | celebratory]. Facts dump (unordered): - … Forbidden: invented metrics, fake quotes, blame language on incidents. Load the matching examples/ guideline, then draft. End with a short verify checklist.
Keep in mind
- State the comms type up front so the skill loads the matching guideline
- Dump facts unordered; forbid invented metrics or stakeholder quotes
- Ask for a draft in the company format, then a short verify checklist
Next pick
- Claude DOCX skillDraft, revise, and extract inside real .docx structure (headings, tables, captions) instead of dumping markdown someone has to reformat all afternoon.Open →
- Computer-use QADrive login → core action → confirmation in a real browser/desktop session. Catch dead buttons and broken redirects that unit tests never see.Open →
- Stop shipping purple AI landing pagesAttachable skill for bold type, real visual anchors, and a hero budget — so agents stop defaulting to Inter + gradient sludge.Open →