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 comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
Install Li Comment
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-comment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-comment --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-comment .claude/skills/li-comment && 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-comment" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-comment into .claude/skills/li-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-comment", 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-commentType 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-comment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-comment --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-comment .agents/skills/li-comment && 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-comment" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-comment into .agents/skills/li-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-comment", 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-comment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-comment --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-comment .cursor/skills/li-comment && 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-comment" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-comment into .cursor/skills/li-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-comment", 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-comment--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-comment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-comment --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-comment .gemini/skills/li-comment && 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-comment" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-comment into .gemini/skills/li-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-comment", 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-commentInstalls 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-comment -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-comment .github/skills/li-comment && 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-comment" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-comment into .github/skills/li-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-comment", 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-comment -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-comment --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-comment .opencode/skills/li-comment && 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-comment" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-comment into .opencode/skills/li-comment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-comment", 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-comment- GitHub stars
- 1.6k
- Token cost
- ~1k tokens
- SKILL.md length
- 543 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
- The user pastes a post and wants a comment
- SKILL.md covers Input, The nine comment types, Rules and Output, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Says comment on this
What it does
Li Comment is an agent skill from Jakeschincariol/linkedin-agent-skill. Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot. Use when the user pastes a post and wants a comment, says "comment on this", "engage with this", "what do I say here", or wants a batch of comments for their engagement round.
Its SKILL.md is about 1k 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. 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 pastes a post and wants a comment
- Says comment on this
- Engage with this
- What do I say here
Example prompts
- “comment on this”
- “engage with this”
- “what do I say here”
- “/li-comment”
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 Comment loads about 1k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 543 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). 543 words, ~1,039 tokens.
Download SKILL.mdSave it as
.claude/skills/li-comment/SKILL.md (or your agent's skills folder).- name
- li-comment
- description
- Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot. Use when the user pastes a post and wants a comment, says "comment on this", "engage with this", "what do I say here", or wants a batch of comments for their engagement round.
li-comment
Commenting is the highest-leverage thing on LinkedIn and the easiest to do badly. A comment on a post with 400 reactions gets seen by more people than most of your own posts. A generic one gets seen by nobody and costs you credibility with the author.
Input
The user pastes the post text (and the author's name and role if they have it). If they paste a screenshot, read it. If they give you a URL you cannot open, ask them to paste the text - do not guess what the post said, and do not use browser automation to scrape the feed.
The nine comment types
Pick by what the post actually is. Never default to type 1.
| # | type | when | shape |
|---|---|---|---|
| 1 | Add a datum | post makes a claim you can support with a number | "We saw the same thing: 40% of our..." |
| 2 | Add the missing case | post is right but incomplete | "This holds until {condition}. Then..." |
| 3 | Respectful disagree | you genuinely think it is wrong | name the agreement first, then the fork |
| 4 | Extend one line | one sentence in the post is the good one | quote it, then build on it |
| 5 | Ask the real question | post skipped the hard part | one question, specific, no "curious to hear" |
| 6 | The receipt | you have done the thing they described | what happened, in two sentences |
| 7 | The correction | there is a factual error | be right, be brief, be kind, be sure |
| 8 | The reframe | the post has the right facts and the wrong frame | "Another way to read this:" |
| 9 | The one-liner | the post needs nothing, you want presence | under 12 words, must be funny or true |
Show full SKILL.md (265 more words)Show less
Rules
- 2 to 4 sentences. Longer reads as a hijack. Shorter reads as filler.
- Never open with "Great post", "Love this", "So true", "Couldn't agree more", "This resonates", or the author's first name followed by an exclamation mark. All six are invisible.
- No emoji openers. No 🔥 or 👏 as a first character.
- Never restate the post. The author knows what they wrote and so does everyone reading.
- One idea. A comment with two points reads as a blog attempt.
- Say the specific thing. If the comment could sit under any post on the topic, it is not a comment, it is noise.
- Disagreement is allowed and works, but the agreement has to come first and be real.
Output
Give two options of different types, labelled, plus a one-line reason for
the one you would post. Run both through /li-human first - a comment with an
em dash in it is more obviously machine-written than a post, because comments
are short and people read them closely.
COMMENT OPTIONS (on @author's post about hiring)
[6 · Receipt]
We tried the no-resume version of this for 3 hires last year. Two were the
best hires we made. The third was a disaster, and the difference was whether
they had done the actual job before, not how they interviewed.
[3 · Respectful disagree]
Agree on the signal problem. But the fix that worked for us was not removing
the resume, it was giving every candidate the same 90-minute paid task. Same
outcome, far less argument internally.
Post the first. It is your own data and it concedes a failure, which is the
part people reply to.Batch mode
If the user wants an engagement round, ask for the 5-10 posts as pasted text
in one message, return one comment each in a single block, and keep a running
note of who they have already commented on this week in
~/.claude/linkedin/log.md. Commenting on the same three people every day is
visible and it looks like what it is.
Never
Do not auto-post. Do not use a browser tool to publish comments on the user's behalf. Automated posting and scraping both violate LinkedIn's User Agreement and put the account at risk. This skill writes the comment. The user posts it.
© 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-comment of Jakeschincariol/linkedin-agent-skill.
Open the folder on GitHubat commit add2c23
Compare with similar skills
Li Comment 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 Comment this skillJakeschincariol/linkedin-agent-skill | 1.6k | — | ~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 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.
Li Plan
Jakeschincariol/linkedin-agent-skill
Build the week on LinkedIn - what to post, when to post it, and who to engage with.
Related
Works with
Categories
Questions about Li Comment
What does Li Comment do?
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot. Li Comment is an agent skill from Jakeschincariol/linkedin-agent-skill. Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
When should I use Li Comment?
Li Comment fits situations like: the user pastes a post and wants a comment; says comment on this; engage with this; what do I say here.
How do I install Li Comment in Claude Code?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-comment -a claude-code`. Or copy the skill folder (skills/li-comment in Jakeschincariol/linkedin-agent-skill) into .claude/skills/li-comment in your project. Claude Code loads it when a task matches its description.
How do I install Li Comment in Codex?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-comment -a codex`. Or copy the skill folder (skills/li-comment in Jakeschincariol/linkedin-agent-skill) into .agents/skills/li-comment in your project. Codex loads it when a task matches its description.
Can I use Li Comment 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-comment -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-comment, .gemini/skills/li-comment, .github/skills/li-comment and .opencode/skills/li-comment in your project.
What does Li Comment need to run?
SKILL.md names no scripts, command-line tools or credentials: Li Comment is instructions for the agent only.
Does Li Comment 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 Comment 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 Comment use?
Li Comment 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 Comment use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Comment?
Skills that share tags, products or a category with Li Comment: 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 Comment?
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.