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.
Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering.
Install Li Reply
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-reply --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-reply .claude/skills/li-reply && 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-reply" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-reply into .claude/skills/li-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-reply", 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-replyType 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-reply -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-reply --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-reply .agents/skills/li-reply && 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-reply" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-reply into .agents/skills/li-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-reply", 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-reply -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-reply --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-reply .cursor/skills/li-reply && 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-reply" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-reply into .cursor/skills/li-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-reply", 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-reply--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-reply -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-reply --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-reply .gemini/skills/li-reply && 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-reply" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-reply into .gemini/skills/li-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-reply", 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-replyInstalls 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-reply -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-reply .github/skills/li-reply && 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-reply" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-reply into .github/skills/li-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-reply", 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-reply -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-reply --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-reply .opencode/skills/li-reply && 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-reply" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-reply into .opencode/skills/li-reply/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-reply", 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-reply- GitHub stars
- 1.6k
- Token cost
- ~753 tokens
- SKILL.md length
- 337 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering.
- The user pastes the comments on their post
- SKILL.md covers Input, Triage first, How to reply and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Says reply to these
What it does
Li Reply is an agent skill from Jakeschincariol/linkedin-agent-skill. Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering. Use when the user pastes the comments on their post, says "reply to these", "handle my comments", "someone said X on my post", or is dealing with a critic or a lead in the comments.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Social media posts. 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 pastes the comments on their post
- Says reply to these
- Handle my comments
- Someone said X on my post
Example prompts
- “reply to these”
- “handle my comments”
- “someone said X on my post”
- “/li-reply”
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 Reply loads about 753 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 337 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). 337 words, ~753 tokens.
Download SKILL.mdSave it as
.claude/skills/li-reply/SKILL.md (or your agent's skills folder).- name
- li-reply
- description
- Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering. Use when the user pastes the comments on their post, says "reply to these", "handle my comments", "someone said X on my post", or is dealing with a critic or a lead in the comments.
li-reply
The reply thread under your own post is where reach is actually decided. Every reply is a second engagement event on the post, and the first hour of replies does most of the work. But the value is not equal across comments, so this skill sorts before it writes.
Input
The user pastes the comments, ideally with names and roles. Screenshots are fine. Do not scrape the thread with a browser tool.
Triage first
Sort every comment into one of five buckets and say the count out loud:
| bucket | what it is | what it gets |
|---|---|---|
| LEAD | someone describing the problem you solve | a real answer + a soft open door |
| SUBSTANCE | adds data, disagrees, extends | the longest reply on the thread |
| PEER | a name worth being seen next to | a reply that gives them something |
| SUPPORT | "great post", 🔥, a tag | a like, and a 3-8 word reply at most |
| NOISE | pitch, spam, bad faith | nothing, or one line and out |
Then write in that order, and stop writing when the value stops.
How to reply
- Answer the actual question. If someone asks how, tell them how, in the reply. Do not send them to a DM to hear the answer they could have had.
- Use their name once, at the start, and never with an exclamation mark.
- Match their length. A two-line comment does not get a six-line reply.
- To a critic: concede the true part first, in their words, then hold the line on the part you believe. Never delete, never get defensive, never reply twice on the same thread.
- To a lead: answer fully in public. The open door is one sentence at the end, and it is an offer of help, not a pitch. Public value is what makes the next person DM you.
- To a pitch in your comments: ignore it. Replying gives it reach.
Output
One block, grouped by bucket, each reply copy-ready and already humanized:
REPLIES · 17 comments · 1 LEAD, 3 SUBSTANCE, 4 PEER, 8 SUPPORT, 1 NOISE
LEAD
@Sarah Chen - "we have the same problem with proposals"
> The part that fixed it for us was pulling the pricing table out of the doc
> entirely and sending it as its own page. Cut a whole review round. Happy to
> send you the template if it is useful.
SUBSTANCE
@Marcus Webb - disagrees on cadence
> Fair, and 4x a week only worked because I had 8 months of posts behind it.
> From a standing start I would do what you said.
SUPPORT (like these, reply to the first three)
@... "This is great" -> Thanks Dan.
...
NOISE (1)
Skipped: an agency pitch. Replying gives it reach.Then the gate: nothing is posted until the user says yes. They paste the replies themselves.
© 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
Just SKILL.md in skills/li-reply of Jakeschincariol/linkedin-agent-skill.
Open the folder on GitHubat commit add2c23
Compare with similar skills
Li Reply 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 Reply this skillJakeschincariol/linkedin-agent-skill | 1.6k | — | ~753 | 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
Categories
Questions about Li Reply
What does Li Reply do?
Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering. Li Reply is an agent skill from Jakeschincariol/linkedin-agent-skill. Handle the replies under the user's own LinkedIn posts - draft answers to every comment, sorted by which ones are worth answering.
When should I use Li Reply?
Li Reply fits situations like: the user pastes the comments on their post; says reply to these; handle my comments; someone said X on my post.
How do I install Li Reply in Claude Code?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -a claude-code`. Or copy the skill folder (skills/li-reply in Jakeschincariol/linkedin-agent-skill) into .claude/skills/li-reply in your project. Claude Code loads it when a task matches its description.
How do I install Li Reply in Codex?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-reply -a codex`. Or copy the skill folder (skills/li-reply in Jakeschincariol/linkedin-agent-skill) into .agents/skills/li-reply in your project. Codex loads it when a task matches its description.
Can I use Li Reply 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-reply -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-reply, .gemini/skills/li-reply, .github/skills/li-reply and .opencode/skills/li-reply in your project.
What does Li Reply need to run?
SKILL.md names no scripts, command-line tools or credentials: Li Reply is instructions for the agent only.
Does Li Reply 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 Reply 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 Reply use?
Li Reply 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 Reply use?
About 753 tokens (SKILL.md is roughly 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 Reply?
Skills that share tags, products or a category with Li Reply: 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 Reply?
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.