Percerno Skillsbeta
← everything it can do · documents

Team Communications DOCX

Drafts, edits, and formats internal company communications such as 3P updates, newsletters, FAQs, and incident reports. It ensures the output matches specific company templates, uses a professional yet approachable tone, and highlights key metrics and progress.

4 uses this weeksource alirezarezvanilicence MIT
Quality gate: FAIL · better answers · measured 2026-10-24
Blind-judged against the bare model on 2 requests: average lift -4.5 points (specificity, structure, method, fit).
won 0/2, lift -4.5, tokens ×10.85
Security scan: clean · 2026-10-24 · 5 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Skriv en 3P-opdatering til udviklingsteamet. Vi har leveret den nye login-funktion, men vi har problemer med testmiljøet.”
“Kan du lave en nyhedsbrev til hele firmaet? Det skal dække den nye feriepolitik og vores resultater i sidste kvartal.”
“Opsummer hvad teamet har lavet denne uge til ledermødet. Hold det kort og præcist.”
“Write a 3P update for the backend team. Progress: we shipped the new API. Plans: start testing next week. Problems: we are short on QA resources.”
“Can you draft a company-wide newsletter for this month? Include the new office policy and the Q3 hiring goals.”
“Summarize what my team did this week for the leadership standup. Keep it to three bullet points.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

internal-communications3p-updatenewsletterstatus-reportincident-reportfaqleadership-updateteam-updatecorporate-writing

Not for

Do not use this skill for external marketing content, public-facing blog posts, or customer-facing support emails, as these require different tones and formats. It is not for general creative writing or personal emails.

Details

When it is the right choice

Use this skill when the user asks to write, summarize, or format updates for internal audiences like leadership, teammates, or the whole company. It is ideal for creating 3P (Progress/Plans/Problems) reports, company-wide newsletters, or incident post-mortems. It also handles requests to summarize recent team work or answer common internal questions.

The full recipe the assistant reads

Internal Comms

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.

Routing

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.

Workflow

  1. Read the reference file for the matched type. Follow its formatting exactly.
  2. Gather inputs. Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.
  3. Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
  4. Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
  5. Present the draft and ask if anything needs to be added, removed, or reworded.

Tone & Style (applies to all types)

  • Use "we" — you are part of the company.
  • Active voice, present tense for progress, future tense for plans.
  • Concise. Every sentence should carry information. Cut filler.
  • Include metrics and links wherever possible.
  • Professional but approachable — not corporate-speak.
  • Put the most important information first.

When tools are unavailable

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-Patterns

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?

Related Skills

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
Files in this skill (6)
  • LICENSE
  • SKILL.md
  • references/3p-updates.md
  • references/company-newsletter.md
  • references/faq-answers.md
  • references/general-comms.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path project-management/skills/team-communications, licence MIT. The upstream licence file ships inside the skill.