--- name: li-post description: >- Write a LinkedIn post from a raw idea using 21 proven hook formulas, in the user's own voice, humanized so it does not read as AI. Use whenever the user wants a LinkedIn post, a hook, a draft for the feed, "post about X", "turn this into a LinkedIn post", or asks for hook options. Produces three hook options, one full draft, and a copy-ready block that is never published without an explicit yes. title: li-post canonical_url: https://skilld.dev/gh/jakeschincariol/linkedin-agent-skill/li-post last_updated: 2026-09-29T04:25:36.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. > > Supporting files, fetch one when the Skill refers to it: [hooks.json](https://skilld.dev/api/skills-raw/jakeschincariol/linkedin-agent-skill/li-post/hooks.json). > > If the user asked to install this Skill, run `npx skilld install jakeschincariol/linkedin-agent-skill/li-post`. 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-post`, 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-post) 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-post`. 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-post --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/li-post --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-post Turns one raw idea into a LinkedIn post that sounds like the person who posted it. ## Before you write 1. Read `~/.claude/linkedin/voice.md` if it exists. That file is the user's voice profile: how they talk, what they never say, who they are talking to. If it does not exist, ask for **three of their own past posts**, infer the voice from those, and write the file. Do not skip this and do not invent a voice. A post in the wrong voice is worse than no post. 2. Read `hooks.json` in this folder. All 21 formulas, with templates, filled examples, what each is for, and how each one usually gets ruined. 3. If the idea is thin - "post about AI" - do not pad it. Ask one batched question: what happened, to whom, and what did it cost or return. A post needs one specific true thing. Get it before writing. ## The shape LinkedIn rewards dwell time, saves and comments, in that order. So: ``` Line 1 the hook. Alone. It has to survive truncation at ~140 chars mobile. Line 2 the payoff of line 1, not setup for line 3. Body short paragraphs, 1-3 lines each, blank line between every one. No wall. The white space is the format. The turn one line that reframes what came before. Close one specific question, or one instruction. Never both. ``` Length: 900-1,300 characters is the working range for a text post. Under 400 reads as a thought, not a post. Over 2,000 needs to earn every line, and the "see more" tap has to be paid for by line 2. ## The loop **1. Pick three hooks, not one.** Run the idea through `hooks.json` and choose the three formulas that genuinely fit it. Different formulas, not three variations of one. Show them as three numbered lines and say which you would ship and why, in one sentence. **2. Draft the full post** on the strongest hook. **3. Humanize it.** Run the draft through `/li-human` before showing it. Every post from this skill ships humanized. That is not an optional extra step, it is the reason the draft is worth reading. **4. Print the block.** Copy-ready, in a fenced block, exactly as it should be pasted. Then, underneath: ``` POST READY hook: #17 Time Anchor length: 1,140 characters humanizer: 6 artefacts stripped, human score 84 PASS post at: Tuesday 8:15am ET (from your plan) Reply "yes" to log it, or tell me what to change. ``` **5. Never publish.** This skill produces text. The user posts it. On "yes", append the post to `~/.claude/linkedin/log.md` with the date, the hook used and the first line, so `/li-audit` has a history to work from later. ## Rules that make the difference - **One idea per post.** If the draft has two, you have two posts. Say so. - **Numbers over adjectives.** "$4,200" beats "a lot". If the user has not given you a number, ask for one rather than writing around the hole. - **No engagement bait.** "Thoughts?" and "Agree?" are dead. The closing question has to be one only this post could ask. - **Three hashtags maximum**, at the bottom, and only if they are real categories someone follows. - **No links in the post body.** LinkedIn suppresses posts with outbound links. Put the link in the first comment and say so in the receipt. - **Never fabricate.** No invented metrics, clients, revenue figures or outcomes under the user's name, even as a placeholder. If a number is needed and unknown, leave `{{your number}}` in the draft and flag it. ## Example ``` /li-post we built an internal tool that cut proposal time from 5 hours to 20 min ``` ``` HOOKS 1. #17 Time Anchor Writing a proposal used to take me 5 hours. It now takes 20 minutes. 2. #12 Comparison A $12,000 proposal writer vs a weekend and a template. The weekend won. 3. #3 Mistake For two years I charged clients for hours I was wasting on formatting. Shipping #17: the ratio is believable and the number is yours. ```