SkillAtlasSkill 详情

linkedin-content-planner

Claude skills for LinkedIn.

审核状态:已审核Quality 80Security 100

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件:README.md

抓取于 2026年8月25日

11 Claude Code and Codex skills for LinkedIn marketing — open source, MIT licensed

LinkedIn Marketing Skills for Claude Code and Codex

Latest release Claude Code Compatible Codex Compatible Claude Skills MIT License GitHub stars PRs Welcome

Claude skills for LinkedIn. 11 Claude Code and Codex skills that write LinkedIn posts, comments, and replies in your voice. They draft content, strip AI tells, and wait for your approval before anything gets published. No coding required.

On another platform too? The same team ships matching marketing skill bundles for X (Twitter) · Instagram · YouTube · TikTok · Threads · Facebook. Same voice engine, same approve-before-publish flow.

Install

Pick whichever way you use Claude Code or Codex:

Codex CLI

codex plugin marketplace add sergebulaev/linkedin-skills
codex plugin add linkedin-skills@linkedin-skills

To test a local clone before publishing changes:

git clone https://github.com/sergebulaev/linkedin-skills.git
cd linkedin-skills
codex plugin marketplace add .
codex plugin add linkedin-skills@linkedin-skills

claude.ai (web)

  1. Open https://claude.ai/code
  2. Go to Skills in the sidebar
  3. Click Add from GitHub
  4. Paste: sergebulaev/linkedin-skills
  5. Done. The skills activate automatically when you ask about LinkedIn.

Claude Desktop (Mac / Windows)

  1. Open Claude Desktop
  2. Click Customize
  3. Click the + next to Personal plugins → Create plugin → Add marketplace
  4. Choose Add from a repository and paste: sergebulaev/linkedin-skills
  5. Install the plugin
  6. Done. Start a new conversation and ask Claude to write a LinkedIn post.

OpenClaw

  1. Open your OpenClaw working directory
  2. Clone the skills into it:
    git clone https://github.com/sergebulaev/linkedin-skills.git
    
  3. In OpenClaw settings, add this to your system prompt:
    You have LinkedIn marketing skills in ./linkedin-skills/.
    For any LinkedIn task, read the relevant skills/*/SKILL.md first.
    Use lib/url_parser.py for URL parsing,
        lib/apify_client.py for reading posts / comments / engagers,
        lib/publora_client.py for publishing actions.
    
  4. Done. Ask OpenClaw to write a LinkedIn post or comment.

Claude Code (CLI / VS Code / JetBrains)

/plugin marketplace add sergebulaev/linkedin-skills
/plugin install linkedin-skills@linkedin-skills

Or clone the repo and open it as your working directory:

git clone https://github.com/sergebulaev/linkedin-skills.git
cd linkedin-skills

Hermes Agent

Hermes Agent (Nous Research) follows the agentskills.io open standard and loads skills/*/SKILL.md directly. Clone the bundle into your Hermes skills folder:

git clone https://github.com/sergebulaev/linkedin-skills.git ~/.hermes/skills/linkedin-skills

Coming from OpenClaw? hermes claw migrate imports these skills automatically. Then call /<skill-name> from any of your Hermes chat surfaces.

Any agent (skills CLI)

One command that works across Claude Code, Codex, Cursor, and any other agent that reads SKILL.md files:

npx skills add sergebulaev/linkedin-skills

Found this useful? Star the repo. Curated Claude Code and Codex directories rank and gate by star count, so a star is what makes these skills findable for the next person. It is the only thing we ask. No signup, no email.

What you can do

Once installed, just ask Claude Code or Codex for help with LinkedIn. The right skill activates automatically.

Write a post:

"Write me a LinkedIn post about why AI agencies are replacing traditional ones. Make it viral."

Comment on someone's post:

"Comment on this post: https://linkedin.com/posts/... — I want to add a thoughtful take."

Check a draft before publishing:

"Audit this post draft for AI tells and algorithm issues: [paste your text]"

Reverse-engineer a viral post:

"What hook formula does this post use? https://linkedin.com/posts/..."

Plan your week:

"Create a 7-day LinkedIn content plan. I'm a B2B SaaS founder targeting VPs of Marketing."

Rewrite your profile:

"Optimize my LinkedIn profile for inbound leads: https://linkedin.com/in/yourname"

Remove AI tells from any text:

"Humanize this text: [paste AI-generated draft]"

Every skill shows you a draft first and waits for your OK before doing anything. Nothing gets posted without your approval.

The 11 skills

SkillWhat it does
Post WriterDrafts viral-ready posts using 20 proven 2026 hook formulas (anaphora, R.I.P. obituary, year-over-year pivot, curiosity gap, emotional cold-open, controlled A/B, false-binary, and 13 more) plus a founders-edition angle library, picked by engagement goal
Comment DrafterDrafts a comment on any LinkedIn post from its URL
Reply HandlerDrafts a reply to any comment, correctly handling LinkedIn's 2-level thread flattening
Post AuditChecks your draft against 2026 algorithm rules and AI-detection patterns before you publish
HumanizerStrips em dashes, AI vocabulary ("leverage", "delve", "harness"), rule-of-three lists, and other AI fingerprints. Bundles three sub-tools: AI-emoji density scorer, multi-detector spread tester (GPTZero, Originality.ai, ZeroGPT, Sapling, Copyleaks), and a rule-explainer reference for defending stylistic choices.
Hook ExtractorReverse-engineers the hook formula from any viral post. Returns a blank template you can fill with your own topic
Content PlannerCreates a 7-day plan with daily post topics, formats, hooks, posting times, and comment targets
Engagement MonitorTwo read-side workflows: (1) tracks your comment threads for author replies and drafts follow-ups in the 6-24h window; (2) pulls likers and commenters on any post and groups them by ICP fit (peer / aspirational / prospect).
Profile OptimizerRewrites your headline, About section, Featured section, and Experience for 2026 conversion patterns
Employee AdvocacyPlans a team LinkedIn program: 14-day launch, posting cadence, brand governance, ROI tracking
RepurposerTurns content from another platform (tweet, thread, YouTube video, blog, newsletter) into a native LinkedIn post: re-hooks for the fold, expands to the 900-1300 char sweet spot, moves links to the first comment, runs the humanizer

Built for founders

If you are a founder, the bundle ships a dedicated founder layer. Your real constraint is rarely reach. It is a small number of high-stakes readers: the next investor, the next hire, the design partner who becomes a case study. The founder layer optimizes for trust with that narrow audience instead of impressions.

  • 10 founder angles (references/founder-topics.md) as fill-in templates: reprice the category, content-to-pipeline, audience of one, the scarce-shots math, the unglamorous bet, the limit of delegation, designed serendipity, the evasive-sentence test, the delegation line, the learning gate. Each maps to an engagement goal and a hook formula.
  • 4 structural hook formulas (F17-F20) that shape a post's logic: controlled A/B anecdote, false-binary dissolve, anecdote-meets-evidence bridge, diverging-curves close.
  • A founders-edition content plan (Conviction / Building in public / The math / Proof) in the Content Planner.

Just tell the Post Writer you are a founder, or ask the Content Planner for a "founder plan," and the skills reach for these first.

Optional: read LinkedIn data with Apify

Four of the skills (Comment Drafter, Reply Handler, Hook Extractor, Engagement Monitor) can read post bodies, comment threads, your own recent comments, and the people who liked or commented on any post. Without an Apify token they fall back to asking you to paste the relevant text. With one, they fetch automatically.

Apify free tier ships with $5/month of credit, which goes a long way at $1-$5 per 1,000 results. The skills use four no-cookies actors:

Use caseActorCost
Post body by URLsupreme_coder/linkedin-post$1 / 1,000
Comments + replies on a postapimaestro/linkedin-post-comments-replies-engagements-scraper-no-cookies$5 / 1,000
Your own recent commentsapimaestro/linkedin-profile-comments$5 / 1,000
Likers + commenters on any postscraping_solutions/linkedin-posts-engagers-likers-and-commenters-no-cookies$5 / 1,000

Setup: drop APIFY_TOKEN=apify_api_... into your .env. The thin client at lib/apify_client.py exposes fetch_post, fetch_post_comments, fetch_user_recent_comments, and fetch_post_engagers.

A typical creator running daily comment ops + a weekly engager-analytics sweep stays under $2/month, well inside the free tier.

Optional: auto-post with Publora

By default, skills draft content for you to copy-paste into LinkedIn. If you want Claude Code or Codex to publish directly to your LinkedIn (and optionally to X, Threads, Instagram), connect Publora. It takes about 2 minutes.

What is Publora?

Publora is a publishing API that handles LinkedIn's quirks (3 different URL formats, reaction type mismatches, thread flattening bugs). The free tier gives you 15 posts/month.

Setup (2 minutes)

Step 1. Sign up at https://app.publora.com/signup (free)

Step 2. Connect LinkedIn: click Channels in the left sidebar, then Add Channel, pick LinkedIn, authorize.

Step 3. Find your Platform ID: go to Channels, click your LinkedIn account. The ID looks like linkedin-ABC123DEF. Copy the whole thing including linkedin-.

Step 4. Get your API key: click Settings (gear icon, bottom-left), then API, then Create Key. Copy the sk_... string.

Step 5. Create a file called .env in the linkedin-skills folder:

PUBLORA_API_KEY=sk_paste_your_key_here
LINKEDIN_PLATFORM_ID=linkedin-paste_your_id_here

If you cloned the repo, you can copy the template instead:

cp .env.example .env

Then open .env and replace the placeholders with your real values.

Step 6. Install two small Python packages:

pip install requests python-dotenv

Step 7. Test it. Ask Claude Code or Codex:

"Schedule a test LinkedIn post via Publora 24 hours from now: 'testing the API connection — will cancel in dashboard'."

If Publora returns a scheduled-post ID, you're set. Cancel the post in the Publora dashboard before the scheduled time. If you get HTTP 401, your API key is wrong. If you get HTTP 400 about a missing platformId, your LINKEDIN_PLATFORM_ID isn't set. See Troubleshooting.

Optional: generate illustrations with Pixfaro

Posts with a visual get more dwell time. The Post Writer can generate an illustration for a draft (a feed image, a carousel slide, or a quote-card of your hook) and attach it automatically when publishing. Without a key it drafts the image prompt and asks you to generate it yourself, so nothing breaks.

Pixfaro is a single image API over multiple models (from flux-schnell at $0.004 to gpt-5-image). It composites your handle, brand color, or logo onto the image as a pixel-exact overlay, so a cheap base model still renders crisp text on a quote-card or thumbnail. Pull those brand fields from your Voice & Brand Profile (section 6) and every asset stays on-brand.

Setup: drop PIXFARO_TOKEN=pf_live_... into your .env. The thin client at lib/pixfaro_client.py and the wrappers lib.illustrate(prompt, kind=...) / lib.refine(image_id, instruction) return a hosted URL that flows straight into lib.publish(..., media_urls=[url]). refine edits a prior image by its id (cheaper than regenerating); results carry cost, balance_after, and a premium flag so the skills never quietly spend on a pricey model.

Voice rules

Every skill follows these rules automatically:

  1. No em dashes. Biggest AI tell in 2026.
  2. Capitalize names. Always. Lowercase reads as disrespectful.
  3. No AI vocabulary: "leverage", "fundamentally", "streamline", "harness", "delve", "unlock", "foster".
  4. Specific numbers beat adjectives. "$14,200" beats "significant savings".
  5. One sharp insight per comment beats three vague ones.
  6. 200-350 chars for comments, 900-1,300 chars for posts.

Troubleshooting

ProblemFix
Skills don't activate when I ask about LinkedInMake sure you installed via the Skills panel, /plugin install, or codex plugin add. Try starting a new conversation.
"Publora API key not provided"Your .env file is missing or in the wrong folder. It should be in the linkedin-skills/ root.
"401 Unauthorized" from PubloraYour API key expired. Go to Publora Settings > API > Create a new key.
"404 on comment/post"Your LINKEDIN_PLATFORM_ID is wrong. Go to Publora Channels and copy the full linkedin-... string.
"400 reactionType" errorKnown Publora quirk. The skills handle this automatically. If you're calling the API manually, use PRAISE (not CELEBRATE), INTEREST (not INSIGHTFUL).
pip install failsUse a virtual environment: python -m venv venv && source venv/bin/activate && pip install requests python-dotenv

Cross-cutting references


For developers: runtime compatibility, URL parsing, and internals

Runtime compatibility

linkedin-skills/
├── skills/          ← SKILL.md frontmatter; native to Claude Code and Codex, others read as markdown
├── .codex-marketplace/ ← generated nested Codex package (run scripts/sync_codex_marketplace.py)
├── lib/             ← pure Python, works in any agent runtime
├── references/      ← pure markdown, works anywhere
└── scripts/         ← pure Python CLI, works anywhere
RuntimeAuto-discovers skills?Setup
Claude Code (CLI, Desktop, Web, IDE)YesInstall via plugin or clone. Skills activate on matching prompts.
Codex CLIYesInstall via codex plugin marketplace add sergebulaev/linkedin-skills and codex plugin add linkedin-skills@linkedin-skills.
Anthropic Managed Agents (/v1/agents)YesPass skill files in the agent context.
OpenClawManualMount the repo, add system prompt pointing to skills/*/SKILL.md.
Cursor / Cline / AiderManualRead SKILL.md files as prompt context; import lib/ as Python.
ManusNoUpload references/ as knowledge base. Call Publora API directly.
LangChain / AutoGenNoUse lib/ as a package; feed references/ as prompt context.

OpenClaw quickstart

git clone git@github.com:sergebulaev/linkedin-skills.git

# Add to OpenClaw system prompt:
# "You have LinkedIn marketing skills in ./linkedin-skills/.
#  Read the relevant skills/*/SKILL.md before any LinkedIn task.
#  Use lib/url_parser.py for URL parsing,
#      lib/apify_client.py for reading posts / comments / engagers,
#      lib/publora_client.py for publishing."

Generic Python agent quickstart

import sys; sys.path.insert(0, "path/to/linkedin-skills")
from lib import parse_linkedin_url, PubloraClient, ApifyClient

parsed = parse_linkedin_url("https://www.linkedin.com/posts/slug-activity-7448808898326654978-iW20")
print(parsed["post_urn"])  # urn:li:activity:7448808898326654978

# Read side (Apify)
apify = ApifyClient()  # reads APIFY_TOKEN from env
post = apify.fetch_post(post_url="https://www.linkedin.com/posts/...")
engagers = apify.fetch_post_engagers(post_url="https://www.linkedin.com/posts/...", max_items=50)

# Write side (Publora)
client = PubloraClient()  # reads PUBLORA_API_KEY from env
client.create_comment(post_urn=parsed["post_urn"], message="draft", platform_id="linkedin-xxx")

# Image side (Pixfaro) — optional, reads PIXFARO_TOKEN from env
from lib import illustrate
img = illustrate("Minimal flat-vector lighthouse, calm blue palette", kind="wide")
# img["url"] -> pass to publish(..., media_urls=[img["url"]])

URL handling

LinkedIn has three post URN types. The lib/url_parser.py handles all of them:

URL fragmentURN
/posts/slug-activity-7448...urn:li:activity:7448...
/posts/slug-share-7449...urn:li:share:7449...
/feed/update/urn:li:ugcPost:7447...urn:li:ugcPost:7447...

Comment URLs include a commentUrn query param. The parser extracts both post_urn and comment_id.

Thread flattening

LinkedIn flattens reply threads to 2 levels. When replying to a reply, parentComment must point to the top-level comment URN, not the reply's URN. The linkedin-reply-handler skill handles this correctly.

Testing the parser

python lib/url_parser.py "https://www.linkedin.com/posts/<author-handle>_activity-<id>"

References

Who builds this

These skills come out of Creative Content Crafts, an engineering company. We build the machinery underneath a company's public voice: ICP parsing, engagement systems, content guardrails, and posting infrastructure. We do not sell the words themselves.

We call that layer content engineering. Writing collapsed to the price of a chat subscription. What stayed valuable is everything below it: pulling every post your market wrote this week, keeping a live list of the people who matter, engaging on it daily with judgment in the loop, and catching the risky drafts before the platform does.

On LinkedIn specifically, that is the whole job. We are engineers of LinkedIn growth, not a ghostwriting agency.

This repo is the thin top layer of that stack, open-sourced. The engine underneath is what we build for clients.

License

MIT. Powered by Publora.

Related open-source skill bundles

Part of a family of AI social-media marketing skill bundles for Claude Code and Codex:

Also: Anthropic Skills repo, the awesome-claude-skills directory.

内容与创作

低风险

  • 来源需自行核对维护者身份。
  • 未检测到明显脚本安装指令。
  • 未检测到明显外部权限要求。
  • 未检测到高风险命令。
  • 扫描发现:0 条。

Codex — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/sergebulaev/linkedin-skills.git
  3. 将 "skills/linkedin-content-planner" 文件夹复制到 Codex 的 skills 目录中。
  4. 重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Codex 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/sergebulaev/linkedin-skills.git
  3. 将 "skills/linkedin-content-planner" 文件夹复制到 Claude Code 的 skills 目录中。
  4. 重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Claude Code 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/sergebulaev/linkedin-skills.git
  3. 将 "skills/linkedin-content-planner" 文件夹复制到 Cursor 的 skills 目录中。
  4. 重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Cursor 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/sergebulaev/linkedin-skills.git
  3. 将 "skills/linkedin-content-planner" 文件夹复制到 GitHub Copilot 的 skills 目录中。
  4. 重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/sergebulaev/linkedin-skills.git
  3. 将 "skills/linkedin-content-planner" 文件夹复制到 Windsurf 的 skills 目录中。
  4. 重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Windsurf 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
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.

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): paths to past posts for voice calibration

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

  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 (user provides or skill generates)
    • 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

Related skills

  • 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

发现问题?提交给管理员复核

评分:

评论 (0)

暂无评论,成为第一个评论者吧!