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 emliunix/home.conf 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
development
Manages thinking patterns and mental models when switching between different topics or modes. Use when (1) switching from analysis to design, (2) switching from exploration to validation, (3) switching from reading to writing, (4) any topic transition where thinking approach must change, (5) user signals "we're going to sketch/design/build" after analysis phase.
development
Systematic codebase investigation producing structured exploration files (Notes → Facts → Claims). Use when researching unknown systems, tracing code paths, or documenting architecture.
testing
Collaborative design workflow for architecture and system design. Use when the user wants to design or redesign a system, component, or feature. Triggers on phrases like "design", "architecture", "how should we", "what's the best way to", or when the user asks for tradeoff analysis. This skill is for exploration and decision-making, not implementation.
development
Change plan workflow for non-trivial code changes. Create, review, and track changes before implementation.