agentleFS
uplikauplika/uplika-plugin/skills/linkedin-content-planner/SKILL.md

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

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
  1. Common:

    Before a launch week (user needs product-pillar alignment)

    line 16
  2. Common:

    One format per pillar per week: Don't stack 3 text posts for Authority, vary.

    line 66
  3. Very specific:

    Every formula earns a primary reaction: comments, reposts, likes, or saves (see ../../references/hook-formulas.md "Engagement-goal split").

    line 93
  4. Very specific:

    Voice profile: If ../../references/voice-profile.md has filled: yes, load it and respect the CTA and link style it records when picking CTA …

    line 106
  5. Common:

    Run inbound-readiness check.

    line 117

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md is not filled yet

Output

A markdown plan with:

7-day calendar

DayTimePillarFormatHook formula1-line angleCTA typeGoal
Mon-(commenting day)-----
Tue8:00 AM localAuthorityTextF7 Odd-Precision Money"What 3 months of agent ops costs"Question closeSaves
Wed9:30 AM localNarrativeTextF4 Time-Anchor Confession"Why I stopped publishing for 4 weeks"Mirror questionComments
Thu8:00 AM localCommunityTextF14 Named Gratitude"The 3 people who shaped our launch"Tag + thanksReposts
Fri9:00 AM localNarrativeTextF11 Emotional Cold-Open"The night our first deploy failed"Soft closeLikes
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

PillarPreferred formulas
AuthorityF7 Odd-Precision Money, F10 Contrarian Historical, F8 Paid-vs-Free, F5 Self-Proving Meta, F15 Explain-to-Kids
NarrativeF4 Time-Anchor Confession, F3 Year-over-Year Pivot, F9 Curiosity-Gap, F11 Emotional Cold-Open, F16 Status-Strip
CommunityF6 Comment-Gate (use sparingly), F12 Permission Slip, F14 Named Gratitude, poll posts, spotlight mentions
Product/OfferF2 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.

PillarShareFounder anglesPreferred formulas
Conviction (POV, category, product philosophy)30-40%A1 Reprice, A7 Designed Serendipity, A8 Evasive-SentenceF10, F18, F5
Building in public (the real, unglamorous work)30-40%A5 Unglamorous Bet, A6 Limit of Delegation, A9 Delegation LineF7, F4, F17
The math (how a founder actually decides)15-20%A4 Scarce-Shots, A10 Learning GateF10, F18, F20
Proof (relationships and wins, told narrowly)10-15%A2 Content-to-Pipeline, A3 Audience of OneF9, 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:

GoalFormulasWeekly target
CommentsF4, F10, F12, F9at least 1
RepostsF14, F2, F8at least 1
LikesF11, F13, F16at least 1
SavesF15, F7, F8at 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
  • references/example-plan-week.md: worked example
  • references/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 from
  • linkedin-post-writer: generate each day's draft from the plan
  • linkedin-comment-drafter: execute the daily comment targets
  • linkedin-thread-monitor: track inbound from the comment strategy
  • linkedin-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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.