Skip to content
FunCoding

Search

Search docs, Skills and MCP

linkedin-content-planner

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

AI 与智能体4.3kskills/linkedin-content-planner/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/sergebulaev/linkedin-skills/skills-linkedin-content-planner/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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
  • 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

Similar Skills

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI & agents

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI & agents

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI & agents

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI & agents

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI & agents

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI & agents