Write internal announcements, progress updates and retrospectives for the right audience.
Internal communication written to be useful to its readers: status reports, leadership updates, company newsletters, FAQs and incident reports each have their own craft. The same news lands differently for engineers, executives or an all-hands audience — what to lead with, what to drop, what tone fits. It confirms audience, purpose and cadence with you before writing.
Company-specific names, cadences and templates stay as blanks it asks about rather than invents. Deliverables are ordinary documents — Word, Markdown or Notes — with the needed data and sources attached. It only writes: sending, posting and sharing stay your actions through the app's own surfaces.
Examples describe the request and the shape of the expected deliverable; they are not completed run results.
Here are three changes and one slip this week: the VP version must foreground risk and the decision needed, the all-hands version plain with context — produce both, keeping unsourced figures as placeholders.
Two audience-calibrated workspace documents, the slip stated honestly and unverified figures marked for sourcing.
From our incident postmortem notes, write a no-blame report: timeline, blast radius, recovery steps and follow-ups as four sections, with nothing beyond the record.
A complete report draft where every impact and action traces to the postmortem, with unconfirmed root causes explicitly left open.
iOS · Android
iOS
Android
Apache-2.0
Apache-2.0 (per-skill LICENSE.txt)
The pinned skill subtree and shipped references were audited; full applicable license and per-file adaptation/asset notes are preserved under references/licenses/ and references/PROVENANCE.md.
Publication commit 25e07dbeeb, audited source 84c524b6fb; catalog digest iOS 46196ba57ed7… · Android 16de89d019e2….
Version records ship with the signed catalog; the target and released versions are shown below.
