plugins/writing-and-docs/skills/internal-comms/SKILL.md
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.).
npx skillsauth add arosenkranz/claude-code-config internal-commsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
To write internal communications, use this skill for:
To write any internal communication:
examples/ directory:
examples/3p-updates.md - For Progress/Plans/Problems team updatesexamples/company-newsletter.md - For company-wide newslettersexamples/faq-answers.md - For answering frequently asked questionsexamples/general-comms.md - For anything else that doesn't explicitly match one of the aboveIf the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms
tools
Lightweight orchestrator for spec-before-plan workflow. Use when starting a feature with ambiguous requirements. Walks SPEC.md → PLAN.md → execute, delegating to /superpowers:writing-plans and /superpowers:executing-plans. Invoke when asked to "spec this out", "spec-first", "spec and plan for X", or when feature requirements are vague.
tools
Problem Statement Co-Authoring Skill
development
Structure and maintain professional brag documents with clear templates for accomplishments, projects, and growth tracking. Use when documenting achievements, creating brag document entries, formatting accomplishments, or tracking career progress.
development
Analyze technical documentation for clarity, conciseness, and effectiveness using Google Technical Writing principles. Use when reviewing documentation, checking writing quality, improving docs, or providing writing feedback.