{"id":101471,"plugin_id":"plugins_6af4333b6f008191806d76e5f43ec5f9","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-17T12:11:35.596Z","digest":"a967e9cba0aef076d45a0af29268774972278c49cbce5718b20c7ffb1d31ed9e","against":null,"payload":{"description":"Write internal communications — status reports, leadership updates, incident reports, project updates, FAQs, and newsletters — in clear, consistent formats. Use whenever drafting an internal update, announcement, or report for a team or company.","included_files":[],"name":"internal-comms","skill_md_contents":"---\nname: internal-comms\ndescription: Write internal communications — status reports, leadership updates, incident reports, project updates, FAQs, and newsletters — in clear, consistent formats. Use whenever drafting an internal update, announcement, or report for a team or company.\nlicense: Apache-2.0\ncompatibility: Tines 3B\n---\n\n# Internal communications\n\nGood internal comms respect the reader’s time. Lead with the point, keep it skimmable, and say only what the audience needs to act or stay informed.\n\n## Principles\n\n- **Lead with the takeaway (BLUF).** The first line should carry the most important information — the decision, the status, the ask. Don’t bury it under context.\n- **Know the audience.** A leadership update is terser and more outcome-focused than a team update. Match the altitude.\n- **Make it skimmable.** Short paragraphs, headers, and bullets. Bold the few words that matter.\n- **Be specific.** Dates, owners, numbers, and links beat adjectives. “Shipped to 100% on Tuesday” beats “made great progress.”\n- **State the ask.** If you need a decision, a review, or nothing at all, say which.\n\n## Formats\n\n**3P update (Progress / Plans / Problems)** — a recurring team update:\n\n- _Progress_ — what got done since the last update.\n- _Plans_ — what’s next, with rough timing.\n- _Problems_ — blockers, risks, and where you need help.\n\n**Status report** — headline status (on track / at risk / off track), a one-line summary, then key updates, risks, and next steps.\n\n**Leadership update** — outcomes and decisions, not activity. Open with the headline, then progress against goals, the top risks, and any decisions you need from them. Keep it short.\n\n**Incident report** — a summary line (what happened, impact, current state), then _impact_ (who/what was affected, for how long), a _timeline_ of key events, _root cause_, _remediation_ (what fixed it), and _follow-ups_ (owners + dates to prevent recurrence). Write blamelessly — focus on systems, not people.\n\n**Project update** — where the project stands against its plan: milestones hit, what’s next, risks, and changes to scope or timeline.\n\n**FAQ** — group by theme; lead each answer with the direct response, then the detail. Anticipate the real questions, including the uncomfortable ones.\n\n**Newsletter** — a short, scannable digest: a brief intro, themed sections with headers, and clear links out for depth. Celebrate wins concretely and credit the people involved.\n\n## Tone\n\nClear, warm, and direct. Plain language over jargon. Confident without overclaiming — if something is uncertain or went wrong, say so plainly and say what happens next.\n\n---\n\n_Adapted by 3B from Anthropic’s “internal-comms” skill (github.com/anthropics/skills), © Anthropic PBC, licensed under Apache-2.0. Modified for 3B._\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}