Transform rough email drafts into polished, professional messages. Use this skill when the user wants to improve email quality, fix grammar and tone, format business emails, or convert casual messages into professional communication. Triggers include: 'format my email', 'make this professional', 'improve this message', 'fix my email', 'polish this draft', or any request to enhance email writing quality. Also use when converting bullet points or notes into complete emails, adjusting tone (formal/casual/friendly), or preparing important messages for clients, managers, or stakeholders.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Transform rough email drafts into polished, professional messages. Use this skill when the user wants to improve email quality, fix grammar and tone, format business emails, or convert casual messages into professional communication. Triggers include: 'format my email', 'make this professional', 'improve this message', 'fix my email', 'polish this draft', or any request to enhance email writing quality. Also use when converting bullet points or notes into complete emails, adjusting tone (formal/casual/friendly), or preparing important messages for clients, managers, or stakeholders.
license
MIT
author
Your Name
version
1.0.0
Email Formatter - Professional Email Enhancement
Installation & Setup
Prerequisites Check
Before using this skill, verify the environment has required capabilities:
# Check if bash is availablewhich bash
# Check Python version (3.8+ required)
python3 --version
# Check Node.js (optional, for advanced features)
node --version
Auto-Installation Script
For AI Agents: Run this installation check at first use
#!/bin/bash# Email Formatter Skill - Auto Setup# This script installs required dependenciesecho"🔧 Email Formatter Skill - Installation Starting..."# Create skill workspace
SKILL_DIR="$HOME/.email-formatter-skill"mkdir -p "$SKILL_DIR"cd"$SKILL_DIR"# Install Python dependenciesecho"📦 Installing Python packages..."
pip3 install --break-system-packages --quiet \
language-tool-python \
textstat \
spacy 2>/dev/null || pip3 install --user --quiet \
language-tool-python \
textstat \
spacy
# Download language model for grammar checkingecho"📚 Downloading language model..."
python3 -m spacy download en_core_web_sm --quiet 2>/dev/null || true# Create helper scripts directorymkdir -p "$SKILL_DIR/scripts"# Test installationif python3 -c "import language_tool_python; import textstat; import spacy" 2>/dev/null; thenecho"✅ Email Formatter Skill installed successfully!"echo"📍 Installed at: $SKILL_DIR"exit 0
elseecho"⚠️ Some dependencies failed. Skill will work with reduced features."exit 0
fi
Manual Installation (if auto-install fails)
# Minimal setup - no external dependencies# The skill will use built-in Python capabilities onlymkdir -p ~/.email-formatter-skill/scripts
echo"✅ Basic setup complete"
Python 3.7+ (standard library only for minimal mode)
Bash shell
Optional (Enhanced Features)
language-tool-python: Advanced grammar checking
textstat: Readability analysis
spacy: NLP for tone detection
Note for AI Agents: The skill works in degraded mode without optional dependencies. Install them only if environment allows.
Overview
This skill transforms rough email drafts into polished, professional communication by improving grammar, adjusting tone, enhancing clarity, and applying proper formatting. It handles everything from quick fixes to complete rewrites while preserving the sender's intent.
⚠️ CRITICAL SECURITY & SAFETY REQUIREMENTS
This skill MUST enforce these non-negotiable safety rules at all times:
SECURITY LEVEL: MAXIMUM - Multi-Layer Validation Required
MANDATORY PRE-PROCESSING SECURITY CHECKS:
Every email MUST pass ALL security layers before any formatting occurs:
Scan for suspicious patterns that indicate malicious intent:
Financial Red Flags:
Urgent payment requests
Wire transfer instructions
Gift card purchases
Cryptocurrency transactions
"Keep this confidential" + money
Bypassing normal approval process
Unusual account changes
Tax refund scams
Inheritance scams
Lottery/prize scams
Authority Impersonation Red Flags:
"I'm from IT/HR/Legal/Management"
"CEO needs you to..."
"Urgent request from [authority]"
"Don't tell anyone"
Bypassing email/domain verification
Unusual requests from superiors
Fake emergency scenarios
Credential Harvesting Red Flags:
"Verify your password"
"Confirm your account"
"Click to prevent suspension"
"Unusual login detected"
Links to login pages
Fake security alerts
Account expiration warnings
Social Engineering Red Flags:
Artificial urgency
Emotional manipulation
Too good to be true
Requests for secrecy
Unusual sender behavior
Pressure tactics
Fear-based messaging
Layer 3: Sentiment & Tone Analysis (WARN OR BLOCK)
⚠️ Aggressive/Hostile: Insulting, demeaning, threatening language
⚠️ Manipulative: Guilt-tripping, gaslighting, emotional blackmail
⚠️ Coercive: Power imbalance exploitation, quid pro quo
⚠️ Deceptive: Half-truths, misleading statements, omissions
⚠️ Discriminatory: Based on protected characteristics
⚠️ Retaliatory: Punishment for protected actions
Layer 4: Context Validation (VERIFY LEGITIMACY)
✓ Sender-Recipient Relationship: Does this match their normal communication?
✓ Request Reasonability: Is this a normal business request?
✓ Communication Channel: Should this be email or in-person/phone?
✓ Timing: Why is this urgent? Is urgency justified?
✓ Information Sensitivity: Should this data be in email?
✓ Authorization: Does sender have authority for this request?
Layer 5: Privacy & Data Protection (GDPR/CCPA COMPLIANCE)
🔒 PII Detection: Name, address, phone, email, SSN, DOB, photos
🔒 Financial Data: Credit cards, bank accounts, tax IDs, salary info
🔒 Health Data: Medical records, diagnoses, prescriptions, HIPAA data
🔒 Credentials: Passwords, API keys, tokens, security questions
🔒 Proprietary Data: Trade secrets, confidential business info, NDA material
🔒 Children's Data: ANY data about individuals under 18
ACTION REQUIRED: If PII detected, warn user about:
1. STOP - Do not process further
2. LOG - Record violation type (no content)
3. INFORM - Tell user specifically what rule was violated
4. EDUCATE - Explain why it's harmful/illegal
5. REDIRECT - Suggest legitimate alternatives
6. REPORT - Flag for review if severe (threats, child safety, fraud)
Example Response Template:
🛑 SECURITY BLOCK: Email Formatting Refused
REASON: [Specific violation - e.g., "Credential request detected"]
WHY THIS IS BLOCKED:
[Explanation - e.g., "Legitimate organizations never ask for
passwords via email. This matches phishing attack patterns."]
WHAT YOU SHOULD DO:
[Alternative - e.g., "If you need to reset a password, use
the official password reset link on the company website."]
THIS SKILL CANNOT:
- Help with fraudulent communications
- Bypass security protocols
- Facilitate illegal activities
- Enable harassment or threats
Helper Scripts & Tools
The skill includes utility scripts for AI agents to use. Create these in ~/.email-formatter-skill/scripts/:
1. Grammar Checker (grammar_check.py)
#!/usr/bin/env python3"""
Basic grammar and spell checker
Usage: python3 grammar_check.py "email text here"
"""import sys
import re
defbasic_grammar_check(text):
"""Basic grammar checks without external dependencies"""
issues = []
# Common spelling errors
typos = {
'recieve': 'receive', 'occured': 'occurred', 'seperate': 'separate',
'definately': 'definitely', 'accomodate': 'accommodate',
'tommorow': 'tomorrow', 'untill': 'until', 'truely': 'truly'
}
for wrong, right in typos.items():
if wrong in text.lower():
issues.append(f"Spelling: '{wrong}' → '{right}'")
# Basic grammar patternsif re.search(r'\bi\s', text): # lowercase 'i'
issues.append("Grammar: 'i' should be capitalized to 'I'")
if re.search(r'\s{2,}', text):
issues.append("Formatting: Multiple spaces detected")
if re.search(r'[.!?]\s*[a-z]', text):
issues.append("Grammar: Sentence should start with capital letter")
# Double punctuationif re.search(r'[.!?]{2,}', text):
issues.append("Punctuation: Multiple punctuation marks")
return issues
if __name__ == "__main__":
iflen(sys.argv) < 2:
print("Usage: python3 grammar_check.py 'text'")
sys.exit(1)
text = sys.argv[1]
issues = basic_grammar_check(text)
if issues:
for issue in issues:
print(f"⚠️ {issue}")
else:
print("✅ No basic issues found")
2. Tone Analyzer (tone_analyzer.py)
#!/usr/bin/env python3"""
Analyze email tone
Usage: python3 tone_analyzer.py "email text"
"""import sys
import re
defanalyze_tone(text):
"""Detect tone indicators in email text"""# Formal indicators
formal_words = ['pursuant', 'hereby', 'aforementioned', 'regarding',
'sincerely', 'respectfully', 'cordially']
# Casual indicators
casual_words = ['hey', 'gonna', 'wanna', 'yeah', 'yep', 'nope',
'btw', 'fyi', 'lol', 'omg', 'tbh']
# Aggressive indicators
aggressive_words = ['immediately', 'must', 'unacceptable', 'ridiculous',
'obviously', 'clearly', 'need to', 'have to']
# Polite indicators
polite_words = ['please', 'kindly', 'would you', 'could you',
'appreciate', 'thank', 'grateful']
text_lower = text.lower()
formal_count = sum(1for w in formal_words if w in text_lower)
casual_count = sum(1for w in casual_words if w in text_lower)
aggressive_count = sum(1for w in aggressive_words if w in text_lower)
polite_count = sum(1for w in polite_words if w in text_lower)
# Exclamation marks
exclamations = len(re.findall(r'!', text))
# ALL CAPS detection
caps_words = len(re.findall(r'\b[A-Z]{2,}\b', text))
# Determine primary tone
tones = []
if formal_count >= 2:
tones.append("FORMAL")
if casual_count >= 2:
tones.append("CASUAL")
if aggressive_count >= 2or caps_words >= 2:
tones.append("AGGRESSIVE")
if polite_count >= 2:
tones.append("POLITE")
if exclamations >= 3:
tones.append("ENTHUSIASTIC/URGENT")
ifnot tones:
tones.append("NEUTRAL")
return {
'primary_tone': tones[0],
'all_tones': tones,
'formal_score': formal_count,
'casual_score': casual_count,
'aggressive_score': aggressive_count,
'polite_score': polite_count,
'exclamations': exclamations,
'caps_words': caps_words
}
if __name__ == "__main__":
iflen(sys.argv) < 2:
print("Usage: python3 tone_analyzer.py 'text'")
sys.exit(1)
result = analyze_tone(sys.argv[1])
print(f"📊 Primary Tone: {result['primary_tone']}")
print(f"🎯 All Tones: {', '.join(result['all_tones'])}")
print(f"📈 Scores - Formal:{result['formal_score']} Casual:{result['casual_score']} "f"Aggressive:{result['aggressive_score']} Polite:{result['polite_score']}")
if result['aggressive_score'] >= 2:
print("⚠️ WARNING: Email may sound aggressive")
if result['exclamations'] >= 3:
print("⚠️ WARNING: Too many exclamation marks")
if result['caps_words'] >= 2:
print("⚠️ WARNING: Excessive capitalization detected")
3. Readability Scorer (readability.py)
#!/usr/bin/env python3"""
Calculate email readability
Usage: python3 readability.py "email text"
"""import sys
import re
defcount_syllables(word):
"""Simple syllable counter"""
word = word.lower()
vowels = 'aeiouy'
syllable_count = 0
previous_was_vowel = Falsefor char in word:
is_vowel = char in vowels
if is_vowel andnot previous_was_vowel:
syllable_count += 1
previous_was_vowel = is_vowel
# Adjust for silent 'e'if word.endswith('e'):
syllable_count -= 1# Every word has at least one syllableif syllable_count == 0:
syllable_count = 1return syllable_count
defflesch_reading_ease(text):
"""Calculate Flesch Reading Ease score"""
sentences = len(re.findall(r'[.!?]+', text)) or1
words = len(text.split())
syllables = sum(count_syllables(word) for word in text.split())
if words == 0:
return0
score = 206.835 - 1.015 * (words / sentences) - 84.6 * (syllables / words)
returnround(score, 1)
defanalyze_readability(text):
"""Analyze email readability"""
words = text.split()
sentences = len(re.findall(r'[.!?]+', text)) or1
avg_word_length = sum(len(w) for w in words) / len(words) if words else0
avg_sentence_length = len(words) / sentences
flesch_score = flesch_reading_ease(text)
# Interpret scoreif flesch_score >= 90:
level = "Very Easy (5th grade)"elif flesch_score >= 80:
level = "Easy (6th grade)"elif flesch_score >= 70:
level = "Fairly Easy (7th grade)"elif flesch_score >= 60:
level = "Standard (8-9th grade)"elif flesch_score >= 50:
level = "Fairly Difficult (10-12th grade)"elif flesch_score >= 30:
level = "Difficult (College)"else:
level = "Very Difficult (Graduate)"return {
'flesch_score': flesch_score,
'level': level,
'avg_word_length': round(avg_word_length, 1),
'avg_sentence_length': round(avg_sentence_length, 1),
'total_words': len(words),
'total_sentences': sentences
}
if __name__ == "__main__":
iflen(sys.argv) < 2:
print("Usage: python3 readability.py 'text'")
sys.exit(1)
result = analyze_readability(sys.argv[1])
print(f"📖 Flesch Reading Ease: {result['flesch_score']}")
print(f"📚 Reading Level: {result['level']}")
print(f"📊 Stats: {result['total_words']} words, {result['total_sentences']} sentences")
print(f"📏 Avg: {result['avg_word_length']} chars/word, {result['avg_sentence_length']} words/sentence")
# Recommendationsif result['flesch_score'] < 60:
print("💡 TIP: Simplify language for better clarity")
if result['avg_sentence_length'] > 20:
print("💡 TIP: Break long sentences into shorter ones")
Tone needed: Formal, semi-formal, casual, friendly, assertive, diplomatic?
Urgency: Routine, important, urgent, sensitive?
Current issues: Grammar errors, unclear structure, wrong tone, missing context?
Step 2: Apply Improvements
Grammar & Mechanics:
Fix spelling, punctuation, and grammatical errors
Correct subject-verb agreement and tense consistency
Remove run-on sentences and fragments
Fix comma splices and misplaced modifiers
Structure & Organization:
Standard Email Structure:
1. Greeting (appropriate to relationship)
2. Opening (context or pleasantry)
3. Purpose statement (clear and direct)
4. Body (organized by topic, use paragraphs/bullets)
5. Call to action (if needed)
6. Closing (polite sign-off)
7. Signature
Tone Adjustments:
Too Casual → Professional:
Before: "Hey! Just wanted to check if u got my last email lol"
After: "Hi Sarah, I wanted to follow up on my previous email from Tuesday. Please let me know if you need any additional information."
Too Formal → Friendly:
Before: "I am writing to inquire whether you have completed the aforementioned task."
After: "Hi John, I wanted to check in on the status of the marketing report. How's it coming along?"
Too Aggressive → Diplomatic:
Before: "You need to fix this immediately. This is unacceptable."
After: "I noticed an issue that requires urgent attention. Could we prioritize resolving this today? I'm happy to help if needed."
Clarity Enhancements:
Replace vague phrases with specific language
Break long paragraphs into digestible chunks
Use bullet points for lists or multiple items
Add context where assumed knowledge might be missing
Remove redundancy and filler words
Step 3: Polish Details
Subject Line (if provided or needed):
Keep it under 50 characters
Make it specific and actionable
Use sentence case (not all caps)
Examples:
"Q1 Budget Review Meeting - March 15"
"Quick question about project timeline"
"Following up: Website redesign proposal"
Greetings:
Formal: "Dear Dr. Smith," or "Dear Hiring Manager,"
Professional: "Best," "Thanks," "Looking forward to hearing from you,"
Casual: "Cheers," "Talk soon," "Have a great day,"
Signature Block:
Best regards,
[Name]
[Title]
[Company]
[Contact Info - if external]
Common Email Scenarios
1. Request Email
Structure:
- Greeting
- Context (why you're writing)
- Specific request
- Deadline or timeframe (if applicable)
- Offer of additional info
- Thanks
- Closing
2. Follow-Up Email
Structure:
- Reference previous communication
- Polite reminder of action needed
- Make it easy to respond
- Maintain friendly tone
- Closing
3. Bad News Email
Structure:
- Direct but empathetic opening
- Clear explanation
- Acknowledge impact
- Offer alternatives or next steps
- End on positive note if possible
4. Introduction Email
Structure:
- Who you are and connection
- Purpose of introduction
- What you're offering/requesting
- Call to action
- Professional closing
Best Practices
DO:
✅ Keep emails concise (under 200 words when possible)
✅ Use active voice ("I will send" vs "It will be sent")
✅ Break up text with white space
✅ Put most important info in first paragraph
✅ Proofread for typos and auto-correct errors
✅ Use "Reply All" judiciously
✅ Include clear next steps or calls to action
✅ Match the sender's energy level
DON'T:
❌ Use all caps (seems like shouting)
❌ Overuse exclamation marks
❌ Include multiple topics in one email (if complex)
❌ Use jargon with external recipients
❌ Write when emotional (flag if email seems angry)
❌ Assume tone translates (sarcasm, humor can fail)
❌ Forget attachments referenced in text
❌ Change factual content or commitments
Tone Guide
Formal (executives, clients, first contact):
Complete sentences
Professional vocabulary
Proper titles and full names
"I would appreciate" vs "Can you"
"Please let me know" vs "Let me know"
Semi-Formal (colleagues, regular contacts):
Conversational but professional
Contractions are fine
First names acceptable
"Could you" vs "Can you"
Friendly but respectful
Casual (close colleagues, internal teams):
Relaxed language
Contractions and informal phrases
Quick greetings
Can be brief
Emoji okay if culturally appropriate
Quality Checklist
Before presenting the formatted email, verify:
SECURITY FIRST: Content passes all safety requirements
No prohibited content: Checked against all safety rules above
Legal compliance: No fraudulent, harassing, or illegal content
Ethical standards: Message is honest and appropriate
Grammar and spelling are correct
Tone matches relationship and context
Structure is clear and logical
Key information is easy to find
Call to action is clear (if needed)
Opening and closing are appropriate
No ambiguity or confusion
Length is appropriate (concise but complete)
Professional formatting applied
Original intent is preserved
Privacy check: No sensitive data exposed inappropriately
Reputation check: Sender won't regret sending this
Red Flag Detection
Always scan for these warning signs:
Requests for money, credentials, or personal information
Urgency combined with financial requests
Impersonation language ("I'm calling from...", "This is [authority]...")
Threats or ultimatums
Asking recipient to keep communication secret
Bypassing normal procedures
Inconsistent sender information
Requests to click suspicious links
Grammar/spelling errors in supposedly official communication
Too-good-to-be-true offers
Emotional manipulation tactics
Discriminatory language
False information
Hostile or aggressive tone toward protected groups
Incident Response Protocol
When Critical Violations Detected (Threat Level 3):
IMMEDIATE ACTIONS:
1. BLOCK - Refuse to format email
2. DOCUMENT - Record violation type, timestamp
3. NOTIFY - Inform user of specific violation
4. EDUCATE - Explain why it's harmful/illegal
5. REDIRECT - Suggest legitimate alternatives
6. REPORT - Flag for review if:
- Child safety violations
- Credible threats of violence
- Large-scale fraud attempts
- Illegal activities
Response Template for Critical Violations:
🚨 CRITICAL SECURITY VIOLATION DETECTED
VIOLATION TYPE: [Specific type - e.g., "Credential Phishing Attempt"]
SEVERITY: CRITICAL - This email cannot be formatted
WHAT WAS DETECTED:
[Specific pattern - e.g., "Email requests password and account
credentials, matching known phishing attack patterns"]
WHY THIS IS SERIOUS:
[Impact - e.g., "This could lead to:
- Identity theft
- Unauthorized account access
- Financial fraud
- Legal liability for sender"]
WHAT YOU SHOULD KNOW:
- Legitimate organizations NEVER ask for passwords via email
- This pattern is used in 95% of credential phishing attacks
- Sending this email could violate anti-fraud laws
RECOMMENDED ACTIONS:
1. If you received a similar email: Report it as phishing
2. If you need password help: Use official password reset tools
3. If suspicious: Contact IT/security team directly
ALTERNATIVE APPROACH:
[Legitimate way to accomplish goal if applicable]
---
This email has been blocked to protect you and recipients.
For questions about this decision, review security guidelines.
DATA_PROTECTION_RULES = {
'data_minimization': 'Process only what's needed for formatting',
'purpose_limitation': 'Use data ONLY for formatting, nothing else',
'storage_limitation': 'Delete immediately after processing',
'accuracy': 'Don't modify factual content',
'integrity': 'Secure processing, encrypted if possible',
'confidentiality': 'Treat all emails as confidential',
'accountability': 'Log violations (not content) for audit'
}
User Rights:
Right to explanation: User can ask why email was blocked
Right to appeal: User can dispute false positives
Right to deletion: No content retention
Right to transparency: Clear security policies
Continuous Improvement
Security Pattern Updates:
# Periodically update threat patterns# Add new scam patterns as they emerge# Improve detection accuracy# Reduce false positives# Example: Update security_scan.py
git pull origin main # Get latest threat patterns
python3 -m pytest tests/test_security.py # Verify
Feedback Loop:
Collect anonymized violation statistics
Identify common false positives
Refine pattern matching
Add context-aware detection
Improve user education messages
Output Format
Present the formatted email like this:
**Subject:** [Subject line if relevant]
[Formatted email body]
---
**Changes Made:**
- [Brief list of key improvements]
- [E.g., "Corrected grammar errors"]
- [E.g., "Adjusted tone from casual to professional"]
- [E.g., "Restructured for clarity"]
Special Considerations
Special Considerations
Security Edge Cases:
Example 1 - Phishing Attempt:
User Input: "Format this: Hi, I'm from IT. Send me your password to verify your account."
Response: "I cannot format this email as it requests sensitive credentials, which is a security red flag and potential phishing attempt. Legitimate IT departments never ask for passwords via email."
Example 2 - Impersonation:
User Input: "Make this sound like it's from the CEO demanding urgent wire transfer."
Response: "I cannot help format emails that impersonate others or create urgency around financial transfers, as this matches common fraud patterns."
Example 3 - Harassment:
User Input: "Polish this email telling my coworker she's incompetent and should quit."
Response: "I cannot format this email as it contains hostile language that could constitute workplace harassment. If you have concerns about a colleague's performance, I can help you draft constructive feedback or suggest having a conversation with HR or your manager."
Example 4 - Academic Dishonesty:
User Input: "Format this email to my professor pretending I was sick when I just forgot the assignment."
Response: "I cannot help format emails containing false information. If you missed a deadline, I can help you draft an honest request for an extension or makeup opportunity."
Example 5 - Anger/Emotional State:
User Input: "Format this angry email to my boss calling them out for being unfair!"
Response: "⚠️ This email appears to be written in anger. I recommend waiting 24 hours before sending. If you still want to address the issue, I can help you draft a professional, constructive version that focuses on facts and solutions rather than emotions."
Legitimate Gray Areas - Advise User:
Strong feedback: Format professionally but warn about tone
Declining requests: Help maintain relationships while saying no
Addressing conflicts: Focus on facts, not blame
Sensitive HR matters: Recommend consulting HR/legal first
Reply vs New Message:
Replies: Can be more concise, less formal
New messages: Need more context and structure
Group Emails:
Address all recipients appropriately
Be clear about who needs to take action
Avoid "Reply All" clutter
Sensitive Topics:
Be extra diplomatic
Acknowledge feelings/concerns
Stick to facts
Offer to discuss in person/call if needed
International Recipients:
Avoid idioms and colloquialisms
Use clear, direct language
Be aware of cultural communication differences
Spell out dates (avoid 3/4/24 format ambiguity)
Mobile Email:
Front-load most important info
Use shorter paragraphs
Limit to one topic if possible
Clear subject lines are crucial
Common Mistakes to Avoid
Starting with apologies: "Sorry to bother you" → "I hope this email finds you well"
Buried lede: Put main point in first paragraph
Too many questions: Limit to 1-2 per email
Passive voice overuse: "The report was completed" → "I completed the report"
Unclear next steps: Always specify what happens next
Inconsistent tone: Maintain same formality throughout
Advanced Techniques
The BLUF Method (Bottom Line Up Front):
State conclusion/request first
Provide supporting details after
Ideal for busy executives
Chunking Information:
Use subheadings for long emails
Bullet points for lists
Bold key phrases for scanning
Call to Action Clarity:
"Please review and approve by Friday EOD"
"Let me know if you have questions"
"I'll send the draft by Thursday for your feedback"
Softening Requests:
"Would you be able to..." vs "Can you..."
"I was wondering if..." vs "I need..."
"If possible..." vs "Please..."
Version History
v1.0.0 (2024): Initial release with core formatting capabilities
License
MIT License - Free to use and modify
Pro Tip for Users: For best results, provide context about the recipient relationship and email purpose. The more context, the better the skill can match the appropriate tone and structure.