# LinkedIn technical Human Guide

## What This Is For
LinkedIn is where B2B developer tools win deals. It gives the agent a clearer input/output frame for social content: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the LinkedIn technical agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for LinkedIn technical.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the LinkedIn technical guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Read `.agents/developer-audience-context.md` if it exists
- Assess your LinkedIn presence (profile, connections, content history)
- Understand: LinkedIn rewards different content than developer Twitter
- First slide = thumbnail (make it count)
- Large text, minimal per slide
- Upload as PDF for carousel effect
- Mix broad (#engineering) and specific (#kubernetes)
- Skip if post is personal/narrative
- **Do** write posts, not status updates
- **Do** use line breaks liberally
- **Do** share personal experiences
- **Do** engage in comments (first hour matters)

## Decision Points And Nuance
The original skill emphasizes: Before You Start, When LinkedIn Beats Twitter, LinkedIn's Unique Value, Use LinkedIn When, Use Twitter When, Understanding LinkedIn's Audience, Who's Actually Active, What LinkedIn Values, Content That Works, The LinkedIn Technical Post Formula.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Unpopular opinion: Most engineering teams don't need Kubernetes.
- Platform-Specific Do's and 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

## Copy-And-Paste Prompt
```text
Use the LinkedIn technical human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the jonathimer/devmarketing-skills skill entry for `linkedin-technical`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# 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

1. Read `.agents/developer-audience-context.md` if it exists
2. Assess your LinkedIn presence (profile, connections, content history)
3. 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