Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Build the week on LinkedIn - what to post, when to post it, and who to engage with.
Install Li Plan
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/li-plan .claude/skills/li-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "li-plan" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-plan into .claude/skills/li-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/li-plan .agents/skills/li-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "li-plan" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-plan into .agents/skills/li-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/li-plan .cursor/skills/li-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "li-plan" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-plan into .cursor/skills/li-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill.git --path skills/li-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/li-plan .gemini/skills/li-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "li-plan" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-plan into .gemini/skills/li-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/li-plan .github/skills/li-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "li-plan" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-plan into .github/skills/li-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/li-plan .opencode/skills/li-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "li-plan" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-plan into .opencode/skills/li-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
li-plan- GitHub stars
- 1.7k
- Token cost
- ~905 tokens
- SKILL.md length
- 489 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build the week on LinkedIn - what to post, when to post it, and who to engage with.
- Works in 4 steps: What the user sells, and to whom. → The three or four themes they want to be… → What actually happened this week - a… → …
- The user says plan my week
- SKILL.md covers Input, What to post, When to post and Who to engage with, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Li Plan is an agent skill from Jakeschincariol/linkedin-agent-skill. Build the week on LinkedIn - what to post, when to post it, and who to engage with. Use when the user says "plan my week", "what should I post", "content calendar", "I have nothing to post about", or wants a posting schedule and an engagement list.
Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Content strategy. It works with LinkedIn. The repository describes itself as: Eleven free Claude skills that run a LinkedIn account: posts off 21 hook formulas, comments, replies, profile score, weekly plan, and a humanizer that strips the AI fingerprint… The licence is MIT.
When your agent uses it
- The user says plan my week
- What should I post
- Content calendar
- I have nothing to post about
Example prompts
- “plan my week”
- “what should I post”
- “content calendar”
- “/li-plan”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- What the user sells, and to whom.
- The three or four themes they want to be known for.
- What actually happened this week - a client call, a number, a mistake, a
- Ten to twenty people or companies worth being visible to.
What it can do on your machine
Read from SKILL.md and the folder at commit add2c23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Li Plan loads about 905 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 489 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jakeschincariol/linkedin-agent-skill at commit add2c23, republished under its MIT licence (© Jakeschincariol). 489 words, ~905 tokens.
Download SKILL.mdSave it as
.claude/skills/li-plan/SKILL.md (or your agent's skills folder).- name
- li-plan
- description
- Build the week on LinkedIn - what to post, when to post it, and who to engage with. Use when the user says "plan my week", "what should I post", "content calendar", "I have nothing to post about", or wants a posting schedule and an engagement list.
li-plan
The control room. Everything else in this pack executes; this decides what gets executed. Run it once a week, on the same day.
Input
If ~/.claude/linkedin/voice.md and log.md exist, read them - the plan
should not repeat a theme from the last fortnight. If they do not exist, ask
for four things and write them down:
- What the user sells, and to whom.
- The three or four themes they want to be known for.
- What actually happened this week - a client call, a number, a mistake, a thing they built, an argument they had. This is where posts come from.
- Ten to twenty people or companies worth being visible to.
What to post
Four posts a week beats seven. Consistency is a floor, not a target, and the fifth post of a week is almost always the weak one that drags the average.
Mix across the week, never two of the same type back to back:
| type | share | job |
|---|---|---|
| Proof | 1 per week | something that happened, with a number |
| Opinion | 1 per week | a position that could lose you followers |
| Teach | 1 per week | one thing the reader can do today |
| Story | 1 per fortnight | a scene with dialogue and a cost |
| Offer | 1 per fortnight | what you sell, said plainly, no apology |
For each slot give: the theme, the specific angle drawn from what actually
happened this week, and the hook formula number from li-post/hooks.json that
fits it. Not a topic - an angle. "AI" is not a plan. "The proposal we lost
because our AI draft had an em dash in it" is a post.
Show full SKILL.md (219 more words)Show less
When to post
Post when the user's audience is at a desk. For a B2B audience in one timezone, Tuesday to Thursday, 7:30-9:30am local, is the working default, with Monday afternoon and Friday morning as the second tier. Weekends are for personal-story posts or nothing.
But state this plainly: the day and hour matter far less than whether the first line is good. If the user is optimising posting times before their hooks work, they are polishing the wrong thing, and you should say so.
Anchor the times to their audience's timezone, not the user's, if those differ.
Who to engage with
Build a list of 10, split three ways:
- 5 reach - people with an audience the user wants, whose posts they can genuinely add to. Comment before they have 20 comments or nobody sees it.
- 3 peers - same level, same field. This is the group that reciprocates.
- 2 buyers - people who could actually buy. Comment on their posts for weeks before any DM, and never pitch in a comment.
20 minutes a day, before posting, not after. Comments on other people's posts are what makes the user's own post land.
Output
WEEK OF SEP 8
MON engage only (20 min, list below)
TUE 8:15am PROOF #17 Time Anchor - the 5hr -> 20min proposal rebuild
WED engage only
THU 8:00am OPINION #1 Contrarian - why we killed the discovery call
FRI 8:30am TEACH #21 Direct Value - the 4-line reopen email, given away
SAT -
SUN 4:00pm STORY #9 Cold Open - the "going with someone cheaper" email
ENGAGE (5 reach / 3 peers / 2 buyers)
...
Say "write Tuesday" and I will draft it.Write the plan to ~/.claude/linkedin/plan.md so the other skills can read it.
Nothing is scheduled or posted anywhere - this is a plan, and the user runs it.
© Jakeschincariol, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/li-plan of Jakeschincariol/linkedin-agent-skill.
Open the folder on GitHubat commit add2c23
Compare with similar skills
Li Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Li Plan this skillJakeschincariol/linkedin-agent-skill | 1.7k | — | ~905 | Automated safety check: Pass | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Content Matrixcharlie947/social-media-skills | 3.8k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Caption Writerstevenflanagan1/social-ai-team | 244 | — | ~2.9k | Automated safety check: Pass | None | |
| Content Calendarstevenflanagan1/social-ai-team | 244 | — | ~3.1k | Automated safety check: Pass | None | |
| Content Calendar Smsblacktwist/social-media-skills | 560 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Content Matrix
charlie947/social-media-skills
Generate 24 to 40 LinkedIn post ideas in a single table by pairing the user's content pillars with 8 proven content formats.
Caption Writer
stevenflanagan1/social-ai-team
Writes on-brand social media captions for SMBs. An agent skill from stevenflanagan1/social-ai-team.
Content Calendar
stevenflanagan1/social-ai-team
Builds a month of social media post ideas for SMBs. An agent skill from stevenflanagan1/social-ai-team.
Content Calendar Sms
blacktwist/social-media-skills
When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post.
Linkedin Writer
stevenflanagan1/social-ai-team
LinkedIn Content Specialist. An agent skill from stevenflanagan1/social-ai-team.
More from Jakeschincariol/linkedin-agent-skill
All 11 skills in this repoLi Audit
Jakeschincariol/linkedin-agent-skill
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing.
Li Carousel
Jakeschincariol/linkedin-agent-skill
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.
Li Comment
Jakeschincariol/linkedin-agent-skill
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
Li Dm
Jakeschincariol/linkedin-agent-skill
Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups.
Li Human
Jakeschincariol/linkedin-agent-skill
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out.
Li Inbox
Jakeschincariol/linkedin-agent-skill
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
Related
Works with
Categories
Questions about Li Plan
What does Li Plan do?
Build the week on LinkedIn - what to post, when to post it, and who to engage with. Li Plan is an agent skill from Jakeschincariol/linkedin-agent-skill. Build the week on LinkedIn - what to post, when to post it, and who to engage with.
When should I use Li Plan?
Li Plan fits situations like: the user says plan my week; what should I post; content calendar; I have nothing to post about.
How do I install Li Plan in Claude Code?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a claude-code`. Or copy the skill folder (skills/li-plan in Jakeschincariol/linkedin-agent-skill) into .claude/skills/li-plan in your project. Claude Code loads it when a task matches its description.
How do I install Li Plan in Codex?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a codex`. Or copy the skill folder (skills/li-plan in Jakeschincariol/linkedin-agent-skill) into .agents/skills/li-plan in your project. Codex loads it when a task matches its description.
Can I use Li Plan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/li-plan, .gemini/skills/li-plan, .github/skills/li-plan and .opencode/skills/li-plan in your project.
What does Li Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Li Plan is instructions for the agent only.
Does Li Plan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Li Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Li Plan use?
Li Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Li Plan use?
About 905 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Li Plan?
Skills that share tags, products or a category with Li Plan: Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars), Content Matrix (charlie947/social-media-skills, 3.8k stars), Caption Writer (stevenflanagan1/social-ai-team, 244 stars) and Content Calendar (stevenflanagan1/social-ai-team, 244 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Li Plan?
Jakeschincariol (a GitHub user) maintains it in Jakeschincariol/linkedin-agent-skill, which has 1,688 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 17, 2026.
Source: Jakeschincariol/linkedin-agent-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.