Install
$ agentstack add skill-spacefrontiers-ai-overmind-email-composer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Email Composer
Craft professional, effective emails that get results.
Instructions
When composing emails:
- Understand Context: Determine the purpose and audience
- Choose Tone: Match formality to relationship and situation
- Structure Clearly: Use professional email structure
- Be Concise: Respect the recipient's time
- Call to Action: Make next steps clear
- Proofread: Check grammar, spelling, and clarity
Email Structure
Subject Line
- Clear and specific
- Action-oriented when appropriate
- Under 50 characters ideal
- No clickbait or ALL CAPS
Greeting
- Formal: "Dear Dr. Smith," or "Dear Ms. Johnson,"
- Professional: "Hello Sarah," or "Hi Team,"
- Casual: "Hey Alex,"
Opening
- Context or reference
- Brief pleasantry (optional)
- State purpose early
Body
- Main message in 1-3 paragraphs
- Use bullet points for multiple items
- One topic per paragraph
- White space for readability
Call to Action
- Clear next steps
- Specific requests
- Deadlines if applicable
Closing
- Summary or thank you
- Professional sign-off
- Contact information
Signature
- Full name
- Title
- Company
- Contact details
Tone Guide
Formal (Executives, First Contact, Official)
Dear Mr. Chen,
I hope this email finds you well. I am writing to...
I would appreciate the opportunity to discuss...
Thank you for your consideration.
Best regards,
[Name]
Professional (Colleagues, Regular Business)
Hello Sarah,
Following up on our conversation about...
Could you please review and let me know...
Thanks,
[Name]
Friendly Professional (Established Relationships)
Hi Alex,
Hope you had a great weekend!
Quick question about the project...
Let me know what you think.
Cheers,
[Name]
Email Types
Follow-Up Email
Subject: Following up: [Original Topic]
Hi [Name],
I wanted to follow up on my previous email from [date] regarding [topic].
[Brief reminder of context]
Would you have time to discuss this [timeframe]? I'm happy to work around your schedule.
Thanks,
[Your Name]
Request Email
Subject: Request: [Specific Request]
Hello [Name],
I'm reaching out to request [specific item/action].
Context: [Why you need this]
Timeline: [When you need it]
Details: [Any relevant information]
Please let me know if you need any additional information.
Best,
[Your Name]
Meeting Request
Subject: Meeting Request: [Topic] - [Proposed Time]
Hi [Name],
I'd like to schedule a meeting to discuss [topic].
Purpose: [What we'll cover]
Duration: [Time needed]
Proposed times:
- [Option 1]
- [Option 2]
- [Option 3]
Please let me know what works for you, or suggest alternative times.
Thanks,
[Your Name]
Thank You Email
Subject: Thank you for [Specific Reason]
Dear [Name],
Thank you for [specific action/help/time]. I particularly appreciated [specific detail].
[Impact of their help]
I look forward to [next steps or continued relationship].
Best regards,
[Your Name]
Announcement Email
Subject: Announcement: [Clear Topic]
Team,
I'm excited to announce [what's being announced].
What this means:
• [Key point 1]
• [Key point 2]
• [Key point 3]
Next steps:
• [Action 1]
• [Action 2]
If you have questions, please [how to reach out].
Best,
[Your Name]
Guidelines
Do's
- Be Clear: State purpose early
- Be Concise: One screen of text ideal
- Be Specific: Include dates, times, details
- Be Professional: Even in casual settings
- Be Responsive: Reply within 24 hours
- Use Proper Grammar: Proofread before sending
- Add Value: Make it worth reading
Don'ts
- Don't Use All Caps: Seems like shouting
- Don't Over-Emoji: Keep professional
- Don't Reply All: Unless truly necessary
- Don't Send When Emotional: Wait and revise
- Don't Forget Attachments: Mention and include
- Don't Wall of Text: Break into paragraphs
- Don't Assume Tone: Text can be misread
Subject Line Formulas
- Action Required: "Action Required: [Task] by [Date]"
- FYI: "FYI: [Information]"
- Question: "Question: [Topic]"
- Meeting: "Meeting: [Topic] - [Date/Time]"
- Follow-up: "Following up: [Previous Topic]"
- Thank You: "Thank you for [Specific Thing]"
- Introduction: "Introduction: [Your Name] from [Company]"
Common Scenarios
Saying No Professionally
Thank you for thinking of me for [opportunity].
Unfortunately, I won't be able to [commitment] due to [brief reason].
I appreciate your understanding, and I hope we can collaborate on future opportunities.
Requesting Information
I'm currently working on [project] and need [specific information].
Could you please provide:
• [Item 1]
• [Item 2]
I need this by [date] to [reason]. Please let me know if that timeline works for you.
Delivering Bad News
I wanted to update you on [situation].
Unfortunately, [what happened].
Here's what we're doing to address this:
• [Action 1]
• [Action 2]
I apologize for any inconvenience and will keep you updated on our progress.
Best Practices
Before Sending
- [ ] Clear subject line
- [ ] Correct recipients
- [ ] Appropriate tone
- [ ] Grammar and spelling checked
- [ ] Links work
- [ ] Attachments included
- [ ] Call to action clear
- [ ] Read out loud for flow
After Sending
- Set reminders for follow-up
- Track if action required
- File for reference
- Update task list
Common Mistakes to Avoid
- Unclear Subject: "Update" or "Question" (too vague)
- Missing Context: Jumping into request without background
- Too Long: Multiple pages of text
- No Action: Unclear what recipient should do
- Poor Timing: Sending late Friday for Monday deadline
- Wrong Tone: Too casual with executives, too formal with peers
- Passive Voice: "Mistakes were made" vs "I made a mistake"
- Jargon Overload: Acronyms and terms reader may not know
Research-Backed Communication Principles
Writing Competency in Professional Settings
Research on business communication (Hines & Basso, 2009) reveals critical findings about professional writing:
Grammar and clarity matter:
- Entry-level professionals frequently lack thorough understanding of grammar, punctuation, and sentence structure
- Passive voice weakens impact: "Mistakes were made" vs "We made mistakes" - active voice creates accountability
- Subject-verb agreement errors: Most common when clauses/phrases separate subject and verb
- Pronoun confusion: Misuse of I/me/myself reflects poorly on credibility
Business writing principles:
- Logical conclusion first: Busy executives need the point upfront (not buried in middle/end)
- Clear and concise prose: Enables quick processing of message meaning
- Expressive vs. elitist language: Write to express ideas, not to impress with complexity
- Plain language initiative: Government and corporate push for clarity and efficiency
Evidence-Based Takeaway: Grammatical competency forges trust. Proper grammar avoids ambiguity and demonstrates professionalism.
Effective Workplace Communication
Research on great workplaces (Great Place to Work Institute, 2011) demonstrates communication's impact:
Communication affects credibility:
- Good communication skills invite two-way dialogue
- Clear and informative managers reduce rumor spread
- Accessible managers allow employees to get needed information
- Open communication allows employees to meet expectations and be productive
Generational communication differences:
- Traditionalists/Baby Boomers: Prefer one-to-one communication
- Gen X: Want work calls only, respond to open-ended questions
- Millennials: Use online social media, expect frequent feedback, prefer teams
Best practice: At team formation, learn how members prefer to communicate. Bring everyone onto the same page for optimal productivity.
Interpersonal Communication Quality
Research on workplace communication (Newson, 2010) highlights:
Key elements of effective interpersonal communication:
- Self-awareness: Understanding your own communication style and biases
- Attentive listening: More than hearing words - observing reactions and tone
- Sensitivity to others: Recognizing emotional state and context
- Strategic silence: Allowing space for reflection and processing
The power of silence:
- Gives speakers time to think and feel
- Creates space for reflection and problem-solving
- In grief/difficult news, presence matters more than words
- Uncomfortable at first, but powerful when mastered
Practical Application: In difficult email conversations, sometimes less is more. Know when brevity and directness serve better than lengthy explanations.
References
- Hines, R., & Basso, J. (2009). "Do Communication Students Have the 'Write Stuff'? Practitioners Evaluate Writing Skills of Entry-Level Workers". Journal of Promotion Management, 14(3-4), 293-307.
- Great Place to Work Institute. (2011). "Communicating at Great Workplaces - Key Principles at Work". Research white paper.
- Newson, P. (2010). "Good communication at work can open the gateway to better relationships". Nursing and Residential Care, 12(8), 366-369.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: SpaceFrontiers
- Source: SpaceFrontiers/ai-overmind
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.