Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

I understand these skills can contain unsafe or unintended behavior, and I will review and security-scan before use. No warranty, suitability, or outcome is guaranteed.

Project ManagementFree Safe

team-communications

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when drafting internal company communications, status updates, newsletters, FAQs, incident reports, or summaries for leadership and teams.

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md

---
name: team-communications
description: Use when drafting internal company communications, status updates, newsletters, FAQs, incident reports, or summaries for leadership and teams.
category: Project Management
version: 1.0.0
tools: []
---

# Internal Communications

## Communication Types & Structure

Identify the communication type and apply the appropriate format:

**3P Updates** (Progress/Plans/Problems): Structure as weekly team summaries. Lead with key accomplishments, upcoming milestones, and blockers. Use active voice to credit team members.

**Newsletters** (Company-wide): Aggregate team updates into a digestible format. Include metrics, launches, and organizational news. Keep sections concise and link to detailed information.

**FAQ Roundups**: Compile common questions with clear, factual answers. Address confusion directly. Include relevant links and context.

**Incident Reports**: Document incident title, timeline, impact, root cause, and remediation steps. Use chronological detail and focus on learnings, not blame.

**Status Reports**: Open with headline, follow with 3-5 bullet points. Most important information first. Include relevant metrics and links.

## Tone & Style Standards

- Use "we" throughout. Position yourself as part of the company.
- Active voice for accomplishments: "Team X shipped the feature" not "The feature was shipped."
- Present tense for progress, future tense for plans.
- Concise sentences carrying actionable information. Eliminate filler.
- Professional but approachable. Avoid corporate jargon.
- Include metrics and performance data wherever possible.

## Workflow

1. **Identify communication type** from user request. Clarify if ambiguous.
2. **Gather context** from available sources (emails, notes, documents, data).
3. **Confirm scope**: team/audience, time period, what to include or exclude.
4. **Draft using the matched format**, following tone and length constraints precisely.
5. **Present and iterate** based on feedback.

## Anti-Patterns to Avoid

Writing without structure → Key info buried. Use headlines and bullet points.
Inventing metrics → Only include confirmed data from actual sources.
Passive voice in achievements → Hides who did the work. Always name the team.
Walls of text → Leadership scans, doesn't read. Keep it scannable.

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

1. Create a dedicated folder for this skill in your local skills library.
2. Place SKILL.md into that folder.
3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

1. Save SKILL.md in your local Syntic Code skills directory.
2. Keep related files in the same skill folder.
3. Run in a safe environment and validate outputs.

Source

https://github.com/alirezarezvani/claude-skills/blob/main/project-management/skills/team-communications/SKILL.md

Open Source Link

Project Management

Related Skills