Draft and edit internal updates, newsletters, FAQs, and incident reports using the appropriate reference format. Turn supplied notes or information retrieved through connected tools into concise communications tailored to the audience and reporting period.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like "write my update" or "summarize what my team did this week" should trigger this skill.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Originally contributed by maximcoding — enhanced and integrated by the claude-skills team.
Write polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.
Identify the communication type from the user's request, then read the matching reference file before writing anything:
| Type | Trigger phrases | Reference file |
|---|---|---|
| 3P Update | "3P", "progress plans problems", "weekly team update", "what did we ship" | references/3p-updates.md |
| Newsletter | "newsletter", "company update", "weekly/monthly roundup", "all-hands summary" | references/company-newsletter.md |
| FAQ | "FAQ", "common questions", "what people are asking", "confusion around" | references/faq-answers.md |
| General | anything internal that doesn't match above | references/general-comms.md |
If the type is ambiguous, ask one clarifying question — don't guess.
If the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Writing updates without reading the reference template first | Output won't match company format — user has to reformat | Always load the matching reference file before drafting |
| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |
| Using passive voice for accomplishments | "The feature was shipped" hides who did the work | "Team X shipped the feature" — active voice credits the team |
| Writing walls of text for status updates | Leadership scans, doesn't read — key info gets buried | Lead with the headline, follow with 3-5 bullet points |
| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |
| Skill | Relationship |
|---|---|
project-management/senior-pm | Broader PM scope — status reports feed into PM reporting |
project-management/meeting-analyzer | Meeting insights can feed into 3P updates and status reports |
project-management/confluence-expert | Publish comms as Confluence pages for permanent record |
marketing-skill/content-production | External comms — use for public-facing content, not internal |
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.