← Back to list
linkedin-content-planner Checked
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post…
9.1Overall rating
Installation
🤖 Install via AI
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "linkedin-content-planner" skill by following the instructions at https://skill123.me/install/linkedin-content-planner.
⌨️ Command line install
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/linkedin-content-planner.sh | bash
📦 Download ZIP
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 10 KBAbout this skill
Overview
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.
Source
- Repo: https://github.com/sergebulaev/linkedin-skills
- Path: skills/linkedin-content-planner
Score breakdown
Trigger
9.0
Clear What/When with explicit not-for-single-post boundary; trigger phrases slightly thinner than sibling skills.
Structure
9.3
130-line SKILL.md plus focused pillars-framework and a full worked example; good progressive disclosure.
Workflow
8.4
Numbered steps with pillar-sum validation, 60-percent cap warnings, readiness checklist as verification loop; no failure-path handling needed for offline task.
Content
10.0
Concrete tables, named formulas, specific percentages; crisp writing throughout.
Engineering
8.0
Correct frontmatter and existing path references, but bundle-root ../../references dependency limits standalone robustness.
Security
10.0
No scripts, no network calls, no credentials; nothing to exfiltrate.
Pure planning skill, no scripts or network. Strong 3-pillar framework with quantified guardrails, formula-to-pillar mapping, founder-edition variant, worked 7-day example, and an inbound-readiness checklist that doubles as output verification.