linkedin-technical

Name: linkedin-technical
Author: jonathimer

81installs6forks

How to install linkedin-technical?

jonathimer/devmarketing-skills/linkedin-technical

$npx -y skills add jonathimer/devmarketing-skills --skill linkedin-technical

Installs into the current project.

Summary

When the user wants to reach developers on LinkedIn, create technical content for B2B audiences, or understand when LinkedIn beats Twitter. Trigger phrases include "LinkedIn," "LinkedIn for developers," "B2B developer marketing," "engineering managers," "reaching CTOs," or "techn

Files · 1

View on GitHub

SKILL.md

1	# LinkedIn for Technical Audiences
2
3	LinkedIn is where B2B developer tools win deals. This skill covers technical content that works on LinkedIn, reaching engineering managers and decision-makers, and knowing when LinkedIn beats Twitter.
4
5	---
6
7	## Before You Start
8
9	1. Read `.agents/developer-audience-context.md` if it exists
10	2. Assess your LinkedIn presence (profile, connections, content history)
11	3. Understand: LinkedIn rewards different content than developer Twitter
12
13	---
14
15	## When LinkedIn Beats Twitter
16
17	### LinkedIn's Unique Value
18
19	\| Factor \| LinkedIn advantage \|
20	\|--------\|-------------------\|
21	\| B2B decisions \| Decision-makers are here \|
22	\| Enterprise reach \| CTOs, VPs, directors active \|
23	\| Company context \| See role, company, team size \|
24	\| Professional network \| Second-degree reach is valuable \|
25	\| Long-form content \| Articles rank in Google \|
26	\| Lead generation \| Built-in company/role targeting \|
27
28	### Use LinkedIn When
29
30	\| Scenario \| Why \|
31	\|----------\|-----\|
32	\| Selling to enterprises \| Buyers are on LinkedIn \|
33	\| Reaching engineering managers \| More managers here than Twitter \|
34	\| Recruiting developer users \| Professional context \|
35	\| B2B partnerships \| Companies > individuals \|
36	\| Industry/vertical targeting \| Company data available \|
37	\| Longer professional content \| Newsletters, articles \|
38
39	### Use Twitter When
40
41	\| Scenario \| Why \|
42	\|----------\|-----\|
43	\| Individual developers \| More devs on Twitter \|
44	\| Real-time engagement \| Faster conversation \|
45	\| Open source projects \| Community is on Twitter \|
46	\| Casual/authentic voice \| LinkedIn is more formal \|
47	\| Technical hot takes \| Twitter thrives on debate \|
48
49	---
50
51	## Understanding LinkedIn's Audience
52
53	### Who's Actually Active
54
55	\| Segment \| Engagement level \| What they consume \|
56	\|---------\|------------------\|-------------------\|
57	\| Engineering managers \| High \| Leadership, team building \|
58	\| CTOs/VPs Engineering \| Medium \| Strategy, industry trends \|
59	\| Tech recruiters \| Very high \| Talent, employer branding \|
60	\| DevRel/Developer advocates \| High \| Community, content tactics \|
61	\| Solution architects \| Medium \| Technical evaluations \|
62	\| Individual developers \| Lower \| Career, learning \|
63
64	### What LinkedIn Values
65
66	\| Content type \| Performance \| Notes \|
67	\|--------------\|-------------\|-------\|
68	\| Personal stories \| Very high \| LinkedIn loves narrative \|
69	\| Career lessons \| High \| Professional growth content \|
70	\| Contrarian opinions \| High \| "Unpopular opinion:" works \|
71	\| Behind-the-scenes \| High \| Company/team stories \|
72	\| Technical deep dives \| Medium \| More accessible than Twitter \|
73	\| Plain announcements \| Low \| Need personal angle \|
74	\| Shared links \| Very low \| Algorithm deprioritizes \|
75
76	---
77
78	## Content That Works
79
80	### The LinkedIn Technical Post Formula
81
82	```
83	[Hook: Personal statement or question]
84
85	[Short paragraph: The context or problem]
86
87	[Bullet points: 3-5 key insights]
88
89	[Personal take: What you learned]
90
91	[CTA: Question or action]
92
93	---
94
95	[Hashtags: 3-5 relevant ones]
96	```
97
98	### Example Formats
99
100	The "Here's What Happened" Post:
101	```
102	Last month we migrated 2TB of data from MongoDB to PostgreSQL.
103
104	Here's what we learned (and what we'd do differently):
105
106	→ Start with a test migration
107	We didn't. Cost us 3 days.
108
109	→ Schema mapping is 80% of the work
110	The actual migration is easy.
111
112	→ Watch for timezone handling
113	MongoDB stores UTC, Postgres respects your settings.
114
115	→ Have a rollback plan
116	Ours worked. Twice.
117
118	The migration took 4 days total, not the "weekend project" we planned.
119
120	What's your biggest database migration war story?
121
122	#engineering #databases #postgresql
123	```
124
125	The "Unpopular Opinion" Post:
126	```
127	Unpopular opinion: Most engineering teams don't need Kubernetes.
128
129	I've seen 3-person startups running K8s because "Netflix uses it."
130
131	The reality:
132	• Single container on Railway/Render: $20/month
133	• Managed K8s: $300/month minimum
134	• Self-hosted K8s: 1 FTE just for maintenance
135
136	Kubernetes is amazing for:
137	→ Multi-region deployments
138	→ Complex orchestration needs
139	→ 99.99% SLA requirements
140
141	But most apps? Docker Compose on a VM is fine.
142
143	What's the smallest team you've seen running Kubernetes?
144
145	#devops #kubernetes #startups
146	```
147
148	The "Behind the Scenes" Post:
149	```
150	We just hit 10,000 API calls per second.
151
152	Here's the unsexy truth about scaling:
153
154	6 months ago we could barely handle 1,000 req/s.
155
156	What changed:
157	→ Moved hot paths to Redis
158	→ Implemented connection pooling (finally)
159	→ Added CDN for static assets
160	→ Profiled and found 3 N+1 queries
161
162	No fancy architecture. No rewrite.
163	Just fixing obvious stuff we'd ignored.
164
165	The lesson: Optimize boring things first.
166
167	What's the simplest optimization t

People who liked this also viewed

6 picks

Type

linkedin-technical

81installs6forks

View on GitHub

How to install linkedin-technical?

jonathimer/devmarketing-skills/linkedin-technical

$npx -y skills add jonathimer/devmarketing-skills --skill linkedin-technical

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# LinkedIn for Technical Audiences
2
3	LinkedIn is where B2B developer tools win deals. This skill covers technical content that works on LinkedIn, reaching engineering managers and decision-makers, and knowing when LinkedIn beats Twitter.
4
5	---
6
7	## Before You Start
8
9	1. Read `.agents/developer-audience-context.md` if it exists
10	2. Assess your LinkedIn presence (profile, connections, content history)
11	3. Understand: LinkedIn rewards different content than developer Twitter
12
13	---
14
15	## When LinkedIn Beats Twitter
16
17	### LinkedIn's Unique Value
18
19	\| Factor \| LinkedIn advantage \|
20	\|--------\|-------------------\|
21	\| B2B decisions \| Decision-makers are here \|
22	\| Enterprise reach \| CTOs, VPs, directors active \|
23	\| Company context \| See role, company, team size \|
24	\| Professional network \| Second-degree reach is valuable \|
25	\| Long-form content \| Articles rank in Google \|
26	\| Lead generation \| Built-in company/role targeting \|
27
28	### Use LinkedIn When
29
30	\| Scenario \| Why \|
31	\|----------\|-----\|
32	\| Selling to enterprises \| Buyers are on LinkedIn \|
33	\| Reaching engineering managers \| More managers here than Twitter \|
34	\| Recruiting developer users \| Professional context \|
35	\| B2B partnerships \| Companies > individuals \|
36	\| Industry/vertical targeting \| Company data available \|
37	\| Longer professional content \| Newsletters, articles \|
38
39	### Use Twitter When
40
41	\| Scenario \| Why \|
42	\|----------\|-----\|
43	\| Individual developers \| More devs on Twitter \|
44	\| Real-time engagement \| Faster conversation \|
45	\| Open source projects \| Community is on Twitter \|
46	\| Casual/authentic voice \| LinkedIn is more formal \|
47	\| Technical hot takes \| Twitter thrives on debate \|
48
49	---
50
51	## Understanding LinkedIn's Audience
52
53	### Who's Actually Active
54
55	\| Segment \| Engagement level \| What they consume \|
56	\|---------\|------------------\|-------------------\|
57	\| Engineering managers \| High \| Leadership, team building \|
58	\| CTOs/VPs Engineering \| Medium \| Strategy, industry trends \|
59	\| Tech recruiters \| Very high \| Talent, employer branding \|
60	\| DevRel/Developer advocates \| High \| Community, content tactics \|
61	\| Solution architects \| Medium \| Technical evaluations \|
62	\| Individual developers \| Lower \| Career, learning \|
63
64	### What LinkedIn Values
65
66	\| Content type \| Performance \| Notes \|
67	\|--------------\|-------------\|-------\|
68	\| Personal stories \| Very high \| LinkedIn loves narrative \|
69	\| Career lessons \| High \| Professional growth content \|
70	\| Contrarian opinions \| High \| "Unpopular opinion:" works \|
71	\| Behind-the-scenes \| High \| Company/team stories \|
72	\| Technical deep dives \| Medium \| More accessible than Twitter \|
73	\| Plain announcements \| Low \| Need personal angle \|
74	\| Shared links \| Very low \| Algorithm deprioritizes \|
75
76	---
77
78	## Content That Works
79
80	### The LinkedIn Technical Post Formula
81
82	```
83	[Hook: Personal statement or question]
84
85	[Short paragraph: The context or problem]
86
87	[Bullet points: 3-5 key insights]
88
89	[Personal take: What you learned]
90
91	[CTA: Question or action]
92
93	---
94
95	[Hashtags: 3-5 relevant ones]
96	```
97
98	### Example Formats
99
100	The "Here's What Happened" Post:
101	```
102	Last month we migrated 2TB of data from MongoDB to PostgreSQL.
103
104	Here's what we learned (and what we'd do differently):
105
106	→ Start with a test migration
107	We didn't. Cost us 3 days.
108
109	→ Schema mapping is 80% of the work
110	The actual migration is easy.
111
112	→ Watch for timezone handling
113	MongoDB stores UTC, Postgres respects your settings.
114
115	→ Have a rollback plan
116	Ours worked. Twice.
117
118	The migration took 4 days total, not the "weekend project" we planned.
119
120	What's your biggest database migration war story?
121
122	#engineering #databases #postgresql
123	```
124
125	The "Unpopular Opinion" Post:
126	```
127	Unpopular opinion: Most engineering teams don't need Kubernetes.
128
129	I've seen 3-person startups running K8s because "Netflix uses it."
130
131	The reality:
132	• Single container on Railway/Render: $20/month
133	• Managed K8s: $300/month minimum
134	• Self-hosted K8s: 1 FTE just for maintenance
135
136	Kubernetes is amazing for:
137	→ Multi-region deployments
138	→ Complex orchestration needs
139	→ 99.99% SLA requirements
140
141	But most apps? Docker Compose on a VM is fine.
142
143	What's the smallest team you've seen running Kubernetes?
144
145	#devops #kubernetes #startups
146	```
147
148	The "Behind the Scenes" Post:
149	```
150	We just hit 10,000 API calls per second.
151
152	Here's the unsexy truth about scaling:
153
154	6 months ago we could barely handle 1,000 req/s.
155
156	What changed:
157	→ Moved hot paths to Redis
158	→ Implemented connection pooling (finally)
159	→ Added CDN for static assets
160	→ Profiled and found 3 N+1 queries
161
162	No fancy architecture. No rewrite.
163	Just fixing obvious stuff we'd ignored.
164
165	The lesson: Optimize boring things first.
166
167	What's the simplest optimization t

People who liked this also viewed

6 picks

Type