How to install linkedin?

getnao/sylph/linkedin

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

Installs into the current project.

Summary

---

Files · 1

View on GitHub

SKILL.md

1	# LinkedIn Post Creator
2
3	```yaml
4	name: linkedin-writer
5	description: >
6	Creates LinkedIn posts across all formats - event announcements, product launches,
7	thought leadership, and community engagement. Handles the full lifecycle from
8	sourcing context through drafting, review, and self-improvement.
9	triggers:
10	- linkedin post
11	- LN post
12	- write a post about
13	```
14
15	---
16
17	## MCP connectors
18
19	\| Connector \| Purpose \|
20	\|-----------\|---------\|
21	\| LinkedIn \| Publish posts, check engagement metrics \|
22
23	## When to Use
24
25	Use this skill whenever a LinkedIn post is needed:
26	- Sharing an article, video, or piece of content
27	- Announcing an event, launch, milestone, or hire
28	- Sharing a contrarian take or industry observation
29	- Community engagement (calls for help, celebrations, vulnerability posts)
30	- Repurposing content from other channels (blog, Substack, talks)
31
32	---
33
34	## Quick Start
35
36	Every LinkedIn post falls into one of four categories. Route to the right sub-file:
37
38	\| Category \| Sub-file \| When \|
39	\|----------\|----------\|------\|
40	\| Events \| `events.md` \| Announcing, recapping, or clustering around events \|
41	\| Launches \| `launches.md` \| Product features, milestones, version releases \|
42	\| Ideas \| `ideas.md` \| Contrarian takes, benchmarks, article shares, thought leadership \|
43	\| Community \| `community.md` \| Mobilization, vulnerability, team celebrations \|
44
45	Read the relevant sub-file for format-specific templates and patterns.
46
47	---
48
49	## Core Writing Principles
50
51	### Tone
52	- Direct and conversational, never corporate
53	- First person singular ("I") unless it is a team moment ("we")
54	- Confident but not arrogant - share what you learned, not what you know
55	- Short sentences. Fragments are fine.
56
57	### Opening Patterns
58	The first line is the post. If it does not stop the scroll, nothing else matters.
59
60	Strong openers:
61	- Contrarian hook: "Most [X] advice is wrong. Here's what actually works."
62	- Specific number: "We went from 0 to 500 users in 3 weeks. No ads."
63	- Question: "Why do analytics teams still spend 80% of their time on data prep?"
64	- Confession: "I almost shut down the company last month."
65	- Bold claim: "[Thing everyone assumes] is dead."
66
67	Weak openers (never use):
68	- "Excited to announce..."
69	- "Thrilled to share..."
70	- "I'm delighted to..."
71	- "Big news!"
72
73	### Generic Post Structure
74	```
75	[Hook - 1-2 lines that stop the scroll]
76
77	[Context - why this matters, what prompted it]
78
79	[Substance - the insight, story, data, or takeaway]
80
81	[Landing - CTA, question, or forward-looking statement]
82	```
83
84	Keep posts between 150-300 words. LinkedIn truncates after ~210 characters, so the hook must land before the "see more" fold.
85
86	---
87
88	## Voice Calibration
89
90	### Structural Preferences
91	- Use line breaks liberally - one thought per line
92	- Bullet points for lists of 3+ items
93	- No walls of text
94	- Emojis: sparingly, max 1-2 per post, never as bullet markers
95	- Hashtags: 3-5 max, at the bottom, relevant to the topic
96
97	### Punctuation Rules
98	- Never use em dashes (--) or en dashes (-) as punctuation. Use a hyphen (-) or colon (:) instead.
99	- Periods over exclamation marks. One exclamation mark per post maximum.
100	- No ellipsis (...) for dramatic effect
101
102	### Voice Tells to Match
103	- Short declarative sentences
104	- "Here's the thing:" as a pivot phrase
105	- "Turns out" to introduce a surprising finding
106	- Direct address to the reader ("If you're a [role]...")
107	- Specific numbers over vague claims
108
109	---
110
111	## Vocabulary to AVOID
112
113	These words and phrases are ghostwriter cliches. Never use them:
114
115	\| Banned \| Why \| Use Instead \|
116	\|--------\|-----\|-------------\|
117	\| "banger" \| Cringe \| "strong post", "it performed well" \|
118	\| "game-changer" \| Overused \| Be specific about what changed \|
119	\| "nails it" \| Vague \| Explain what specifically is good \|
120	\| "had a blast" \| Generic \| Describe the actual experience \|
121	\| "incredibly" \| Filler \| Cut it or use a specific adjective \|
122	\| "leverage" \| Corporate \| "use" \|
123	\| "synergy" \| Corporate \| Describe the actual benefit \|
124	\| "ecosystem" \| Overused \| Be specific \|
125	\| "thought leader" \| Self-aggrandizing \| Never self-apply this label \|
126	\| "deep dive" \| Cliche \| "breakdown", "analysis", "walkthrough" \|
127	\| "unpack" \| Cliche \| "explain", "break down" \|
128	\| "landscape" \| Vague \| Name the specific market or space \|
129	\| "at the end of the day" \| Filler \| Cut entirely \|
130
131	---
132
133	## Sourcing Context Before You Write
134
135	Never write a post from thin air. Always fetch the source material first.
136
137	\| Source Type \| How to Fetch \|
138	\|-------------\|-------------\|
139	\| Article/blog post \| Use `WebFetch` to get the full text \|
140	\| YouTube video \| Use `WebFetch` on the video URL to get metadata; fetch transcript if available \|
141	\| GitHub repo/release \| Use `gh` CLI to read release notes, README, or issue \|
142	\| Internal doc \| Read the file from the repo \|
143	\| Event page \| Use `WebFetch` on the event URL \|
144	\| CRM context \| Use CRM tools to pull customer/deal context \|
145
146	Read the source fully before drafting. Extract:
147	1. The single most interesting claim or data point
148	2. Why it matters to the targe

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 linkedin?

getnao/sylph/linkedin

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

Installs into the current project.

Summary

---

Files · 1

View on GitHub

SKILL.md

1	# LinkedIn Post Creator
2
3	```yaml
4	name: linkedin-writer
5	description: >
6	Creates LinkedIn posts across all formats - event announcements, product launches,
7	thought leadership, and community engagement. Handles the full lifecycle from
8	sourcing context through drafting, review, and self-improvement.
9	triggers:
10	- linkedin post
11	- LN post
12	- write a post about
13	```
14
15	---
16
17	## MCP connectors
18
19	\| Connector \| Purpose \|
20	\|-----------\|---------\|
21	\| LinkedIn \| Publish posts, check engagement metrics \|
22
23	## When to Use
24
25	Use this skill whenever a LinkedIn post is needed:
26	- Sharing an article, video, or piece of content
27	- Announcing an event, launch, milestone, or hire
28	- Sharing a contrarian take or industry observation
29	- Community engagement (calls for help, celebrations, vulnerability posts)
30	- Repurposing content from other channels (blog, Substack, talks)
31
32	---
33
34	## Quick Start
35
36	Every LinkedIn post falls into one of four categories. Route to the right sub-file:
37
38	\| Category \| Sub-file \| When \|
39	\|----------\|----------\|------\|
40	\| Events \| `events.md` \| Announcing, recapping, or clustering around events \|
41	\| Launches \| `launches.md` \| Product features, milestones, version releases \|
42	\| Ideas \| `ideas.md` \| Contrarian takes, benchmarks, article shares, thought leadership \|
43	\| Community \| `community.md` \| Mobilization, vulnerability, team celebrations \|
44
45	Read the relevant sub-file for format-specific templates and patterns.
46
47	---
48
49	## Core Writing Principles
50
51	### Tone
52	- Direct and conversational, never corporate
53	- First person singular ("I") unless it is a team moment ("we")
54	- Confident but not arrogant - share what you learned, not what you know
55	- Short sentences. Fragments are fine.
56
57	### Opening Patterns
58	The first line is the post. If it does not stop the scroll, nothing else matters.
59
60	Strong openers:
61	- Contrarian hook: "Most [X] advice is wrong. Here's what actually works."
62	- Specific number: "We went from 0 to 500 users in 3 weeks. No ads."
63	- Question: "Why do analytics teams still spend 80% of their time on data prep?"
64	- Confession: "I almost shut down the company last month."
65	- Bold claim: "[Thing everyone assumes] is dead."
66
67	Weak openers (never use):
68	- "Excited to announce..."
69	- "Thrilled to share..."
70	- "I'm delighted to..."
71	- "Big news!"
72
73	### Generic Post Structure
74	```
75	[Hook - 1-2 lines that stop the scroll]
76
77	[Context - why this matters, what prompted it]
78
79	[Substance - the insight, story, data, or takeaway]
80
81	[Landing - CTA, question, or forward-looking statement]
82	```
83
84	Keep posts between 150-300 words. LinkedIn truncates after ~210 characters, so the hook must land before the "see more" fold.
85
86	---
87
88	## Voice Calibration
89
90	### Structural Preferences
91	- Use line breaks liberally - one thought per line
92	- Bullet points for lists of 3+ items
93	- No walls of text
94	- Emojis: sparingly, max 1-2 per post, never as bullet markers
95	- Hashtags: 3-5 max, at the bottom, relevant to the topic
96
97	### Punctuation Rules
98	- Never use em dashes (--) or en dashes (-) as punctuation. Use a hyphen (-) or colon (:) instead.
99	- Periods over exclamation marks. One exclamation mark per post maximum.
100	- No ellipsis (...) for dramatic effect
101
102	### Voice Tells to Match
103	- Short declarative sentences
104	- "Here's the thing:" as a pivot phrase
105	- "Turns out" to introduce a surprising finding
106	- Direct address to the reader ("If you're a [role]...")
107	- Specific numbers over vague claims
108
109	---
110
111	## Vocabulary to AVOID
112
113	These words and phrases are ghostwriter cliches. Never use them:
114
115	\| Banned \| Why \| Use Instead \|
116	\|--------\|-----\|-------------\|
117	\| "banger" \| Cringe \| "strong post", "it performed well" \|
118	\| "game-changer" \| Overused \| Be specific about what changed \|
119	\| "nails it" \| Vague \| Explain what specifically is good \|
120	\| "had a blast" \| Generic \| Describe the actual experience \|
121	\| "incredibly" \| Filler \| Cut it or use a specific adjective \|
122	\| "leverage" \| Corporate \| "use" \|
123	\| "synergy" \| Corporate \| Describe the actual benefit \|
124	\| "ecosystem" \| Overused \| Be specific \|
125	\| "thought leader" \| Self-aggrandizing \| Never self-apply this label \|
126	\| "deep dive" \| Cliche \| "breakdown", "analysis", "walkthrough" \|
127	\| "unpack" \| Cliche \| "explain", "break down" \|
128	\| "landscape" \| Vague \| Name the specific market or space \|
129	\| "at the end of the day" \| Filler \| Cut entirely \|
130
131	---
132
133	## Sourcing Context Before You Write
134
135	Never write a post from thin air. Always fetch the source material first.
136
137	\| Source Type \| How to Fetch \|
138	\|-------------\|-------------\|
139	\| Article/blog post \| Use `WebFetch` to get the full text \|
140	\| YouTube video \| Use `WebFetch` on the video URL to get metadata; fetch transcript if available \|
141	\| GitHub repo/release \| Use `gh` CLI to read release notes, README, or issue \|
142	\| Internal doc \| Read the file from the repo \|
143	\| Event page \| Use `WebFetch` on the event URL \|
144	\| CRM context \| Use CRM tools to pull customer/deal context \|
145
146	Read the source fully before drafting. Extract:
147	1. The single most interesting claim or data point
148	2. Why it matters to the targe

People who liked this also viewed

6 picks

Type