How to install newsletter?

getnao/sylph/newsletter

$npx -y skills add getnao/sylph --skill newsletter

Installs into the current project.

Summary

---

Files · 1

View on GitHub

SKILL.md

1	# Newsletter Writer
2
3	```yaml
4	name: newsletter-writer
5	description: >
6	Writes short-form email newsletters. Optimized for open rates,
7	click-throughs, and subscriber retention.
8	triggers:
9	- newsletter
10	- email newsletter
11	- weekly update email
12	```
13
14	---
15
16	## MCP connectors
17
18	\| Connector \| Purpose \|
19	\|-----------\|---------\|
20	\| Email platform \| Send newsletter (e.g., Mailchimp, Substack, ConvertKit) \|
21
22	## What Works
23
24	- Short. 200-400 words max for the main content. Readers skim email.
25	- Hook-first. The first sentence after the subject line determines if they keep reading.
26	- One CTA. Every newsletter has exactly one primary call-to-action. Don't split attention.
27	- Consistent structure. Readers should know what to expect each time.
28	- Personal tone. Write like you're emailing one person, not broadcasting to thousands.
29	- Value upfront. The best newsletters give the takeaway in the email, not behind a click.
30
31	## What Doesn't Work
32
33	- Long intros before getting to the point
34	- Multiple CTAs competing for attention
35	- Generic "this week in [industry]" roundups with no POV
36	- Formal language ("Dear subscriber")
37	- Walls of text without formatting
38
39	---
40
41	## Subject Line Discipline
42
43	The subject line is the most important line. Rules:
44
45	- Under 50 characters (renders fully on mobile)
46	- Specific over clever. "3 things that broke our pipeline" beats "Newsletter #47"
47	- No ALL CAPS or excessive punctuation
48	- Preview text (preheader) should extend the subject, not repeat it
49
50	\| Good Subject \| Bad Subject \|
51	\|-------------\|------------\|
52	\| "We tested 5 tools. One stood out." \| "Weekly Update #23" \|
53	\| "The metric nobody tracks (but should)" \| "Important News Inside!" \|
54	\| "What I got wrong about [topic]" \| "Don't Miss This!!" \|
55
56	---
57
58	## Newsletter Structure
59
60	```
61	[Subject Line]
62	[Preheader text - extends the subject]
63
64	[Greeting - casual, first name if available]
65
66	[Hook - 1-2 sentences, the reason to keep reading]
67
68	[Body - the substance, 2-4 short paragraphs or bullet points]
69
70	[CTA - one clear action: read, try, reply, register]
71
72	[Sign-off - brief, personal]
73
74	[P.S. - optional, for a secondary link or personal note]
75	```
76
77	---
78
79	## Formatting Rules
80
81	- Short paragraphs: 2-3 sentences max
82	- Use bold for key phrases readers need to catch while scanning
83	- Bullet points for lists
84	- One link per CTA (don't scatter links everywhere)
85	- P.S. lines get read more than body text - use them strategically
86
87	---
88
89	## Self-Improvement Step
90
91	After each send:
92
93	1. Record open rate, click rate, and unsubscribe count in frontmatter
94	2. Compare subject line patterns: which styles drive opens?
95	3. Compare CTA patterns: which placements drive clicks?
96	4. Update `content/newsletter/_insights.md` with findings
97	5. Promote high-performing issues to `content/newsletter/_examples/`

People who liked this also viewed

6 picks

Type

seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026168k41k
copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026159k41k
marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026116k41k
content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026111k41k
programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026107k41k
marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026104k41k

168stars52forks

View on GitHub

How to install newsletter?

getnao/sylph/newsletter

$npx -y skills add getnao/sylph --skill newsletter

Installs into the current project.

Summary

---

Files · 1

View on GitHub

SKILL.md

1	# Newsletter Writer
2
3	```yaml
4	name: newsletter-writer
5	description: >
6	Writes short-form email newsletters. Optimized for open rates,
7	click-throughs, and subscriber retention.
8	triggers:
9	- newsletter
10	- email newsletter
11	- weekly update email
12	```
13
14	---
15
16	## MCP connectors
17
18	\| Connector \| Purpose \|
19	\|-----------\|---------\|
20	\| Email platform \| Send newsletter (e.g., Mailchimp, Substack, ConvertKit) \|
21
22	## What Works
23
24	- Short. 200-400 words max for the main content. Readers skim email.
25	- Hook-first. The first sentence after the subject line determines if they keep reading.
26	- One CTA. Every newsletter has exactly one primary call-to-action. Don't split attention.
27	- Consistent structure. Readers should know what to expect each time.
28	- Personal tone. Write like you're emailing one person, not broadcasting to thousands.
29	- Value upfront. The best newsletters give the takeaway in the email, not behind a click.
30
31	## What Doesn't Work
32
33	- Long intros before getting to the point
34	- Multiple CTAs competing for attention
35	- Generic "this week in [industry]" roundups with no POV
36	- Formal language ("Dear subscriber")
37	- Walls of text without formatting
38
39	---
40
41	## Subject Line Discipline
42
43	The subject line is the most important line. Rules:
44
45	- Under 50 characters (renders fully on mobile)
46	- Specific over clever. "3 things that broke our pipeline" beats "Newsletter #47"
47	- No ALL CAPS or excessive punctuation
48	- Preview text (preheader) should extend the subject, not repeat it
49
50	\| Good Subject \| Bad Subject \|
51	\|-------------\|------------\|
52	\| "We tested 5 tools. One stood out." \| "Weekly Update #23" \|
53	\| "The metric nobody tracks (but should)" \| "Important News Inside!" \|
54	\| "What I got wrong about [topic]" \| "Don't Miss This!!" \|
55
56	---
57
58	## Newsletter Structure
59
60	```
61	[Subject Line]
62	[Preheader text - extends the subject]
63
64	[Greeting - casual, first name if available]
65
66	[Hook - 1-2 sentences, the reason to keep reading]
67
68	[Body - the substance, 2-4 short paragraphs or bullet points]
69
70	[CTA - one clear action: read, try, reply, register]
71
72	[Sign-off - brief, personal]
73
74	[P.S. - optional, for a secondary link or personal note]
75	```
76
77	---
78
79	## Formatting Rules
80
81	- Short paragraphs: 2-3 sentences max
82	- Use bold for key phrases readers need to catch while scanning
83	- Bullet points for lists
84	- One link per CTA (don't scatter links everywhere)
85	- P.S. lines get read more than body text - use them strategically
86
87	---
88
89	## Self-Improvement Step
90
91	After each send:
92
93	1. Record open rate, click rate, and unsubscribe count in frontmatter
94	2. Compare subject line patterns: which styles drive opens?
95	3. Compare CTA patterns: which placements drive clicks?
96	4. Update `content/newsletter/_insights.md` with findings
97	5. Promote high-performing issues to `content/newsletter/_examples/`

People who liked this also viewed

6 picks

Type