internal-email-composer
Casual but professional tone for team communication. Uses company-specific terminology with scannable format.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install gked2121-claude-skills-internal-email-composer
Repository
Skill path: internal-email-composer
Casual but professional tone for team communication. Uses company-specific terminology with scannable format.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: gked2121.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install internal-email-composer into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/gked2121/claude-skills before adding internal-email-composer to shared team environments
- Use internal-email-composer for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
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!