Skip to main content
skill CX Codex

li-plan — Claude Code skill: LinkedIn week plan, how to install

li-plan turns a blank week into a schedule: four posts with angles from what actually happened, slots in your audience's timezone, and ten people to comment on.

MIT ★ 3,812 updated 2026-09-17

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Jakeschincariol/linkedin-agent-skill
/plugin install linkedin-agent@linkedin-agent-skill
Open on GitHub

What li-plan does

This is the planning step of a LinkedIn pack: other skills draft, li-plan decides what gets drafted. Run it once a week on a fixed day. It opens ~/.claude/linkedin/voice.md and log.md so the new plan avoids themes from the previous fortnight. Without those files it asks four questions instead: what you sell and to whom, the few topics you want to be known for, what happened this week, and which ten to twenty people are worth staying visible to.

Four posts beat seven, spread across post types (proof, opinion, teach, story, offer), with two of them on a fortnightly rotation. Each slot gets a specific angle taken from the week's events plus a hook formula number from li-post/hooks.json. Timing follows the audience's timezone, not yours: Tuesday to Thursday, 7:30–9:30am, with Monday afternoon and Friday morning as the fallback.

Engagement is a list of ten split into five reach, three peers and two buyers, worked for twenty minutes a day before posting. The skill is blunt about priorities: the day and hour matter far less than whether the first line is good, so tuning slots before hooks is wasted effort. The plan lands in ~/.claude/linkedin/plan.md. Nothing is scheduled or published; you run it yourself.

What it helps with

  • turn a blank calendar into four posts with real angles
  • pick posting slots in your audience's timezone
  • build a comment list of reach, peers and buyers
  • avoid repeating themes from the last two weeks
  • get a hook formula number for each post before drafting

Example prompts for the agent

  • Plan my week on LinkedIn
  • I have nothing to post about — build me a content calendar
  • What should I post this week and who should I engage with?

How to install li-plan

1Plugin marketplace

/plugin marketplace add Jakeschincariol/linkedin-agent-skill
/plugin install linkedin-agent@linkedin-agent-skill

This installs the whole linkedin-agent plugin with all its skills

2Skills CLI (Vercel)

npx skills add Jakeschincariol/linkedin-agent-skill --skill li-plan -a claude-code

3Manually: put the files in place

~/.claude/skills/li-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/li-plan/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about li-plan

How do I install li-plan in Claude Code?

Through the plugin marketplace: run /plugin marketplace add Jakeschincariol/linkedin-agent-skill, then /plugin install linkedin-agent@linkedin-agent-skill.

What does li-plan do?

It lays out a LinkedIn week: four posts with concrete angles and hook numbers, days and times matched to the audience, and ten people worth commenting on. The result goes to ~/.claude/linkedin/plan.md.

Do I need voice.md and log.md before running it?

No. Without them the skill asks four questions about what you sell, the topics you want to be known for, what happened this week, and who you want to stay visible to.

Source text

SKILL.md · MIT
---
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:

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:

| 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.

## 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.

© Jake Schincariol · MIT · Jakeschincariol/linkedin-agent-skill

Similar skills

All skills for Marketing and content →

From the same set12

The whole set →

Project sponsors

Companies that keep this analytics open