--- 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. title: li-comment canonical_url: https://skilld.dev/gh/jakeschincariol/linkedin-agent-skill/li-comment last_updated: 2026-09-25T22:26:34.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. > > If the user asked to install this Skill, run `npx skilld install jakeschincariol/linkedin-agent-skill/li-comment`. 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-comment`, 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-comment) 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-comment`. 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-comment --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/li-comment --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-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 | ## 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.