bundles/content/skills/internal-comms/SKILL.md
Resources for writing internal communications in company-preferred formats. Use when asked to draft status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, or project updates.
npx skillsauth add shipshitdev/library 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
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.