MCPInstall

li-plan

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.

Installs
243
Last 24h
+13
Trending rank
#7468
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/jakeschincariol/linkedin-agent-skill --skill li-plan
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads li-plan automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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:

  1. What the user sells, and to whom.
  2. The three or four themes they want to be known for.
  3. 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.
  4. 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:

typesharejob
Proof1 per weeksomething that happened, with a number
Opinion1 per weeka position that could lose you followers
Teach1 per weekone thing the reader can do today
Story1 per fortnighta scene with dialogue and a cost
Offer1 per fortnightwhat 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.

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.

FAQ

What does the li-plan skill do?

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.

How do I install li-plan?

Run npx skills add https://github.com/jakeschincariol/linkedin-agent-skill --skill li-plan in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/li-plan/ (personal) or .claude/skills/li-plan/ (project).

Which AI agents can use li-plan?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is li-plan safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains li-plan?

It is published by jakeschincariol in jakeschincariol/linkedin-agent-skill. It has 243 recorded installs.

More from jakeschincariol/linkedin-agent-skill

View all →

li-post

jakeschincariol/linkedin-agent-skill

Write a LinkedIn post from a raw idea using 21 proven hook formulas, in the user's own voice, humanized so it does not read as AI. Use whenever the user wants a LinkedIn post, a hook, a draft for the feed, "post about X", "turn this into a LinkedIn post", or asks for hook options. Produces three hook options, one full draft, and a copy-ready block that is never published without an explicit yes.

Marketing & SEO247 installs

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. Use whenever text needs to sound human, when the user says humanize, "does this sound like AI", "remove the em dashes", "de-slop this", "will this get flagged", or before any LinkedIn post, comment, reply or DM is shown to the user.

Marketing & SEO245 installs

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. Use when the user says "carousel", "document post", "slides for LinkedIn", "turn this into a carousel", or has a list-shaped idea that would die as a text post.

Marketing & SEO244 installs

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. Use when the user pastes a post and wants a comment, says "comment on this", "engage with this", "what do I say here", or wants a batch of comments for their engagement round.

Marketing & SEO243 installs

li-profile

jakeschincariol/linkedin-agent-skill

Open the skill to read its SKILL.md instructions.

Marketing & SEO242 installs

li-dm

jakeschincariol/linkedin-agent-skill

Open the skill to read its SKILL.md instructions.

Marketing & SEO237 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.