linkedin-content-planner
Skill3 starsChanged 34 days agoMITView on GitHub
Generate a 7-day LinkedIn content plan from a theme, audience and pillars: pillar, format, hook, CTA, time and comment targets per day.
6 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- 07001ec010shnk-svg/linkedin-agent-skillstheir own version, first seen Oct 25, 2026
- CodesbyFebin/linkedin-manageredited, first seen Oct 20, 2026
- AIProUK/linkedin-claude-skillsedited, first seen Oct 20, 2026
- sylvan-io/linkedin-skillsedited, first seen Oct 11, 2026
- subu53/linkedin_exponentialtheir own version, first seen Oct 8, 2026
- sergebulaev/linkedin-skillsedited, first seen May 19, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- sergebulaev/linkedin-skills★ 5.4k96% same
- AIProUK/linkedin-claude-skills★ 196% same
- sylvan-io/linkedin-skills★ 195% same
- CodesbyFebin/linkedin-manager★ 096% same
Wrote their own version · 2
- 07001ec010shnk-svg/linkedin-agent-skills★ 0same name
- subu53/linkedin_exponential★ 0same 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 repository50 other files it gives its agents.
- automationsSkill
- commentsSkill
- hooksSkill
- ig-auditSkill
- ig-captionSkill
- ig-carouselSkill
- ig-dmSkill
- ig-humanSkill
- ig-profileSkill
- ig-reelSkill
- ig-storySkill
- ig-viralSkill
- inboxSkill
- linkedin-comment-drafterSkill
- linkedin-employee-advocacySkill
- linkedin-engager-analyticsSkill
- linkedin-hook-extractorSkill
- linkedin-humanizerSkill
- linkedin-interviewerSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- linkedin-reply-handlerSkill
- linkedin-repurposerSkill
- linkedin-thread-monitorSkill
- naver-ai-citeSkill
- naver-draftsSkill
- naver-engageSkill
- naver-keywordsSkill
- naver-postSkill
- performance-reviewSkill
- publishSkill
- repurposeSkill
- schedule-weekSkill
- setupSkill
- threadsSkill
- troubleshootSkill
- voice-profileSkill
- yt-auditSkill
- yt-benchmarkSkill
- yt-chaptersSkill
- yt-commentSkill
- yt-editSkill
- yt-packageSkill
- yt-planSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-shortsSkill
- yt-uploadSkill
- yt-viralSkill
The file
We split this skill into the rules it gives an agent
5 rules. 3 are common, 0 are distinctive, and 2 are very specific to this project.
3
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 16
Before a launch week (user needs product-pillar alignment)
- Common: line 66
One format per pillar per week: Don't stack 3 text posts for Authority, vary.
- Very specific: line 93
Every formula earns a primary reaction: comments, reposts, likes, or saves (see ../../references/hook-formulas.md "Engagement-goal split").
- Very specific: line 106
Voice profile: If ../../references/voice-profile.md has filled: yes, load it and respect the CTA and link style it records when picking CTA …
- Common: line 117
Run inbound-readiness check.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Adapted from sergebulaev/linkedin-skills (MIT). Not affiliated with the original author.
LinkedIn Content Planner
Produce a 7-day LinkedIn plan built around the 3-pillar discipline (Authority 40-50%, Personal Narrative 30-40%, Community 20-30%). Optionally adds a Product/Offer pillar at 10-15%.
When to use
- User asks "plan my week" or "what should I post this week"
- User wants to escape ad-hoc shipping and establish rhythm
- Before a launch week (user needs product-pillar alignment)
Input
- Theme (optional): e.g., "AI agents shipping in production", "first 6 months of Co.Actor"
- Audience description: e.g., "B2B founders, AI ops leaders, marketing VPs"
- Pillar mix (optional): defaults to 40% Authority / 30% Narrative / 20% Community / 10% Product
- Posting days (optional): defaults to Tue/Wed/Thu/Fri (4 posts)
- Voice samples (optional): only if
../../references/voice-profile.mdis not filled yet
Output
A markdown plan with:
7-day calendar
| Day | Time | Pillar | Format | Hook formula | 1-line angle | CTA type | Goal |
| Mon | - | (commenting day) | - | - | - | - | - |
| Tue | 8:00 AM local | Authority | Text | F7 Odd-Precision Money | "What 3 months of agent ops costs" | Question close | Saves |
| Wed | 9:30 AM local | Narrative | Text | F4 Time-Anchor Confession | "Why I stopped publishing for 4 weeks" | Mirror question | Comments |
| Thu | 8:00 AM local | Community | Text | F14 Named Gratitude | "The 3 people who shaped our launch" | Tag + thanks | Reposts |
| Fri | 9:00 AM local | Narrative | Text | F11 Emotional Cold-Open | "The night our first deploy failed" | Soft close | Likes |
| Sat/Sun | - | (off) | - | - | - | - | - |
The Goal column spans saves / comments / reposts / likes across the four posts, satisfying the Goal mix check below.
Daily comment targets
For each posting day:
- 3-5 creators to engage (names or archetypes: "peer founders at 5-20k", "VCs with AI thesis", "BigCo CTOs")
- Comment pattern to apply (first-commenter, data-first, answer-their-question)
- Target count: 10-20 substantive comments per day
Weekly inbound-readiness check
- At least 1 vulnerability post (Narrative)
- At least 1 receipt/data post (Authority)
- At least 1 soft offer or CTA-driving post
- Comment strategy includes 70% peers, 20% aspirational, 10% prospects
- No pillar >60% of the week's posts
- No duplicate formula used twice in the same week
- Goal mix spread: not every post chases the same reaction (see Goal mix below)
Rules
- 3 pillars minimum, 5 maximum. More than 5 dilutes signal.
- 3-5 posts per week. 6+/week triggers cannibalization signal in 360Brew.
- 10-20 comments/day on other creators. Comments drive more inbound than posts.
- Tue/Wed/Thu top for B2B. Avoid Fri after 2 PM, Sat/Sun (B2B 30-50% reach cut).
- One format per pillar per week. Don't stack 3 text posts for Authority, vary.
- Product/Offer pillar max 1 post/week. Overuse kills trust.
Formula → pillar mapping
| Pillar | Preferred formulas |
| Authority | F7 Odd-Precision Money, F10 Contrarian Historical, F8 Paid-vs-Free, F5 Self-Proving Meta, F15 Explain-to-Kids |
| Narrative | F4 Time-Anchor Confession, F3 Year-over-Year Pivot, F9 Curiosity-Gap, F11 Emotional Cold-Open, F16 Status-Strip |
| Community | F6 Comment-Gate (use sparingly), F12 Permission Slip, F14 Named Gratitude, poll posts, spotlight mentions |
| Product/Offer | F2 R.I.P. Obituary (when pivoting category), F1 Anaphora (when framing product as fix), F13 Bait-and-Switch (upgrade announcements) |
Founders edition (alternative pillar set)
When the whole plan is for a founder building trust with investors, hires, and design partners, swap the default pillar mix for the founder set from ../../references/founder-topics.md. It maps each pillar to founder angles (A1-A10) instead of generic topics, and leans on the structural formulas F17-F20.
| Pillar | Share | Founder angles | Preferred formulas |
| Conviction (POV, category, product philosophy) | 30-40% | A1 Reprice, A7 Designed Serendipity, A8 Evasive-Sentence | F10, F18, F5 |
| Building in public (the real, unglamorous work) | 30-40% | A5 Unglamorous Bet, A6 Limit of Delegation, A9 Delegation Line | F7, F4, F17 |
| The math (how a founder actually decides) | 15-20% | A4 Scarce-Shots, A10 Learning Gate | F10, F18, F20 |
| Proof (relationships and wins, told narrowly) | 10-15% | A2 Content-to-Pipeline, A3 Audience of One | F9, F11, F5 |
Same guardrails apply: 3-5 posts/week, no pillar above 60%, no formula repeated inside 7 days, spread the goal across the week. Ask the user "founder plan or general plan?" when the audience is a founder building a company, and default to this set if they say founder.
Goal mix (balance the week, not just the pillars)
Every formula earns a primary reaction: comments, reposts, likes, or saves (see ../../references/hook-formulas.md "Engagement-goal split"). A week that is all comment-bait or all repost-bait reads as engineered and flattens reach. Spread the goals across the week:
| Goal | Formulas | Weekly target |
| Comments | F4, F10, F12, F9 | at least 1 |
| Reposts | F14, F2, F8 | at least 1 |
| Likes | F11, F13, F16 | at least 1 |
| Saves | F15, F7, F8 | at least 1 |
Steps
Story bank first. If ../../references/story-bank.md has filled: yes, load it before planning anything. The week's angles come from material that already exists: a dated turning point, a number with a named referent, a position the user holds and pays for. Planning a week against an empty bank is how a calendar fills with themes no draft can execute, so if the bank is not filled, say once that linkedin-interviewer fills it in 20 to 40 minutes, then plan from the theme the user gave.
Voice profile. If ../../references/voice-profile.md has filled: yes, load it and respect the CTA and link style it records when picking CTA types. If it is not filled, mention once that linkedin-humanizer --mode profile can learn it from a few posts, then use the generic voice rules.
- Gather inputs. Ask user for theme, audience, pillar preferences if not provided.
- Validate pillar mix sums to 100%; warn if any pillar >60%.
- For each posting day, pick:
- Pillar (rotate to match mix)
- Formula from that pillar's bank (don't repeat within 7 days)
- Format (alternating text / carousel / poll per pillar rules)
- Specific angle, taken from the Story Bank where it has material that fits (name the bank section in the plan so the draft knows what to open), otherwise from the user, otherwise generated. Never put a figure in an angle that is not in the bank or supplied by the user.
- Posting time (audience-timezone aware)
- For each posting day, add 3-5 comment targets with suggested pattern.
- Run inbound-readiness check; flag anything missing.
- Return as markdown + optional JSON for Notion/Airtable import.
Example
See references/example-plan-week.md for a filled-in 7-day plan.
Files
SKILL.md: this filereferences/example-plan-week.md: worked examplereferences/pillars-framework.md: the 3-pillar discipline explained../../references/founder-topics.md: founders-edition angle library (A1-A10) and founder pillar set../../references/story-bank.md: the material the week's angles are drawn from../../references/voice-profile.md: voice fingerprint and CTA style
Related skills
linkedin-interviewer: fills the Story Bank the plan draws its angles fromlinkedin-post-writer: generate each day's draft from the planlinkedin-comment-drafter: execute the daily comment targetslinkedin-thread-monitor: track inbound from the comment strategylinkedin-engager-analytics: segment audience on each post
Tools
None. This skill plans on text and calls no Uplika tool; linkedin-post-writer publishes each post.
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.

