linkedin-content-planner
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Skill by CodesbyFebin
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/codesbyfebin-linkedin-content-planner
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
linkedin-content-planner- Description
- Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).
- License
- MIT
- Instructions
- 134 lines in SKILL.md · view on GitHub
Files (3)
- SKILL.md
- example-plan-week.md · references/
- pillars-framework.md · references/
SKILL.md (first lines)
# 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.md` is 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. 1. Gather inputs. Ask user for theme, audience, pillar preferences if not provided. 2. Validate pillar mix sums to 100%; warn if any pillar >60%. 3. 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) 4. For each posting day, add 3-5 comment targets with suggested pattern. 5. Run inbound-readiness check; flag anything missing. 6. 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 file
From CodesbyFebin/linkedin-manager, MIT.
More from CodesbyFebin/linkedin-manager
- 0.570score
linkedin-cta-lab
CodesbyFebin
Write three closing lines for an existing draft and score them.
SkillAFreshness: AClaude Code +9 - 0.570score
linkedin-carousel-writer
CodesbyFebin
Turn one claim into a LinkedIn document or carousel script.
SkillAFreshness: AClaude Code +9 - 0.570score
linkedin-analytics-review
CodesbyFebin
Read pasted LinkedIn analytics and say what to repeat.
SkillAFreshness: AClaude Code +9 - 0.570score
linkedin-connection-note
CodesbyFebin
Draft one connection note or follow-up for a named person.
SkillAFreshness: AClaude Code +9 - 0.567score
linkedin-case-receipt
CodesbyFebin
Draft a proof post from a build log: what shipped, what failed, what the log showed.
SkillAFreshness: AClaude Code +9 - 0.566score
linkedin-approval-gate
CodesbyFebin
Run the pre-publish gate on a draft before any post, comment, reply, invite, poll, or caption goes out.
SkillAFreshness: AClaude Code +9 - 0.565score
linkedin-correction
CodesbyFebin
Draft a public correction when an earlier post was wrong.
SkillAFreshness: AClaude Code +9 - 0.565score
agent-youtube-desk
CodesbyFebin
Draft a title, description, and pinned comment for a video the user already cut.
SkillAFreshness: AClaude Code +9 - 0.565score
linkedin-event-note
CodesbyFebin
Draft a post for a talk, meetup, or ship review the user is actually doing.
SkillAFreshness: AClaude Code +9 - 0.565score
linkedin-feature-picker
CodesbyFebin
Choose three items for the LinkedIn Featured section from work the user already shipped.
SkillAFreshness: AClaude Code +9 - 0.563score
linkedin-marketing
CodesbyFebin
Plan, draft, audit, and publish LinkedIn posts, comments, carousels, newsletters, and polls.
SkillAFreshness: AClaude Code +9 - 0.561score
linkedin-experience-bullet
CodesbyFebin
Rewrite one experience entry into four proof bullets.
SkillAFreshness: AClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 2
- Last commit (this folder)
- Oct 4, 2026 (25 days ago)
- Last release
- Oct 4, 2026 (24 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/CodesbyFebin/linkedin-manager
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from CodesbyFebin
- 0.570score
linkedin-cta-lab
CodesbyFebin
Write three closing lines for an existing draft and score them.
SkillAFreshness: AClaude Code +9 - 0.570score
linkedin-connection-note
CodesbyFebin
Draft one connection note or follow-up for a named person.
SkillAFreshness: AClaude Code +9 - 0.570score
linkedin-analytics-review
CodesbyFebin
Read pasted LinkedIn analytics and say what to repeat.
SkillAFreshness: AClaude Code +9 - 0.570score
linkedin-carousel-writer
CodesbyFebin
Turn one claim into a LinkedIn document or carousel script.
SkillAFreshness: AClaude Code +9 - 0.567score
linkedin-case-receipt
CodesbyFebin
Draft a proof post from a build log: what shipped, what failed, what the log showed.
SkillAFreshness: AClaude Code +9 - 0.566score
linkedin-approval-gate
CodesbyFebin
Run the pre-publish gate on a draft before any post, comment, reply, invite, poll, or caption goes out.
SkillAFreshness: AClaude Code +9
Cite this page
linkedin-content-planner skill. Agent Mart. https://agentmart.dev/skills/codesbyfebin-linkedin-content-planner (last updated 2026-10-24)