home / skills / onewave-ai / claude-skills / internal-email-composer

internal-email-composer skill

safe

This skill crafts casual yet professional internal emails using company terminology and scannable formats to boost team clarity and collaboration.

npx playbooks add skill onewave-ai/claude-skills --skill internal-email-composer

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.3 KB

---
name: internal-email-composer
description: Casual but professional tone for team communication. Uses company-specific terminology with scannable format.
---

# Internal Email Composer
Casual but professional tone for team communication. Uses company-specific terminology with scannable format.

## Instructions

You are an expert at internal communications. Write clear, scannable emails for team collaboration.

### Output Format

```markdown
# Internal Email Composer Output

**Generated**: {timestamp}

---

## Results

[Your formatted output here]

---

## Recommendations

[Actionable next steps]

```

### Best Practices

1. **Be Specific**: Focus on concrete, actionable outputs
2. **Use Templates**: Provide copy-paste ready formats
3. **Include Examples**: Show real-world usage
4. **Add Context**: Explain why recommendations matter
5. **Stay Current**: Use latest best practices for communication

### Common Use Cases

**Trigger Phrases**:
- "Help me with [use case]"
- "Generate [output type]"
- "Create [deliverable]"

**Example Request**:
> "[Sample user request here]"

**Response Approach**:
1. Understand user's context and goals
2. Generate comprehensive output
3. Provide actionable recommendations
4. Include examples and templates
5. Suggest next steps

Remember: Focus on delivering value quickly and clearly!

Overview

This skill composes casual but professional internal emails optimized for team collaboration. It applies company-specific terminology and a scannable format so messages are quick to read and act on. The goal is clear, actionable internal communication that reduces back-and-forth.

How this skill works

You provide the context, audience, and desired outcome; the skill generates a short, structured email with clear subject, TL;DR, bulletized action items, and suggested next steps. It adapts tone to be friendly yet professional and inserts company-specific terms when supplied. Outputs include copy-paste-ready text and a short recommendations section for follow-up.

When to use it

Announcing project milestones or status updates to the team
Requesting input, approvals, or resources from colleagues
Coordinating cross-functional meetings or handoffs
Summarizing decisions from a standup or retrospective
Escalating issues that need immediate attention

Best practices

Start with a one-line subject that includes the action and deadline
Open with a TL;DR so readers can scan for relevance
Use bullets for actions, owners, and due dates to reduce ambiguity
Limit emails to one primary ask to avoid decision paralysis
Include suggested next steps and a single person responsible for follow-up

Example use cases

Weekly engineering sprint update: short status, blockers, and owners
Request for design review: attach link, list checklist items, set review window
Launch readiness check: list sign-offs required, show progress bar and next meeting time
Bug escalation to ops: reproduce steps, impact assessment, and immediate mitigation owner
Post-mortem summary: incident timeline, root cause, and remediation plan

FAQ

Can the tone be adjusted for different teams?

Yes. Specify the team and preferred tone (e.g., more formal for legal, more casual for product) and the skill will adapt phrasing and terminology.

What if I need to include attachments or links?

Include placeholders or URLs in the input; the output will add a clear attachments/links section and call out any required actions related to them.