使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jakeschincariol/linkedin-agent-skill --skill li-plan開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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.
