internal-comms-tone-by-communication-type

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

5 stars

Best use case

internal-comms-tone-by-communication-type is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using internal-comms-tone-by-communication-type should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/tone-by-communication-type/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/business/communication/internal-comms/tone-by-communication-type/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/tone-by-communication-type/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How internal-comms-tone-by-communication-type Compares

Feature / Agent	internal-comms-tone-by-communication-type	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

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

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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]"

Related Skills

stakeholder-comms

from vamseeachanta/workspace-hub

Draft stakeholder updates tailored to audience -- executives, engineering, customers, or cross-functional partners

internal-comms

from vamseeachanta/workspace-hub

Create professional internal communications including memos, announcements, newsletters, and company updates. Use for employee communications, policy announcements, team updates, and organizational messaging.