Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

email

Estrellas700

Forks58

Actualizado21 de marzo de 2026 a las 05:01

Business email writing — formal/informal tone, structured format, replies, follow-ups, multilingual support.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

openyak

openyak/openyak

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Empleados de oficina generalesOficina y apoyo administrativo·SOC 43-9061

SKILL.md

readonly

name	email
description	Business email writing — formal/informal tone, structured format, replies, follow-ups, multilingual support.

Business Email Writing

When the user asks you to draft an email, follow this workflow:

1. Clarify key details

Before writing, confirm:

Recipient: Who is it for? (manager, colleague, client, external partner)
Purpose: Inform, request, follow up, thank, apologize, invite?
Tone: Formal, semi-formal, or casual?
Language: Match the user's language or ask if bilingual is needed.

If unspecified, infer from context or ask briefly.

2. Email structure

Standard format

Subject line: Clear and specific — the reader should know the topic at a glance
Greeting: Match formality level
Opening: 1-2 sentences stating the purpose or context
Body: Core content, use paragraphs or bullet points for readability
Action items: Clearly state what you need from the recipient and by when
Closing: Polite sign-off
Signature: Add if the user requests it

Reply emails

Acknowledge receipt or thank the sender
Address each point raised
Propose next steps

Follow-up emails

Politely reference the previous message
Briefly restate the context (avoid making the recipient dig through old emails)
State the expected response timeline

3. Tone guide

Scenario	Tone	Example opening
To senior/client	Formal	"Dear Mr./Ms. X, I hope this message finds you well."
To colleague	Semi-formal	"Hi X, regarding our discussion yesterday..."
To familiar partner	Friendly professional	"Hey X, quick follow-up on what we talked about..."

4. Best practices

One email, one topic: Keep each email focused on a single core message
Actionable: Tell the recipient exactly what you need them to do
No ambiguity: Use specific dates (not "next week"), full names
Sensitive content: Remind the user to check for confidential information
CC/BCC: Suggest appropriate recipients if relevant

5. Output format

Output in two parts:

Subject line (labeled separately)
Email body

If the user wants multiple versions (e.g., formal and casual), label each clearly.

Más de este repositorio

mismo repositorio

project-planning

openyak/openyak

Parse a PRD, requirements document, or feature description into a structured task list with dependencies and priorities. Trigger when the user wants to plan a project, break down requirements, create a task list from a document, or says things like "plan this project", "break this down into tasks", "create tasks from this PRD".

2026-03-30700

bootstrap

openyak/openyak

Generate personalized project instructions through an adaptive onboarding conversation. Trigger when the user wants to set up, initialize, or personalize their AI assistant — e.g., "bootstrap my agent", "set up my assistant", "personalize this AI", "let's do onboarding", "create my instructions", or when project instructions are missing. Also trigger for updates like "update my instructions", "change my AI's personality".

2026-03-27700

github-deep-research

openyak/openyak

Conduct multi-round deep research on any GitHub repository. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of a GitHub project. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on GitHub repository URLs or open source project names.

2026-03-27700

charting

openyak/openyak

Create Mermaid diagrams: flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, pie charts, architecture diagrams, and 20+ more types.

2026-03-21700

data-analysis

openyak/openyak

Data analysis and interpretation — tabular data, trend identification, statistical summaries, comparisons, chart recommendations, anomaly detection.

2026-03-21700

document-summary

openyak/openyak

Document summarization and interpretation — long document distillation, multi-level summaries (one-line/paragraph/detailed), key information extraction.

2026-03-21700

name	email
description	Business email writing — formal/informal tone, structured format, replies, follow-ups, multilingual support.

Business Email Writing

When the user asks you to draft an email, follow this workflow:

1. Clarify key details

Before writing, confirm:

Recipient: Who is it for? (manager, colleague, client, external partner)
Purpose: Inform, request, follow up, thank, apologize, invite?
Tone: Formal, semi-formal, or casual?
Language: Match the user's language or ask if bilingual is needed.

If unspecified, infer from context or ask briefly.

2. Email structure

Standard format

Subject line: Clear and specific — the reader should know the topic at a glance
Greeting: Match formality level
Opening: 1-2 sentences stating the purpose or context
Body: Core content, use paragraphs or bullet points for readability
Action items: Clearly state what you need from the recipient and by when
Closing: Polite sign-off
Signature: Add if the user requests it

Reply emails

Acknowledge receipt or thank the sender
Address each point raised
Propose next steps

Follow-up emails

Politely reference the previous message
Briefly restate the context (avoid making the recipient dig through old emails)
State the expected response timeline

3. Tone guide

Scenario	Tone	Example opening
To senior/client	Formal	"Dear Mr./Ms. X, I hope this message finds you well."
To colleague	Semi-formal	"Hi X, regarding our discussion yesterday..."
To familiar partner	Friendly professional	"Hey X, quick follow-up on what we talked about..."

4. Best practices

One email, one topic: Keep each email focused on a single core message
Actionable: Tell the recipient exactly what you need them to do
No ambiguity: Use specific dates (not "next week"), full names
Sensitive content: Remind the user to check for confidential information
CC/BCC: Suggest appropriate recipients if relevant

5. Output format

Output in two parts:

Subject line (labeled separately)
Email body

If the user wants multiple versions (e.g., formal and casual), label each clearly.