Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

linkedin-content-plannerlinkedin 内容规划师

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

2,546

周安装

103

GitHub Stars

公开资料未说明

下载量

799
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:linkedin-content-planner(linkedin 内容规划师)
来源仓库:https://github.com/sergebulaev/linkedin-content-planner
安装命令:
openclaw skills install linkedin-content-planner
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install linkedin-content-planner

简介

生成定制的 7 天 LinkedIn 内容计划,其中包含支柱、格式、挂钩、CTA、评论目标和每周参与清单。

SKILL.md

name
linkedin-content-planner
description
Generate a 7-day LinkedIn content plan given a theme, audience, and content pillars. Produces per-day recommendations (pillar, format, hook, angle, CTA type, best time), daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week of posts and comments instead of ad-hoc shipping. Keywords: content plan, weekly calendar, content pillars, LinkedIn strategy, founder schedule.

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%) used by Justin Welsh, Matt Gray, Jasmin Alic. 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 type
Mon(commenting day)
Tue8:00 AM localAuthorityTextF7 Odd-Precision Money"What 3 months of agent ops costs"Question close
Wed9:30 AM localNarrativeTextF4 Time-Anchor Confession"Why I stopped publishing for 4 weeks"Mirror question
Thu8:00 AM localCommunityPoll"Which metric matters most"Poll
Fri9:00 AM localAuthorityCarouselF10 Contrarian Historical"AI agencies have been dying since 2023"Soft offer
Sat/Sun(off)

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

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
NarrativeF4 Time-Anchor Confession, F3 Year-over-Year Pivot, F9 Curiosity-Gap
CommunityF6 Comment-Gate (use sparingly), poll posts, spotlight mentions
Product/OfferF2 R.I.P. Obituary (when pivoting category), F1 Anaphora (when framing product as fix)

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)

  1. For each posting day, add 3-5 comment targets with suggested pattern.
  2. Run inbound-readiness check; flag anything missing.
  3. 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

Related skills

  • linkedin-post-writer — generate each day's draft from the plan
  • linkedin-comment-drafter — execute the daily comment targets
  • linkedin-thread-engagement — track inbound from the comment strategy

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

85.84%
按下载量换算686

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills