メニュー
Load when a task needs internal communications such as status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, or project updates; skip public marketing copy.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | internal-comms |
| description | Load when a task needs internal communications such as status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, or project updates; skip public marketing copy. |
| license | Complete terms in LICENSE.txt |
| metadata | {"source":"anthropics/skills skills/internal-comms","upstream_commit":"690f15cac7f7b4c055c5ab109c79ed9259934081","adaptation":"Examples moved to references/ and trigger text made organization-neutral."} |
To write internal communications, use this skill for:
To write any internal communication:
references/ directory:
references/3p-updates.md - For Progress/Plans/Problems team updatesreferences/company-newsletter.md - For company-wide newslettersreferences/faq-answers.md - For answering frequently asked questionsreferences/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
Load when a task needs a throwaway prototype, state-model sanity check, UI variant, image-assisted visual mockup, mock interaction, or playable design; do not use for production feature work.
Load when a user describes a Web animation or motion effect without knowing its name and needs the precise term or close alternatives; use only for naming, not design, implementation, or review.
Load when a frontend task needs Apple-platform design guidance or physical, gesture-driven, velocity-aware, interruptible interaction; skip generic visual styling and use review-animations for report-only motion review.
Load when a task needs polished product UI, web pages, landing pages, dashboards, React components, HTML/CSS layouts, or styling; skip routine frontend logic and reports.
Load when a task needs React or Next.js frontend logic, component patterns, state, forms, routing, accessibility, or responsive behavior; use frontend-design for visual direction.
Load when an existing Web product, especially a dashboard, dense-data view, or multi-step app, needs a deep evidence-backed experience review; report findings only, and use design-taste-frontend for marketing-page direction, code-review for source diffs, web-design-guidelines for checklist compliance, or frontend-design for implementation.