linkedin-content-strategy
Skill1 starsChanged 11 days agoMITView on GitHub
Builds a LinkedIn content system for founders, consultants, creators, and influencers that grows the right followers and produces inbound conversations: content pillars, an honest cadence, formats, hooks, a 4-week calendar, and 3 ready-to-publish posts. Use when someone asks what to post on LinkedIn, how often, for a content plan or calendar, for post ideas, or for help writing hooks or posts. Not for job seekers or corporate employer branding.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- the-nam-shub/e5-real-skillstheir own version, first seen Apr 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- the-nam-shub/e5-real-skills★ 10same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
If the proof inventory is empty, the first month of content is the work in progress: what they are building, testing, and learning.
- Very specific: line 59
Write each pillar as one sentence the user can hold in their head, plus 10 topic seeds.
- Distinctive: line 69
Daily: only for full-time creators, and it degrades fast without a pipeline.
- Distinctive: line 136
Add the weekly operating rhythm:
- Distinctive: line 139
Post: start with weekday mornings in the audience's time zone (for B2B in India, 8–11am IST is a common starting point).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LinkedIn Content Strategy
Build a repeatable publishing system for someone selling something: a service, a product, a body of work, or their own expertise. The output is a plan they can run every week without you, not a pile of inspiration.
Success is not followers. It is qualified conversations. A 2,000-follower profile where 15 buyers read every post beats 50,000 followers who never buy. Say this out loud when the user asks for follower tactics.
Pick the depth
- Quick: the user wants a few posts or hooks, not a plan. Get Step 1's four
answers in one message (or ask for them), write what was asked using
references/post-formats.md, and offer the full plan in one line. - Full (default for "build my content strategy"): Steps 1 to 7.
Step 1: Establish the foundation
Get these four before writing anything. If they are vague, the content will be.
- Who: one primary audience, described by situation, not demographics. "Agency owners with 5–15 people who just lost their biggest client" beats "business owners".
- What they buy: the offer, the price band, the decision cycle.
- What you know that they do not: the unfair knowledge. This is the entire content supply.
- Proof inventory: client results, personal numbers, failures, experiments, screenshots. List them. Everything worth posting comes from here.
If the proof inventory is empty, the first month of content is the work in progress: what they are building, testing, and learning.
Step 2: Set content pillars
Pick 3–4 pillars. Each maps to a stage of the buyer journey.
| Pillar | Job | Share of posts |
| Authority / point of view | Make them think differently. Earns reach and follows. | 30% |
| Proof / results | Make them believe you can do it. Earns trust. | 30% |
| Teaching / how-to | Make them act. Earns saves and shares. | 25% |
| Personal / story | Make them like you. Earns replies. | 15% |
The offer post is not a pillar. It is a placement: one in every 8–10 posts, and the proof posts around it are what make it land.
Write each pillar as one sentence the user can hold in their head, plus 10 topic
seeds. references/pillar-worksheet.md has the extraction questions.
Step 3: Set cadence honestly
Match the plan to the time the user actually has.
- 3 posts a week: the working minimum for a business account. Compounds slowly and survives a busy month.
- 5 posts a week: growth pace. Needs a repurposing system or a writer.
- Daily: only for full-time creators, and it degrades fast without a pipeline.
Cap at one post a day. Two posts in a day compete for the same audience and both underperform.
Comments are part of the cadence. 10 substantive comments a day on posts the
buyers read often does more for reach and DMs than an extra post a week. Put it in
the calendar as a task. Comments count toward the daily action ceiling in
references/platform-reality.md, so keep the total sane.
The first hour is part of the cadence, not an extra. Early comments and the author's replies matter most, and LinkedIn ranks on dwell time (people actually reading). Block 20 minutes right after posting to reply to every comment. A post published when the author cannot engage is a post published at half strength.
Step 4: Formats
Match the format to the job. references/post-formats.md has a template for each.
| Format | Best for | Notes |
| Text post (900–1,300 characters) | Point of view, story, teaching | The default on a personal profile. Fastest to write. |
| Text + single image | Proof, screenshots, results | A real screenshot beats a stock photo every time. |
| Document carousel (PDF, 8–12 slides) | Frameworks, checklists | Built to be saved. Held reach better than video and polls in 2025 data. |
| Native video (30–90 seconds) | Personality, face-to-camera trust | Burn in captions; most people watch muted. Use it for trust, not as a reach hack. |
| Poll | Audience research | At most once every 2 weeks. LinkedIn shows fewer polls from people members don't know, so never use one for reach. |
| Newsletter | Owned distribution | Subscribers get a notification and an email. Only with a weekly commitment. |
Links: on a company page, always put the link in the first comment. On a personal profile the measured effect of a link is small, but the first comment is still the safe default when reach matters.
Never post text-only from a company page. On a personal profile, text-only is fine and often best.
Facts behind this section, with sources and grades: references/platform-reality.md.
Step 5: Hooks
The first two lines decide everything; the rest sits behind "see more".
Hook shapes that work without sounding like a growth hacker. The niches vary on purpose: copy the shape, never the content.
- Specific number: "We cut a client's checkout load time from 8.4s to 1.9s. Here's what actually did it."
- Contrarian claim: "Most SaaS onboarding emails are written for the product team, not the user."
- Confession: "I lost my biggest retainer last month. My fault, and here's the mistake."
- Direct address: "If your clinic gets calls but no bookings, check this before you touch the ads."
- Before and after: "Two years ago I was X. Today Y. The three decisions in between:"
Banned openings: "Excited to announce", "Thrilled to share", "In today's fast-paced world", "Let that sink in", and walls of one-line paragraphs used as fake drama.
Voice rules: references/voice-rules.md. Write how the user talks. If they sent
samples, mirror their sentence length and vocabulary.
Step 6: Build the calendar
Produce a 4-week calendar as a table: date, pillar, format, topic, hook draft, CTA. Front-load week 1 with proof posts, so a new visitor sees evidence immediately.
Add the weekly operating rhythm:
- Write: one 90-minute batching session drafts the week.
- Post: start with weekday mornings in the audience's time zone (for B2B in India, 8–11am IST is a common starting point). Test two windows for 4 weeks each and keep the winner. No posting time is gospel.
- Engage: 20 minutes right after posting, replying to every comment. Then 10 comments a day on other people's posts.
- Review: Friday, 15 minutes: note what earned saves and DMs, and hand off to
linkedin-metrics-review.
Step 7: Deliver
- Audience and offer, one sentence each
- 3–4 pillars with 10 topic seeds each
- Cadence and the weekly rhythm
- 4-week calendar with every hook drafted
- 3 fully written posts they can publish this week, with
[placeholders]wherever a number or name is missing - What to track, with today's baseline
Anti-patterns
- Engagement bait ("Agree?", tag-a-friend, "comment YES"). LinkedIn reduces the reach of posts that ask for engagement to boost reach, and it teaches the algorithm the wrong audience.
- Broad "value" content aimed at everyone. It grows followers who never convert, and then the user concludes LinkedIn does not work.
- Posting only offers. Also: posting only inspiration and never the offer.
- Copying another creator's voice. Steal structure, never phrasing.
- Chasing viral posts. One viral post to the wrong audience is worse than twenty read by the right fifty people.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

