Skip to content
Back to skills

Tone By Communication Type

ASecurity

Sub-skill of internal-comms: Tone by Communication Type (+2).

  • 17 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 9, 2026
documentationgo

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add vamseeachanta/workspace-hub --skill tone-by-communication-type --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tone By Communication Type?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Tone By Communication Type
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vamseeachanta-tone-by-communication-type/badge)](https://www.skillsdirectory.com/skills/vamseeachanta-tone-by-communication-type)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: internal-comms-tone-by-communication-type
description: 'Sub-skill of internal-comms: Tone by Communication Type (+2).'
version: 2.0.0
category: business
type: reference
scripts_exempt: true
---

# Tone by Communication Type (+2)

## Tone by Communication Type


| Type | Tone | Example Phrase |
|------|------|----------------|
| Announcements | Professional, clear | "We're pleased to announce..." |
| Newsletters | Warm, engaging | "Great progress this month!" |
| Policy | Formal, precise | "Effective immediately, all employees must..." |
| Executive | Authentic, inspiring | "I want to share my perspective on..." |
| Crisis | Calm, direct | "Here's what we know..." |


## Best Practices


**DO:**
- Lead with the most important information
- Use bullet points for scanability
- Include specific dates, names, and actions
- Provide context for decisions
- End with clear next steps
- Keep paragraphs short (2-3 sentences)

**DON'T:**
- Bury important information
- Use jargon without explanation
- Send without proofreading
- Forget mobile readers (keep formatting simple)
- Assume prior knowledge
- Be vague about deadlines or responsibilities


## Subject Line Formulas


**Announcements:**
- "[Action]: [Topic] Effective [Date]"
- "Introducing: [New Thing]"
- "Update: [Topic] Changes"

**Newsletters:**
- "[Team] Weekly: [Date Range]"
- "[Month] Update: [Key Theme]"

**Urgent:**
- "[URGENT] [Brief Description]"
- "[ACTION REQUIRED] [Topic] by [Date]"

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.