--- 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. title: li-plan canonical_url: https://skilld.dev/gh/jakeschincariol/linkedin-agent-skill/li-plan last_updated: 2026-09-16T18:45:38.000Z --- > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > If the user asked to install this Skill, run `npx skilld install jakeschincariol/linkedin-agent-skill/li-plan`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/li-plan`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/jakeschincariol/linkedin-agent-skill/li-plan) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/li-plan`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/li-plan --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/li-plan --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # 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.