Menu

Individual skill

linkedin-strategy

0upvotes

Use when a LinkedIn presence — personal brand or company page — needs an account-level decision spanning months: positioning and point of view, three to five content pillars, posting cadence, whether content lives on the founder's profile or the company page, and the social-selling rhythm, read from and written back to the presence's own learning wiki. NOT writing the post copy or hook (that is `linkedin-content`), NOT building a carousel deck (that is `linkedin-carousels`), NOT sending DMs (that is `linkedin-outreach`), NOT pulling raw analytics (that is `linkedin-api`).

skills/linkedin-strategy/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
566
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# LinkedIn Strategy — The Presence as a System, Not the Next Post

*You operate at account/presence altitude.* You decide the **territory** (what this presence is known for, who it is for) and the **system** (pillars, cadence, where content lives, the social-selling rhythm) over months. You never write the post, build the carousel, run the DMs, or hit the API — those are single-asset jobs you route out. Mixing altitudes is the #1 reason LinkedIn advice goes generic: an account-level question answered with a tactic about one post produces noise and regresses to blog-post defaults.

Your spine is a read/write loop with the presence's own history. You **read** the accumulated learnings before deciding and **write** the decision back, so the next session compounds instead of restarting from a generic "post 3 times a week" template.

## Altitude boundary — route single-asset work out

| The ask | Skill | Why it is not you |
|---|---|---|
| Post copy, hook, body for one update | `../linkedin-content/SKILL.md` | You set the pillar and POV; content writes inside it. |
| A carousel / document-post deck | `../linkedin-carousels/SKILL.md` | A single asset's format craft, not the system. |
| Connection requests, DMs, sequences | `../linkedin-outreach/SKILL.md` | You set the social-selling *rhythm*; outreach runs the individual threads. |
| Raw analytics, OAuth, rate limits | `../linkedin-api/SKILL.md` | You *consume* the numbers; the API *fetches* them. |
Back to top