Who it is forA founder or consultant with a rough idea and 15 minutes who wants to publish a post this week without a blank page.
The problemStarting from nothing takes too long, and generic AI drafts read as slop to the people you are trying to reach.
The outcomeA copy-ready post with three hook options from the 21 formulas, one full draft that has been humanized, and a block you paste yourself.
What you need first
- Claude access, either Claude Code for installing the skills or a chat where you can paste a SKILL.md
- A LinkedIn account you will post from yourself, since the skills never post for you
- Python 3 for the humanizer scripts, which need no extra dependencies
- Three of your own past posts, or a filled-in templates/voice.md, so drafts match your voice
Steps
- Run
git clone https://github.com/Jakeschincariol/linkedin-agent-skill.gitin a terminal. - Run
cp -r linkedin-agent-skill/skills/li-* ~/.claude/skills/to install the skills globally. - Run
cp templates/voice.md ~/.claude/linkedin/voice.mdfrom inside the cloned repo, then fill in the file or ask Claude to write it from three of your posts. (inferred, check the README) - In Claude Code, type
/li-postand give it one idea in a sentence or two. - Pick one of the three hooks, read the full draft, and post it yourself on LinkedIn.
Prompt for your agent
Install the skills from https://github.com/Jakeschincariol/linkedin-agent-skill, fill in voice.md from the three posts at <path to your posts>, then run /li-post on the idea: <your idea>. Expected output: three hook options and one full draft with no em dashes and no invented numbers. Verify that any figure you did not supply appears as {{your number}}.
Caveat. The skills write drafts only, so you must copy each post into LinkedIn yourself, and the quality depends on how well voice.md describes you.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page