li-audit
Post-mortem on what the user has already published - which posts actually worked, why, and…
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.
$ npx -y skills add Jakeschincariol/linkedin-agent-skill --skill li-plan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/li-planContext preview
The summary Claude sees to decide when to auto-load this 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.
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.
The control room. Everything else in this pack executes; this decides what gets executed. Run it once a week, on the same day.
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.
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.
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.
Build a list of 10, split three ways:
genuinely add to. Comment before they have 20 comments or nobody sees it.
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.
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.
Eleven Claude skills that run a LinkedIn account. Free, MIT, no signup, no API key, nothing to connect. One of them writes your posts off 21 hook formulas. One comments on other people's posts. One handles the replies under yours.
Post-mortem on what the user has already published - which posts actually worked, why, and…
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the…
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a…
Write connection notes and DM follow-ups that get replies - the 200-character invite, the…
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible…
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers…