email-composer
Skill0 starsChanged 49 days agoMITView on GitHub
Compose professional emails in Spanish and English. Includes templates for common scenarios: meetings, updates, deadlines, introductions, apologies. Trigger on 'write email', 'compose email', 'draft email', 'send email'.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- JayRHa/agent-skillstheir own version, first seen Oct 15, 2026
- peakdong68/my-skillstheir own version, first seen Aug 29, 2026
- BenPrem/business-braintheir own version, first seen Aug 8, 2026
- JayRHa/AgentSkillstheir own version, first seen Jun 9, 2026
- dhriyatinandu-bot/claude-skillstheir own version, first seen Mar 5, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- jaskirat1616/grok-skills★ 22same name
- JayRHa/agent-skills★ 12same name
- JayRHa/AgentSkills★ 12same name
- Crumbgrabber/llm_system_template_agents_skills_patterns_tools_prompts★ 3same name
- BenPrem/business-brain★ 1same name
- dhriyatinandu-bot/claude-skills★ 0same name
- peakdong68/my-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- examples/CLAUDE.mdCLAUDE.md
- Anti-Hallucination VerificationSkill
- backup-snapshotSkill
- Multi-Agent BrainstormSkill
- Browser UATSkill
- ci-cd-builderSkill
- Code Patterns ReferenceSkill
- Conventional Commits WorkflowSkill
- Context Curator AdministrationSkill
- git-detectiveSkill
- imap-emailSkill
- ollama-model-managerSkill
- Ollama Code VerificationSkill
- project-bootstrapperSkill
- prompt-engineerSkill
- refactor-analyzerSkill
- release-managerSkill
- scheduleSkill
- skill-creatorSkill
- Work LogSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
All professional emails follow:
- Distinctive: line 44
Keep paragraphs short (3-4 sentences max)
- Distinctive: line 45
Use clear subject lines that describe content
- Distinctive: line 46
Avoid all-caps (appears like shouting)
- Distinctive: line 47
Avoid vague language ("ASAP", "soon", "shortly")
- Distinctive: line 48
Use specific deadlines ("by Friday 5pm")
- Distinctive: line 106
Use active verbs: "I reviewed", "We decided", "Please send"
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Email Composer Skill
Overview
Draft professional, clear, and appropriate emails in both English and Spanish. Covers common business scenarios with templates and best practices.
Phase 1: ASSESS
Understand Requirements
- Recipient: Who are you writing to? (colleague, manager, client, external contact)
- Purpose: What's the primary goal? (request, update, apology, introduction, scheduling, deadline)
- Tone: Formal, semi-formal, friendly, urgent?
- Language: English or Spanish?
- Context: Is this first contact or ongoing relationship?
- Urgency: Normal, important, or time-sensitive?
Identify Email Type
- Meeting request
- Project update
- Deadline reminder
- Introduction
- Apology
- Thank you
- Problem escalation
- Decision notification
- Feedback request
Phase 2: DRAFT
Structure
All professional emails follow:
- Greeting — appropriate for relationship level
- Opening — context, why you're writing
- Body — main content (2-3 focused paragraphs)
- Call-to-Action — what response/action needed (if applicable)
- Closing — professional sign-off
- Signature — name, title, contact info
Best Practices
- Keep paragraphs short (3-4 sentences max)
- Use clear subject lines that describe content
- Avoid all-caps (appears like shouting)
- Avoid vague language ("ASAP", "soon", "shortly")
- Use specific deadlines ("by Friday 5pm")
- Be concise but warm
- Passive voice only when necessary (focus on actions, not blame)
Common Phrases by Situation
Requests
- "Could you please..."
- "I would appreciate if you could..."
- "Would it be possible to..."
- "I'm reaching out regarding..."
Urgency
- "I wanted to flag this because..."
- "This requires your attention by..."
- "This is time-sensitive..."
Agreement/Positive
- "Thank you for..."
- "I appreciate your..."
- "Great idea about..."
Disagreement (tactful)
- "I had another thought on..."
- "Have you considered..."
- "I see your point, and I'd also suggest..."
Next Steps
- "Let's connect on..."
- "I'll send over... by..."
- "Looking forward to your thoughts"
Phase 3: REFINE
Check for:
Clarity
- Is the purpose clear in first paragraph?
- Does each sentence add value?
- Would a non-expert understand this?
Tone & Professionalism
- Any accidental harshness or passive-aggressive tone?
- Appropriate formality for relationship?
- Typos, grammar, spelling?
Ambiguity
- Could key points be misinterpreted?
- Are deadlines and expectations clear?
- Is call-to-action explicit?
Length
- Too long? (more than 1 screen = too long)
- Too short? (missing context?)
- Ideal: 100-300 words
Passive Voice
- Minimize "is", "was", "be"
- Use active verbs: "I reviewed", "We decided", "Please send"
Phase 4: PRESENT
Show draft to user with:
- Plain text version ready to copy
- 1-2 alternative variants (if major tone choices)
- Summary of what it accomplishes
- Suggested subject line(s)
- Invite refinement ("Would you like me to adjust...?")
Template Library
Meeting Request (English)
Subject: Meeting Request - [Topic]
Dear [Name],
I hope this email finds you well. I wanted to connect regarding [specific topic], as I think it would be valuable for us to align on [brief context].
Would you be available for a 30-minute meeting next week? I'm flexible with timing and can work around your schedule. Some times that work for me are:
- Tuesday, 2-4 PM
- Wednesday, 10 AM-12 PM
- Thursday, 1-3 PM
Let me know what works best for you, or feel free to suggest an alternative time.
Thanks, [Your Name]
Meeting Request (Spanish)
Subject: Solicitud de reunión - [Topic]
Estimado/a [Nombre],
Espero que se encuentre bien. Me gustaría contactarle respecto a [tema específico], ya que creo que sería valioso que nos pusiéramos de acuerdo sobre [contexto breve].
¿Tendría disponibilidad para una reunión de 30 minutos la próxima semana? Tengo flexibilidad y puedo adaptarme a su horario. Algunos momentos que me vienen bien son:
- Martes, 14:00-16:00
- Miércoles, 10:00-12:00
- Jueves, 13:00-15:00
Avíseme qué le parece bien, o siéntase libre de sugerir otro horario.
Saludos, [Su Nombre]
Project Update (English)
Subject: Project Update - [Project Name]
Hi [Name],
I wanted to give you a quick status update on [project name]. We're on track and making good progress.
Completed this week:
- [Item 1]
- [Item 2]
In progress:
- [Item 3] — expected completion [date]
- [Item 4] — expected completion [date]
Upcoming blockers:
- None at the moment, but [awareness item if relevant]
We're on schedule to deliver [key milestone] by [date]. Please let me know if you have any questions or would like to discuss in more detail.
Thanks, [Your Name]
Project Update (Spanish)
Subject: Actualización de proyecto - [Nombre del Proyecto]
Hola [Nombre],
Quería ofrecerle una actualización rápida sobre el proyecto [nombre del proyecto]. Vamos en buen camino y haciendo buen progreso.
Completado esta semana:
- [Elemento 1]
- [Elemento 2]
En progreso:
- [Elemento 3] — conclusión esperada [fecha]
- [Elemento 4] — conclusión esperada [fecha]
Obstáculos próximos:
- Ninguno por el momento, pero [item de conciencia si es relevante]
Estamos en camino de entregar [hito clave] antes del [fecha]. Avíseme si tiene alguna pregunta o si desea discutir esto en más detalle.
Saludos, [Su Nombre]
Deadline Reminder (English)
Subject: Reminder - [Deliverable] Due [Date]
Hi [Name],
A quick reminder that [deliverable/task] is due [specific date and time].
Please [specific instruction: submit, review, approve, etc.] at [location/system]. If you have any questions or foresee any issues with meeting this deadline, please let me know as soon as possible so we can troubleshoot together.
Thanks for keeping this on track!
[Your Name]
Deadline Reminder (Spanish)
Subject: Recordatorio - [Entregable] Vence el [Fecha]
Hola [Nombre],
Un recordatorio rápido de que [entregable/tarea] vence el [fecha y hora específica].
Por favor, [instrucción específica: envíe, revise, apruebe, etc.] en [ubicación/sistema]. Si tiene alguna pregunta o prevé algún problema para cumplir con este plazo, avíseme lo antes posible para que podamos resolver juntos.
¡Gracias por mantener esto en marcha!
[Su Nombre]
Introduction (English)
Subject: Introduction - [Your Name]
Dear [Name],
I hope this email finds you well. [Name] recently suggested we connect, as we share interests in [common area/mutual connection].
A bit about me: I'm [brief title/role] at [organization], focusing on [key area]. I've been particularly interested in [specific area of their expertise/your shared interest].
I'd be delighted to learn more about your work in [their area]. Would you be open to a brief introductory call sometime next week?
Looking forward to connecting.
Best regards, [Your Name] [Title] [Contact Info]
Introduction (Spanish)
Subject: Presentación - [Su Nombre]
Estimado/a [Nombre],
Espero que se encuentre bien. Recientemente [nombre] me sugirió que nos pusiéramos en contacto, ya que compartimos intereses en [área común/conexión mutua].
Un poco sobre mí: soy [título/rol breve] en [organización], enfocándome en [área clave]. He estado particularmente interesado en [área específica de su experiencia/interés compartido].
Me gustaría aprender más sobre su trabajo en [su área]. ¿Estaría abierto a una breve llamada introductoria la próxima semana?
Espero conectar con usted.
Saludos cordiales, [Su Nombre] [Título] [Información de Contacto]
Apology (English)
Subject: Apology - [Situation]
Dear [Name],
I want to sincerely apologize for [specific action/mistake]. You're right that [acknowledge their concern], and I take full responsibility for [what went wrong].
Here's what I'm doing to fix this:
- [Action 1]
- [Action 2]
- [Action 3]
I value our working relationship and want to make sure this doesn't happen again. Please let me know if there's anything else I can do.
Again, I apologize for the inconvenience this caused.
Sincerely, [Your Name]
Apology (Spanish)
Subject: Disculpas - [Situación]
Estimado/a [Nombre],
Quiero ofrecerle mis más sinceras disculpas por [acción/error específico]. Tiene razón en que [reconozca su preocupación], y asumo total responsabilidad por [qué salió mal].
Aquí está lo que estoy haciendo para solucionar esto:
- [Acción 1]
- [Acción 2]
- [Acción 3]
Valoro nuestra relación de trabajo y quiero asegurarme de que esto no vuelva a suceder. Por favor, avíseme si hay algo más que pueda hacer.
De nuevo, le pido disculpas por los inconvenientes que esto le ha causado.
Atentamente, [Su Nombre]
Feedback Request (English)
Subject: Your Feedback Requested - [Topic]
Hi [Name],
I'm working on [project/document/idea] and would greatly value your perspective. Given your expertise in [their area], I think your feedback would be particularly helpful.
Could you review [attached file/link] and share your thoughts on:
- [Specific question 1]
- [Specific question 2]
- [Specific question 3]
I'd really appreciate getting your input by [date]. Let me know if you need any additional context or would prefer to discuss over a call.
Thanks!
[Your Name]
Thank You (English)
Subject: Thank You for [Action/Help]
Dear [Name],
I wanted to express my gratitude for [specific thing they did]. Your [contribution/insight/support] made a real difference in [outcome].
I genuinely appreciate [specific detail about why it mattered], and it's clear that [acknowledge their character/expertise].
Thank you again for everything.
Best regards, [Your Name]
Writing Tips
Common Mistakes to Avoid
- Using "hope you're doing well" in every email (varies if ongoing correspondence)
- Ending with a period after sign-off (use comma after greeting)
- Multiple exclamation marks (comes across as unprofessional)
- Using emoticons or slang
- Forwarding without adding context
- "Per my last email" (frustrating tone)
Tone Checklist
- Not too formal? (check for unnecessary jargon)
- Not too casual? (check for slang or informality)
- Warm but professional?
- Action-oriented?
Before Sending
- Read aloud (catches awkward phrasing)
- Check recipient name spelling
- Verify dates and times are correct
- Confirm attachments if mentioned
- Check subject line is informative
- Wait 5 minutes and re-read (catch tone issues)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

