Social
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
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.
Install Li Post
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-post --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/li-post .claude/skills/li-post && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "li-post" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-post into .claude/skills/li-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-post", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-postType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-post --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/li-post .agents/skills/li-post && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "li-post" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-post into .agents/skills/li-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-post", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-post --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/li-post .cursor/skills/li-post && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "li-post" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-post into .cursor/skills/li-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-post", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill.git --path skills/li-post--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-post --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/li-post .gemini/skills/li-post && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "li-post" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-post into .gemini/skills/li-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-post", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-postInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/li-post .github/skills/li-post && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "li-post" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-post into .github/skills/li-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-post", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-post --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/li-post .opencode/skills/li-post && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "li-post" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-post into .opencode/skills/li-post/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-post", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
li-post- GitHub stars
- 1.6k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 487 words
- Files
- 2
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 3 steps: Read ~/.claude/linkedin/voice.md if it… → Read hooks.json in this folder. All 21… → If the idea is thin - "post about AI" -…
- The user wants a LinkedIn post
- SKILL.md covers Before you write, The shape, The loop and Rules that make the difference, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Li Post is an agent skill from Jakeschincariol/linkedin-agent-skill. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `hooks.json`).
It sits in Writing & Content, covering Social media posts. It works with LinkedIn. The repository describes itself as: Eleven free Claude skills that run a LinkedIn account: posts off 21 hook formulas, comments, replies, profile score, weekly plan, and a humanizer that strips the AI fingerprint… The licence is MIT.
When your agent uses it
- The user wants a LinkedIn post
- A draft for the feed
- Turn this into a LinkedIn post
- Asks for hook options
Example prompts
- “post about X”
- “turn this into a LinkedIn post”
- “/li-post”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read ~/.claude/linkedin/voice.md if it exists. That file is the user's
- Read hooks.json in this folder. All 21 formulas, with templates, filled
- If the idea is thin - "post about AI" - do not pad it. Ask one batched
What it can do on your machine
Read from SKILL.md and the folder at commit add2c23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Li Post loads about 1.1k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 487 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jakeschincariol/linkedin-agent-skill at commit add2c23, republished under its MIT licence (© Jakeschincariol). 487 words, ~1,084 tokens.
Download SKILL.mdSave it as
.claude/skills/li-post/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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.
li-post
Turns one raw idea into a LinkedIn post that sounds like the person who posted it.
Before you write
- Read
~/.claude/linkedin/voice.mdif 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. - Read
hooks.jsonin this folder. All 21 formulas, with templates, filled examples, what each is for, and how each one usually gets ruined. - 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.
Show full SKILL.md (140 more words)Show less
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 minHOOKS
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.© Jakeschincariol, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/li-post of Jakeschincariol/linkedin-agent-skill.
- SKILL.md
- hooks.json
Open the folder on GitHubat commit add2c23
Compare with similar skills
Li Post next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Li Post this skillJakeschincariol/linkedin-agent-skill | 1.6k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Social Contentfreekmurze/dotfiles | 1k | 23 repos | ~2.1k | Automated safety check: Pass | None | |
| Linkedin Marketingsergebulaev/linkedin-skills | 4.4k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.4k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Typefullyfreekmurze/dotfiles | 1k | 1 repos | ~3.4k | Automated safety check: Notes | None |
Similar skills
Social Content
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
Linkedin Marketing
sergebulaev/linkedin-skills
Plan, draft, audit, and publish LinkedIn posts and comments.
Linkedin Content Planner
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
Typefully
freekmurze/dotfiles
Create, schedule, and manage social media posts via Typefully.
Changelog Social Recap
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
More from Jakeschincariol/linkedin-agent-skill
All 11 skills in this repoLi Audit
Jakeschincariol/linkedin-agent-skill
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing.
Li Carousel
Jakeschincariol/linkedin-agent-skill
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.
Li Comment
Jakeschincariol/linkedin-agent-skill
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
Li Dm
Jakeschincariol/linkedin-agent-skill
Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups.
Li Human
Jakeschincariol/linkedin-agent-skill
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out.
Li Inbox
Jakeschincariol/linkedin-agent-skill
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
Related
Works with
Categories
Questions about Li Post
What does Li Post do?
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. Li Post is an agent skill from Jakeschincariol/linkedin-agent-skill. 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.
When should I use Li Post?
Li Post fits situations like: the user wants a LinkedIn post; A draft for the feed; turn this into a LinkedIn post; asks for hook options.
How do I install Li Post in Claude Code?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a claude-code`. Or copy the skill folder (skills/li-post in Jakeschincariol/linkedin-agent-skill) into .claude/skills/li-post in your project. Claude Code loads it when a task matches its description.
How do I install Li Post in Codex?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a codex`. Or copy the skill folder (skills/li-post in Jakeschincariol/linkedin-agent-skill) into .agents/skills/li-post in your project. Codex loads it when a task matches its description.
Can I use Li Post in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-post -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/li-post, .gemini/skills/li-post, .github/skills/li-post and .opencode/skills/li-post in your project.
What does Li Post need to run?
SKILL.md names no scripts, command-line tools or credentials: Li Post is instructions for the agent only.
Does Li Post access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Li Post safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Li Post use?
Li Post is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Li Post use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Li Post?
Skills that share tags, products or a category with Li Post: Social (coreyhaines31/marketingskills, 54k stars), Social Content (freekmurze/dotfiles, 1k stars), Linkedin Marketing (sergebulaev/linkedin-skills, 4.4k stars) and Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Li Post?
Jakeschincariol (a GitHub user) maintains it in Jakeschincariol/linkedin-agent-skill, which has 1,627 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 17, 2026.
Source: Jakeschincariol/linkedin-agent-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.