Li plan skill
Build the week on LinkedIn - what to post, when to post it, and who to engage with.
by Jakeschincariol·MIT license·★ 1,856 Stars on the repo·GitHub ↗
npx degit Jakeschincariol/linkedin-agent-skill/skills/li-plan#main ~/.claude/skills/li-planChecked ·commit main
Inside this skill
SKILL.md · the author's own words# 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.
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Li plan
Show the full text95 lines
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.
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.
| 1 | |
| 2 | name li-plan |
| 3 | description >- |
| 4 | Build the week on LinkedIn - what to post, when to post it, and who to engage |
| 5 | with. Use when the user says "plan my week", "what should I post", "content |
| 6 | calendar", "I have nothing to post about", or wants a posting schedule and an |
| 7 | engagement list. |
| 8 | |
| 9 | |
| 10 | # li-plan |
| 11 | |
| 12 | The control room. Everything else in this pack executes; this decides what |
| 13 | gets executed. Run it once a week, on the same day. |
| 14 | |
| 15 | ## Input |
| 16 | |
| 17 | If `~/.claude/linkedin/voice.md` and `log.md` exist, read them - the plan |
| 18 | should not repeat a theme from the last fortnight. If they do not exist, ask |
| 19 | for four things and write them down: |
| 20 | |
| 21 | What the user sells, and to whom. |
| 22 | The three or four themes they want to be known for. |
| 23 | What actually happened this week - a client call, a number, a mistake, a |
| 24 | thing they built, an argument they had. This is where posts come from. |
| 25 | Ten to twenty people or companies worth being visible to. |
| 26 | |
| 27 | ## What to post |
| 28 | |
| 29 | Four posts a week beats seven. Consistency is a floor, not a target, and the |
| 30 | fifth post of a week is almost always the weak one that drags the average. |
| 31 | |
| 32 | Mix across the week, never two of the same type back to back: |
| 33 | |
| 34 | | type | share | job | |
| 35 | | --- | --- | --- | |
| 36 | | **Proof** | 1 per week | something that happened, with a number | |
| 37 | | **Opinion** | 1 per week | a position that could lose you followers | |
| 38 | | **Teach** | 1 per week | one thing the reader can do today | |
| 39 | | **Story** | 1 per fortnight | a scene with dialogue and a cost | |
| 40 | | **Offer** | 1 per fortnight | what you sell, said plainly, no apology | |
| 41 | |
| 42 | For each slot give: the theme, the specific angle drawn from what actually |
| 43 | happened this week, and the hook formula number from `li-post/hooks.json` that |
| 44 | fits it. Not a topic - an angle. "AI" is not a plan. "The proposal we lost |
| 45 | because our AI draft had an em dash in it" is a post. |
| 46 | |
| 47 | ## When to post |
| 48 | |
| 49 | Post when the user's audience is at a desk. For a B2B audience in one |
| 50 | timezone, Tuesday to Thursday, 7:30-9:30am local, is the working default, with |
| 51 | Monday afternoon and Friday morning as the second tier. Weekends are for |
| 52 | personal-story posts or nothing. |
| 53 | |
| 54 | But state this plainly: **the day and hour matter far less than whether the |
| 55 | first line is good.** If the user is optimising posting times before their |
| 56 | hooks work, they are polishing the wrong thing, and you should say so. |
| 57 | |
| 58 | Anchor the times to their audience's timezone, not the user's, if those |
| 59 | differ. |
| 60 | |
| 61 | ## Who to engage with |
| 62 | |
| 63 | Build a list of 10, split three ways: |
| 64 | |
| 65 | **5 reach** - people with an audience the user wants, whose posts they can |
| 66 | genuinely add to. Comment before they have 20 comments or nobody sees it. |
| 67 | **3 peers** - same level, same field. This is the group that reciprocates. |
| 68 | **2 buyers** - people who could actually buy. Comment on their posts for |
| 69 | weeks before any DM, and never pitch in a comment. |
| 70 | |
| 71 | 20 minutes a day, before posting, not after. Comments on other people's posts |
| 72 | are what makes the user's own post land. |
| 73 | |
| 74 | ## Output |
| 75 | |
| 76 | |
| 77 | WEEK OF SEP 8 |
| 78 | |
| 79 | MON engage only (20 min, list below) |
| 80 | TUE 8:15am PROOF #17 Time Anchor - the 5hr -> 20min proposal rebuild |
| 81 | WED engage only |
| 82 | THU 8:00am OPINION #1 Contrarian - why we killed the discovery call |
| 83 | FRI 8:30am TEACH #21 Direct Value - the 4-line reopen email, given away |
| 84 | SAT - |
| 85 | SUN 4:00pm STORY #9 Cold Open - the "going with someone cheaper" email |
| 86 | |
| 87 | ENGAGE (5 reach / 3 peers / 2 buyers) |
| 88 | ... |
| 89 | |
| 90 | Say "write Tuesday" and I will draft it. |
| 91 | |
| 92 | |
| 93 | Write the plan to `~/.claude/linkedin/plan.md` so the other skills can read it. |
| 94 | Nothing is scheduled or posted anywhere - this is a plan, and the user runs it. |
| 95 |
Discussion
Browse more free Claude skills.