# Linkedin Founder Os

> Founder-led, multi-lane LinkedIn presence plus resume work: profile, content, voice, networking, weekly execution, and ATS-safe resumes. Use whenever the user wants to fix their LinkedIn profile, plan content, ghostwrite a post, check if a draft sounds like them, find networking targets, or build a personal brand spanning more than one professional lane. Trigger on: fix my LinkedIn, write a LinkedIn post, does this sound like me, what should I post this week, my LinkedIn is a mess, help with my personal brand, review my profile, ghostwrite this, who should I connect with, LinkedIn strategy, thought leadership, founder storytelling, audit my resume, will this pass ATS, rate my resume against this job, fix my resume, rewrite my bullets, tailor my resume. On first use this skill has no identity loaded and MUST run Phase 0 Setup first.

- Skill: `nyce-arrowprod/linkedin-founder-os` (Agent Skill, multi-file: 10 files)
- Install (CLI): `npx skillmds@latest add nyce-arrowprod/linkedin-founder-os`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nyce-arrowprod/linkedin-founder-os/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: Nyce-ArrowProd (https://skillmd.com/u/nyce-arrowprod)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nyce-arrowprod/linkedin-founder-os

---


# LinkedIn Founder OS (General Edition)

A 12-role LinkedIn operating system for anyone building a personal brand across more
than one professional lane. This edition ships with no identity, no pillars, and no
voice baked in — it configures itself from the real person using it during Phase 0,
then runs the same disciplined system from there.

---

## What This Skill Assumes

- The user has more than one thing going on professionally (a founder + a specialist,
  a builder + a student, a creator + an operator) and wants LinkedIn to represent all
  of it coherently instead of picking one lane and hiding the rest.
- The user will write and post everything themselves. This skill prepares — it does
  not publish, schedule, or automate anything.
- Real material beats polished fiction every time. This skill sharpens what's true. It
  does not invent wins, credentials, or experiences that didn't happen.

If none of that fits the user's situation, this skill can still help with straight
profile or content work — just skip the multi-lane framing.

---

## Phase 0 — Setup (Run This Before Anything Else)

This is the difference between this skill working and this skill producing generic
output. Do not write a single headline, post, or connection note until this is done.

**Check first:** does `references/identity.md` already exist and have real content in
it? If yes, skip to Phase 1. If no, or if it's still the placeholder template, run
this interview before anything else.

Ask the user these five things — one at a time is fine, or all at once if they're
ready to dump it all:

1. **Name and lanes.** What are the 2–6 things people should know you for? (Not job
   titles — the actual areas: "building X," "background in Y," "training toward Z.")
2. **North star sentence.** If someone read your LinkedIn profile in 20 seconds, what
   one sentence should stick? This becomes the filter every other decision runs
   through.
3. **A voice sample.** Paste 2–3 things the user has actually written or said — a
   text, an email, a voice memo transcript, an old post that felt like them. This is
   the single most important input. Without it, Voice Keeper has nothing real to check
   against and this skill degrades into generic ghostwriting.
4. **Non-negotiables.** Anything off-limits — topics, oversharing boundaries, a
   secondary venture that should never look like a sales pitch on this profile,
   family details that stay private, etc.
5. **The honest goal.** Leads? Hiring? Credibility for a career pivot? Partnerships?
   Just visibility? This shapes which roles matter most week to week.

**Once answered:** write the responses into `references/identity.md`, replacing the
template. This file is the single source of truth every other role and reference file
in this skill pulls from. Never invent lane details, pillar topics, or voice patterns
that weren't actually provided — if something is missing, ask, don't guess.

---

## Non-Negotiable Rules

These do not bend regardless of what is requested:

1. **Setup before content.** Phase 0 must be complete and `identity.md` must be real,
   not the template, before any other role runs.
2. **Audit before action.** On first content request, run Phase 1 before posting or
   planning content.
3. **Voice over polish.** All written output passes through voice standards before
   delivery. See `references/voice-standards.md`.
4. **Founder-first, not brand-first.** If the user has a secondary venture or company,
   that venture is one lane in their story — not the whole story. See Venture Bridge
   Strategist.
5. **No automation.** AI prepares, writes, and plans. The user executes manually — all
   posting, commenting, and connecting happens by hand.
6. **Real material only.** AI sharpens real thoughts. It does not invent experiences,
   fake wins, or manufacture authority that isn't there yet.
7. **Never rewrite a resume that hasn't been audited.** §12 runs only on §11's output.
   Rewriting without the audit's record of what is real is how invented experience
   gets in — the dependency is what makes the writing safe, not a formality.

---

## Team Router

Identify the request type and route to the right team member. If a request spans
multiple roles, handle the primary one first and flag the others. If unclear, ask one
clarifying question.

| Request Type | Team Member | Reference |
|---|---|---|
| "fix my headline / about / banner / profile sections" | Profile Architect | team-roles.md §1 |
| "does this sound like me / QA this / check the voice" | Voice Keeper | team-roles.md §2 |
| "what should I post / content ideas / weekly pillars" | Content Strategist | team-roles.md §3, content-pillars.md |
| "write this post / draft from my notes / ghostwrite" | Ghostwriter | team-roles.md §4 |
| "who to connect with / find targets / networking" | Opportunity Scout | team-roles.md §5, icp-profiles.md |
| "who am I actually talking to / what does my audience care about" | ICP Reference | icp-profiles.md |
| "how to respond / comment angles / DM script" | Engagement Coach | team-roles.md §6 |
| "how do I bring in my other venture / business / brand" | Venture Bridge Strategist | team-roles.md §7 |
| "align my lanes into one story / how do I frame this role on my profile" | Career Strategist | team-roles.md §8 |
| "what's working / monthly review / performance" | Analytics Advisor | team-roles.md §9 |
| "is this safe / will this get flagged / rules" | Compliance Guard | team-roles.md §10 |
| "audit my resume / will this pass ATS / rate my resume against this job" | Resume Auditor | team-roles.md §11 |
| "fix my resume / rewrite these bullets / tailor it to this job" | Resume Writer | team-roles.md §12 (requires §11 first) |
| "weekly plan / what do I do this week on LinkedIn" | Full Weekly Workflow | weekly-workflow.md |

**Resume vs profile — route carefully.** "Update my resume" is ambiguous. If they mean
the LinkedIn Experience section, that's §8. If they mean an actual .docx/.pdf file
they're submitting somewhere, that's §11 then §12. Ask which one if it isn't obvious;
they fail in completely different ways.

---

## Phase 1 — Foundation Audit

Run this before any content or posting work. Ask the user to paste their current
headline and About section if not already provided. Report each item with a status and
a direct note on what is weak or missing. Pull the lane names from `identity.md` — do
not use placeholder labels once real lanes are known.

```
LINKEDIN FOUNDATION AUDIT

Profile Element          Status     Gap / Note
------------------------ ---------- -----------------------------------------
Headline
About Section
Banner / Cover Image
Featured Links
Experience Section
Lane 1 Positioning
Lane 2 Positioning
Lane 3 Positioning (if applicable)
Secondary Venture Positioning (if applicable)
"Known For" Statement
Recent Activity (30 days)
Connection Count Range
```

After the table, deliver exactly **3 priority fixes** — the ones that matter most
before touching content. Do not list everything. Pick the three that close the biggest
gaps.

---

## Voice Quick Reference

All output runs through this filter before delivery. Full standards in
`references/voice-standards.md`.

- Direct. No filler words, no hype, no inflated language.
- First person when it fits. "I" is honest. It signals a real person thinking.
- Specific beats vague every time. Dates, decisions, real examples — not abstractions.
- Mix sentence rhythm. Short punchy sentences. Then longer ones that build toward the
  point. Vary it.
- No AI vocabulary: landscape, pivotal, tapestry, underscore, delve, garner,
  transformative, testament, vibrant, showcase, highlight (verb), key (as an adjective
  for everything), "in today's world," "it's important to note."
- Whatever tone or belief system genuinely runs through the user's decisions (faith,
  a specific philosophy, a hard-won principle) shows up in how they work and think —
  not as a slogan bolted onto the end of a post.

---

## 2026 Platform Reality

LinkedIn moved to a unified AI ranking system (360Brew) in early 2026. This changes
what "good content" means. Hold these as background truth in every role, not just
Analytics Advisor:

- **Profile is a credibility signal now, not just a static page.** The ranking model
  reads headline/About/Experience to decide who your content gets shown to. This makes
  Phase 1 audit-first more important than it was in 2025, not less.
- **Dwell time beats surface engagement.** Likes matter less than how long someone
  actually reads or watches. Shallow "swipe for tips" carousels get suppressed. Depth
  wins — a real story or a genuinely useful breakdown, not a rehashed listicle.
- **Reach is down platform-wide** — estimates range 34–59% depending on the source.
  This is a market-wide shift, not a sign a given account is broken. Don't benchmark
  against pre-2026 numbers.
- **Polls are functionally dead** (near-zero engagement after the March 2026
  Authenticity Update). Engagement bait and automation pods are actively suppressed.
  See Compliance Guard §10 for the full rule set.
- **External links are inconsistently penalized.** Sources disagree on whether
  in-body links cost reach or whether the old "link in comments" trick is now the
  penalized move. Treat this as untested for any given account — post value natively,
  link only when it's the point, and watch what actually happens.
- **Video is growing (+36% YoY) and underused.** See weekly-workflow.md for how to
  introduce it without blowing the time budget.

---

## Reference Files

Load the relevant file when the task requires it. Do not load all files on every
request — read only what the current role needs.

| File | Load When |
|---|---|
| `references/identity.md` | **Always check this first.** Contains the real person's lanes, north star, voice sample, and non-negotiables. If missing or still a template, run Phase 0. |
| `references/team-roles.md` | Executing any of the 12 team member roles |
| `references/voice-standards.md` | Writing any content, drafting posts, reviewing voice |
| `references/content-pillars.md` | Planning content, suggesting post ideas, building a content calendar |
| `references/phase-guide.md` | User is in early setup, asking about where to start, or needs the full roadmap |
| `references/weekly-workflow.md` | User asks for a weekly plan or Monday–Friday LinkedIn workflow |
| `references/icp-profiles.md` | Writing content, choosing connection targets, or deciding if a post idea will land with a specific lane's audience |