AGENT SKILLBY JONATHIMER
LinkedIn technical
AT A GLANCE
LinkedIn technical is a social media agent skill from jonathimer. LinkedIn is where B2B developer tools win deals. The jonathimer/devmarketing-skills repository on GitHub has 80 stars and the MIT license. Its SKILL.md runs to about 2,300 words. To add it, run npx skills add jonathimer/devmarketing-skills --skill linkedin-technical
- SOURCE REPOSITORY
- jonathimer/devmarketing-skills (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 13.7 KB516 LINES
QUICK ANSWER
- WHAT IT IS01
- 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. It stands out by giving social content a defined shape, so the agent asks for better context and returns a more usable result.
- INPUTS02
- Context for social content: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for social content: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add jonathimer/devmarketing-skills --skill linkedin-technicalREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 27
LinkedIn for Technical Audiences#
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.
Before You Start#
- Read
.agents/developer-audience-context.mdif it exists - Assess your LinkedIn presence (profile, connections, content history)
- Understand: LinkedIn rewards different content than developer Twitter
When LinkedIn Beats Twitter#
LinkedIn's Unique Value#
| Factor | LinkedIn advantage |
|---|---|
| B2B decisions | Decision-makers are here |
| Enterprise reach | CTOs, VPs, directors active |
| Company context | See role, company, team size |
| Professional network | Second-degree reach is valuable |
| Long-form content | Articles rank in Google |
| Lead generation | Built-in company/role targeting |
Use LinkedIn When#
| Scenario | Why |
|---|---|
| Selling to enterprises | Buyers are on LinkedIn |
| Reaching engineering managers | More managers here than Twitter |
| Recruiting developer users | Professional context |
| B2B partnerships | Companies > individuals |
| Industry/vertical targeting | Company data available |
| Longer professional content | Newsletters, articles |
Use Twitter When#
| Scenario | Why |
|---|---|
| Individual developers | More devs on Twitter |
| Real-time engagement | Faster conversation |
| Open source projects | Community is on Twitter |
| Casual/authentic voice | LinkedIn is more formal |
| Technical hot takes | Twitter thrives on debate |
Understanding LinkedIn's Audience#
Who's Actually Active#
| Segment | Engagement level | What they consume |
|---|---|---|
| Engineering managers | High | Leadership, team building |
| CTOs/VPs Engineering | Medium | Strategy, industry trends |
| Tech recruiters | Very high | Talent, employer branding |
| DevRel/Developer advocates | High | Community, content tactics |
| Solution architects | Medium | Technical evaluations |
| Individual developers | Lower | Career, learning |
What LinkedIn Values#
| Content type | Performance | Notes |
|---|---|---|
| Personal stories | Very high | LinkedIn loves narrative |
| Career lessons | High | Professional growth content |
| Contrarian opinions | High | "Unpopular opinion:" works |
| Behind-the-scenes | High | Company/team stories |
| Technical deep dives | Medium | More accessible than Twitter |
| Plain announcements | Low | Need personal angle |
| Shared links | Very low | Algorithm deprioritizes |
Content That Works#
The LinkedIn Technical Post Formula#
[Hook: Personal statement or question]
[Short paragraph: The context or problem]
[Bullet points: 3-5 key insights]
[Personal take: What you learned]
[CTA: Question or action]
---
[Hashtags: 3-5 relevant ones]Example Formats#
The "Here's What Happened" Post:
Last month we migrated 2TB of data from MongoDB to PostgreSQL.
Here's what we learned (and what we'd do differently):
→ Start with a test migration
We didn't. Cost us 3 days.
→ Schema mapping is 80% of the work
The actual migration is easy.
→ Watch for timezone handling
MongoDB stores UTC, Postgres respects your settings.
→ Have a rollback plan
Ours worked. Twice.
The migration took 4 days total, not the "weekend project" we planned.
What's your biggest database migration war story?
#engineering #databases #postgresqlThe "Unpopular Opinion" Post:
Unpopular opinion: Most engineering teams don't need Kubernetes.
I've seen 3-person startups running K8s because "Netflix uses it."
The reality:
• Single container on Railway/Render: $20/month
• Managed K8s: $300/month minimum
• Self-hosted K8s: 1 FTE just for maintenance
Kubernetes is amazing for:
→ Multi-region deployments
→ Complex orchestration needs
→ 99.99% SLA requirements
But most apps? Docker Compose on a VM is fine.
What's the smallest team you've seen running Kubernetes?
#devops #kubernetes #startupsThe "Behind the Scenes" Post:
We just hit 10,000 API calls per second.
Here's the unsexy truth about scaling:
6 months ago we could barely handle 1,000 req/s.
What changed:
→ Moved hot paths to Redis
→ Implemented connection pooling (finally)
→ Added CDN for static assets
→ Profiled and found 3 N+1 queries
No fancy architecture. No rewrite.
Just fixing obvious stuff we'd ignored.
The lesson: Optimize boring things first.
What's the simplest optimization that made your biggest impact?Content Mix for LinkedIn#
| Type | Percentage | Purpose |
|---|---|---|
| Personal insights | 40% | Build authority |
| Technical content | 30% | Demonstrate expertise |
| Company/team stories | 20% | Employer branding |
| Promotional | 10% | Actual asks |
Formatting Best Practices#
Post Structure#
| Element | Guideline |
|---|---|
| First line | Hook — make them click "see more" |
| Length | 1,200-1,500 characters optimal |
| Line breaks | Every 1-2 sentences |
| White space | Use blank lines liberally |
| Emojis | Sparingly, for bullets (→, •) |
| Hashtags | 3-5 at the end |
What Gets Hidden#
LinkedIn truncates after ~210 characters. Your first 2-3 lines are critical.
Bad hook (no curiosity gap):
I wanted to share some thoughts about microservices.Good hook (creates curiosity):
We ripped out our microservices architecture.
Here's why going back to a monolith was the right call:Visual Content#
| Format | Performance | Use for |
|---|---|---|
| Carousels (PDF) | Very high | Step-by-step, lists |
| Native video | High | Demos, explanations |
| Images | Medium | Diagrams, screenshots |
| Text only | Medium | Stories, opinions |
| Links | Low | External content |
Carousel tips:
- 5-10 slides optimal
- First slide = thumbnail (make it count)
- Large text, minimal per slide
- Upload as PDF for carousel effect
Company Page vs Personal#
When to Use Each#
| Use Case | Company Page | Personal Profile |
|---|---|---|
| Product announcements | ✓ | Cross-post |
| Company news | ✓ | Leadership shares |
| Industry thought leadership | ✓ | |
| Technical insights | ✓ | |
| Hiring posts | ✓ | Hiring manager shares |
| Customer stories | ✓ | Personal angle helps |
The Reality#
| Metric | Company Pages | Personal Profiles |
|---|---|---|
| Organic reach | Low (2-5%) | Higher (10-20%) |
| Engagement | Lower | Higher |
| Following growth | Slow | Faster |
| Lead gen tools | Available | Limited |
| Analytics | Better | Basic |
Strategy: Post from company page, have team members share with personal commentary.
Reaching Engineering Managers#
What Engineering Managers Care About#
| Topic | Why it resonates |
|---|---|
| Team productivity | Their main metric |
| Hiring/retention | Constant challenge |
| Technical decisions | Balancing team + business |
| Developer experience | Team satisfaction |
| Technical debt | Constant negotiation |
| Process improvements | Making teams effective |
Content Angles for EM Audience#
| Angle | Example hook |
|---|---|
| Metrics | "The 3 metrics our team tracks (and 5 we stopped tracking)" |
| Process | "How we cut our sprint planning from 4 hours to 45 minutes" |
| Hiring | "The technical interview question that tells us the most" |
| Tech decisions | "Why we chose boring technology for our startup" |
| Team building | "What I learned managing my first remote team" |
Hashtags#
Technical Hashtags That Work#
| Hashtag | Audience |
|---|---|
| #engineering | Broad engineering |
| #softwaredevelopment | General dev |
| #webdevelopment | Web devs |
| #devops | DevOps/SRE |
| #cloudcomputing | Cloud/infra |
| #startup | Startup audience |
| #techleadership | EMs, VPs |
| #remotework | Remote teams |
| #hiring | Recruiting context |
| #opensource | OSS community |
Hashtag Rules#
- 3-5 hashtags maximum
- Put at the end of post
- Mix broad (#engineering) and specific (#kubernetes)
- Skip if post is personal/narrative
Platform-Specific Do's and Don'ts#
Do's#
- Do write posts, not status updates
- Do use line breaks liberally
- Do start with a hook
- Do share personal experiences
- Do engage in comments (first hour matters)
- Do cross-post from company page personally
- Do use carousels for educational content
- Do mention people and companies when relevant
Don'ts#
- Don't post just links (algorithm kills them)
- Don't use LinkedIn like Twitter
- Don't over-hashtag (looks spammy)
- Don't be too promotional
- Don't ignore comments
- Don't post walls of text without breaks
- Don't share memes (different culture than Twitter)
- Don't buy engagement pods
Profile Optimization#
Technical Professional Profile#
| Section | Best practice |
|---|---|
| Photo | Professional, friendly |
| Headline | [Role] at [Company] |
| About | Story format: background → now → what you share |
| Featured | Pin your best posts, articles |
| Experience | Focus on impact, not job duties |
| Skills | Technical skills get endorsements |
Headline examples:
Staff Engineer at Stripe | Building payments infrastructure
VP Engineering at Startup | Scaling teams from 5 to 50
DevRel at Supabase | Making databases accessibleLinkedIn Articles vs Posts#
When to Use Articles#
| Articles | Posts |
|---|---|
| 1,000+ words | Under 1,500 characters |
| SEO value (Google indexed) | No SEO |
| Evergreen content | Timely/current |
| Newsletter integration | One-time reach |
| Lower immediate reach | Higher immediate reach |
Article Best Practices#
- Front-load value (assume people don't finish)
- Use headers and formatting
- Include visuals
- End with CTA
- Share as post after publishing
Tools#
| Tool | Use case |
|---|---|
| Octolens (opens in a new tab) | Monitor LinkedIn for mentions of your product, competitors, and relevant conversations. Track when your space gets discussed. |
| Shield Analytics | Detailed LinkedIn analytics |
| Taplio | Post scheduling and analytics |
| AuthoredUp | Post formatting and preview |
| Canva | Carousel design |
| PDF carousels | Create in Canva, upload as PDF |
Content Calendar#
Weekly Template#
| Day | Content type |
|---|---|
| Monday | Technical insight post |
| Tuesday | Engage with others' content |
| Wednesday | Personal/career story |
| Thursday | Company news (shared personally) |
| Friday | Industry opinion or hot take |
Measuring Success#
Metrics That Matter#
| Metric | What it tells you |
|---|---|
| Impressions | Reach of content |
| Engagement rate | Content resonance |
| Profile views | Interest generation |
| Connection requests | Network growth |
| Followers | Audience building |
| Click-throughs | Action conversion |
| Comments | Discussion value |
Good Benchmarks#
| Metric | Good | Great |
|---|---|---|
| Engagement rate | 2-3% | 5%+ |
| Profile views/week | 50+ | 200+ |
| Post reach | 500+ | 2000+ |
Related Skills#
developer-audience-context— Know who you're reachingx-devs— Cross-post adapted contentgithub-presence— Link from LinkedIn to GitHubyoutube-devrel— Share video content on LinkedIn
Supporting file: README.md#
linkedin-technical#
B2B social skill — Reach developers and engineering leaders on LinkedIn.
What It Does#
Guides you through LinkedIn for technical audiences: content that works, reaching engineering managers, company page vs personal, formatting, and when LinkedIn beats Twitter.
When to Use#
- Creating technical content for LinkedIn
- Reaching B2B decision-makers (CTOs, VPs, EMs)
- Building thought leadership for dev tools
- When you say "LinkedIn," "B2B developer marketing," or "reaching engineering managers"
Quick Start#
/linkedin-technical
I want to announce our open source project on LinkedIn
in a way that reaches engineering managers at
enterprises. How should I structure the post?Key Sections#
- When LinkedIn Beats Twitter — Understanding the platform
- Content That Works — Formats and formulas
- Formatting Best Practices — Hooks, structure, visuals
- Company Page vs Personal — When to use each
- Reaching Engineering Managers — What EMs care about
- Profile Optimization — Technical professional profile
When to Use LinkedIn vs Twitter#
| Use LinkedIn | Use Twitter |
|---|---|
| Selling to enterprises | Individual developers |
| Reaching eng managers | Open source projects |
| B2B partnerships | Real-time engagement |
| Recruiting | Casual/authentic voice |
| Longer professional content | Technical hot takes |
Content That Works#
| Type | Performance |
|---|---|
| Personal stories | Very high |
| Career lessons | High |
| Contrarian opinions | High |
| Behind-the-scenes | High |
| Technical deep dives | Medium |
| Plain announcements | Low |
| Shared links | Very low |
Post Structure#
- Hook (first 210 chars critical)
- Context or problem
- Bullet points (3-5 insights)
- Personal take
- Question CTA
- 3-5 hashtags at end
Tools#
- Octolens (opens in a new tab) — Monitor LinkedIn conversations
- Shield Analytics — LinkedIn analytics
- Canva — Carousel design
Related Skills#
developer-audience-context— Know your audiencex-devs— Cross-post adapted contentyoutube-devrel— Share video on LinkedIn
FAQ
07 QUESTIONS
01What is the LinkedIn technical agent skill?
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. It is listed under social media in the 100xLab agent skills directory.
02How do I install LinkedIn technical in Cursor, Claude Code, or Codex?
Run npx skills add jonathimer/devmarketing-skills --skill linkedin-technical in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only LinkedIn technical, not every skill in the repository.
03What does the LinkedIn technical SKILL.md cover?
The SKILL.md includes sections on Before You Start, When LinkedIn Beats Twitter, LinkedIn's Unique Value, Use LinkedIn When, Use Twitter When and Understanding LinkedIn's Audience. Read the full text on this page or in plain markdown at /resources/agent-skills/jonathimer-devmarketing-skills--linkedin-technical--12bdzlp/raw.
04Which agents can use LinkedIn technical?
LinkedIn technical installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is LinkedIn technical under?
The jonathimer/devmarketing-skills repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is LinkedIn technical free to use?
Reading, copying and installing LinkedIn technical costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of LinkedIn technical?
LinkedIn technical comes from https://github.com/jonathimer/devmarketing-skills, which has 80 GitHub stars. The SKILL.md is at https://github.com/jonathimer/devmarketing-skills/blob/HEAD/skills/linkedin-technical/SKILL.md. The author is jonathimer.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
LinkedIn technical was written by its original authors and is published in jonathimer/devmarketing-skills (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.