email-writer

Name: email-writer
Author: getnao

168stars52forks

How to install email-writer?

getnao/sylph/email-writer

$npx -y skills add getnao/sylph --skill email-writer

Installs into the current project.

Summary

---

Files · 1

View on GitHub

SKILL.md

1	# Email Drafting Skill
2
3	```yaml
4	name: email-writer
5	description: >
6	Drafts emails in the user's authentic voice and tone. Handles replies,
7	cold outreach, follow-ups, introductions, and internal communication.
8	Used by zero-inbox and any email drafting task.
9	triggers:
10	- draft an email
11	- reply to this email
12	- write an email
13	- email response
14	```
15
16	---
17
18	## MCP connectors
19
20	\| Connector \| Purpose \|
21	\|-----------\|---------\|
22	\| Gmail \| Send drafted emails \|
23
24	## Greetings
25
26	Match formality to the relationship:
27
28	<!-- Customize: add columns for each language the CAO writes in. Run /sylph-setup-skill email to auto-configure. -->
29
30	\| Relationship \| English \| [Other language] \|
31	\|-------------\|---------\|--------\|
32	\| Friends / close peers \| "Hey [name]," \| [casual greeting] \|
33	\| Colleagues / warm contacts \| "Hi [name]," \| [warm greeting] \|
34	\| Prospects / cold contacts \| "Hello [name]," \| [formal greeting] \|
35	\| Formal / unknown \| "Dear [name]," \| [formal greeting] \|
36
37	Always follow the greeting with a warm opener:
38	- English: "Hope you're doing well!"
39	- [Other language]: [equivalent warm opener]
40
41	Never skip the opener. It bridges the greeting and the body.
42
43	---
44
45	## Closings
46
47	<!-- Customize: match language columns to your Greetings table above. -->
48
49	\| Context \| English \| [Other language] \|
50	\|---------\|---------\|--------\|
51	\| Warm / friendly \| "Best," \| [warm closing] \|
52	\| Professional \| "Thanks," \| [professional closing] \|
53	\| After a request \| "Thanks in advance," \| [request closing] \|
54	\| Formal \| "Kind regards," \| [formal closing] \|
55	\| Internal / quick \| "Cheers," \| [casual closing] \|
56
57	---
58
59	## Structure Pattern
60
61	Every email follows this three-part structure:
62
63	### 1. Acknowledge
64	Reference the context: what they said, what happened, or why you're writing.
65	- Reply: "Thanks for sending this over."
66	- Cold: "I came across [specific thing] and wanted to reach out."
67	- Follow-up: "Just circling back on our conversation from [date]."
68
69	### 2. Answer / Content
70	The substance of the email. Keep it tight:
71	- One main point per paragraph
72	- If there are multiple items, use bullet points
73	- If there's a question, answer it directly before adding context
74
75	### 3. Next Step
76	Always end with a clear next action:
77	- "Let me know if [specific question]."
78	- "Want to jump on a quick call this week?"
79	- "I'll send the doc by Friday."
80
81	Never end an email without a next step. Even "No action needed on your end" is a next step.
82
83	---
84
85	## Language Matching
86
87	Match the language of the thread. If the incoming email is in French, reply in French. If it is in English, reply in English. If the thread switches languages, follow the most recent message.
88
89	Do not ask the user which language to use. Just match.
90
91	---
92
93	## Presentation Rules
94
95	- Plain text only. Never wrap drafts in blockquotes (`>`), code blocks, or italic formatting.
96	- Copy-pasteable. The draft should be ready to paste directly into an email client.
97	- No subject line unless asked. If replying, the subject already exists.
98	- For new emails, suggest a subject line separately above the body.
99
100	---
101
102	## Storage Rule
103
104	Email drafts go to the email client only, never to the repo.
105
106	Do not save email drafts to `content/` or `_drafts/` folders. Emails are ephemeral and belong in the email tool (Gmail, Outlook, etc.) or in the conversation. The only exception is outbound campaign templates, which go in `sales/outbound/campaigns/`.
107
108	---
109
110	## Tone Calibration
111
112	- Write like a real person, not a bot
113	- Short sentences. Get to the point.
114	- Confident but not pushy
115	- Warm but not sycophantic
116	- Match the energy of the sender (casual thread = casual reply)
117
118	---
119
120	## What NOT to Do
121
122	\| Don't \| Why \| Do Instead \|
123	\|-------\|-----\|------------\|
124	\| Start with "I hope this email finds you well" \| Cliche, robotic \| Use the standard opener for the relationship \|
125	\| Write paragraphs longer than 3 sentences \| Nobody reads long email paragraphs \| Break it up or use bullets \|
126	\| Use "per my last email" \| Passive-aggressive \| Reference the specific point directly \|
127	\| CC people without reason \| Creates noise \| Only CC people who need to act or be informed \|
128	\| Use em dashes (--) \| Formatting rule \| Use hyphens (-) or colons (:) \|
129	\| End without a next step \| Leaves the thread hanging \| Always state what happens next \|
130	\| Use "please do the needful" \| Dated and unclear \| Be specific about what you need \|
131	\| Over-apologize \| Undermines confidence \| Acknowledge once, then move forward \|
132	\| Write "As per our discussion" \| Stiff \| "Following up on our chat" or just reference the topic \|
133	\| Add a signature block \| The email client handles this \| Just end with the closing \|
134	\| Save drafts to the repo \| Emails are ephemeral \| Send via email tool or present in conversation \|
135	\| Invent a tone the user hasn't used \| Feels off-brand \| Match previous emails from the user \|
136
137	## Self-improvement
138
139	After the CAO edits an email draft before sending:
140
141	1. Diff what was drafted vs what she sent - identify patterns in her edits to tone, structure, or phrasing

People who liked this also viewed

6 picks

Type

email-writer

168stars52forks

View on GitHub

How to install email-writer?

getnao/sylph/email-writer

$npx -y skills add getnao/sylph --skill email-writer

Installs into the current project.

Summary

---

Files · 1

View on GitHub

SKILL.md

1	# Email Drafting Skill
2
3	```yaml
4	name: email-writer
5	description: >
6	Drafts emails in the user's authentic voice and tone. Handles replies,
7	cold outreach, follow-ups, introductions, and internal communication.
8	Used by zero-inbox and any email drafting task.
9	triggers:
10	- draft an email
11	- reply to this email
12	- write an email
13	- email response
14	```
15
16	---
17
18	## MCP connectors
19
20	\| Connector \| Purpose \|
21	\|-----------\|---------\|
22	\| Gmail \| Send drafted emails \|
23
24	## Greetings
25
26	Match formality to the relationship:
27
28	<!-- Customize: add columns for each language the CAO writes in. Run /sylph-setup-skill email to auto-configure. -->
29
30	\| Relationship \| English \| [Other language] \|
31	\|-------------\|---------\|--------\|
32	\| Friends / close peers \| "Hey [name]," \| [casual greeting] \|
33	\| Colleagues / warm contacts \| "Hi [name]," \| [warm greeting] \|
34	\| Prospects / cold contacts \| "Hello [name]," \| [formal greeting] \|
35	\| Formal / unknown \| "Dear [name]," \| [formal greeting] \|
36
37	Always follow the greeting with a warm opener:
38	- English: "Hope you're doing well!"
39	- [Other language]: [equivalent warm opener]
40
41	Never skip the opener. It bridges the greeting and the body.
42
43	---
44
45	## Closings
46
47	<!-- Customize: match language columns to your Greetings table above. -->
48
49	\| Context \| English \| [Other language] \|
50	\|---------\|---------\|--------\|
51	\| Warm / friendly \| "Best," \| [warm closing] \|
52	\| Professional \| "Thanks," \| [professional closing] \|
53	\| After a request \| "Thanks in advance," \| [request closing] \|
54	\| Formal \| "Kind regards," \| [formal closing] \|
55	\| Internal / quick \| "Cheers," \| [casual closing] \|
56
57	---
58
59	## Structure Pattern
60
61	Every email follows this three-part structure:
62
63	### 1. Acknowledge
64	Reference the context: what they said, what happened, or why you're writing.
65	- Reply: "Thanks for sending this over."
66	- Cold: "I came across [specific thing] and wanted to reach out."
67	- Follow-up: "Just circling back on our conversation from [date]."
68
69	### 2. Answer / Content
70	The substance of the email. Keep it tight:
71	- One main point per paragraph
72	- If there are multiple items, use bullet points
73	- If there's a question, answer it directly before adding context
74
75	### 3. Next Step
76	Always end with a clear next action:
77	- "Let me know if [specific question]."
78	- "Want to jump on a quick call this week?"
79	- "I'll send the doc by Friday."
80
81	Never end an email without a next step. Even "No action needed on your end" is a next step.
82
83	---
84
85	## Language Matching
86
87	Match the language of the thread. If the incoming email is in French, reply in French. If it is in English, reply in English. If the thread switches languages, follow the most recent message.
88
89	Do not ask the user which language to use. Just match.
90
91	---
92
93	## Presentation Rules
94
95	- Plain text only. Never wrap drafts in blockquotes (`>`), code blocks, or italic formatting.
96	- Copy-pasteable. The draft should be ready to paste directly into an email client.
97	- No subject line unless asked. If replying, the subject already exists.
98	- For new emails, suggest a subject line separately above the body.
99
100	---
101
102	## Storage Rule
103
104	Email drafts go to the email client only, never to the repo.
105
106	Do not save email drafts to `content/` or `_drafts/` folders. Emails are ephemeral and belong in the email tool (Gmail, Outlook, etc.) or in the conversation. The only exception is outbound campaign templates, which go in `sales/outbound/campaigns/`.
107
108	---
109
110	## Tone Calibration
111
112	- Write like a real person, not a bot
113	- Short sentences. Get to the point.
114	- Confident but not pushy
115	- Warm but not sycophantic
116	- Match the energy of the sender (casual thread = casual reply)
117
118	---
119
120	## What NOT to Do
121
122	\| Don't \| Why \| Do Instead \|
123	\|-------\|-----\|------------\|
124	\| Start with "I hope this email finds you well" \| Cliche, robotic \| Use the standard opener for the relationship \|
125	\| Write paragraphs longer than 3 sentences \| Nobody reads long email paragraphs \| Break it up or use bullets \|
126	\| Use "per my last email" \| Passive-aggressive \| Reference the specific point directly \|
127	\| CC people without reason \| Creates noise \| Only CC people who need to act or be informed \|
128	\| Use em dashes (--) \| Formatting rule \| Use hyphens (-) or colons (:) \|
129	\| End without a next step \| Leaves the thread hanging \| Always state what happens next \|
130	\| Use "please do the needful" \| Dated and unclear \| Be specific about what you need \|
131	\| Over-apologize \| Undermines confidence \| Acknowledge once, then move forward \|
132	\| Write "As per our discussion" \| Stiff \| "Following up on our chat" or just reference the topic \|
133	\| Add a signature block \| The email client handles this \| Just end with the closing \|
134	\| Save drafts to the repo \| Emails are ephemeral \| Send via email tool or present in conversation \|
135	\| Invent a tone the user hasn't used \| Feels off-brand \| Match previous emails from the user \|
136
137	## Self-improvement
138
139	After the CAO edits an email draft before sending:
140
141	1. Diff what was drafted vs what she sent - identify patterns in her edits to tone, structure, or phrasing

People who liked this also viewed

6 picks

Type