linkedin-reply-handler SKILL.md skillA
linkedin-reply-handler from sylvan-io/linkedin-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sylvan-io/linkedin-skills/linkedin-reply-handler@git:20261117.60125ffPins git:20261117.60125ff in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sylvan-io/linkedin-skills
- Path
skills/linkedin-reply-handler/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261117.60125ff, committed Nov 17, 2026
- First version recorded
- Oct 10, 2026
- Size
- 27,699 bytes
- Repository stars
- 2
- License
- MIT
Reply to one LinkedIn comment, sweep a whole comment thread in one batch, or reply to a LinkedIn DM with conversation history as context. Use for answering a comment, following an author reply, clearing comments on a post, or continuing a direct-message thread. Handles 2-level thread flattening, filters low-value comments, archives DMs with dedup, and delivers approved drafts as copy-paste blocks for manual posting. Not for top-level comments (use linkedin-comment-drafter).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# LinkedIn Reply Handler Drafts a reply in one of three modes: (1) a reply to a specific LinkedIn comment, (2) a sweep of an entire comment thread (every top-level comment and its replies) with a draft for each one worth answering, or (3) a reply to a LinkedIn direct message (DM) grounded in the full archived conversation history. Both comment modes correctly handle LinkedIn's 2-level thread flattening: if you're replying to a reply, the reply should attach to the TOP-level comment, not the reply. DM mode archives the thread to a per-connection file first, then drafts a message that matches the live conversation. > **Project stores:** Use `CONNECTIONS_DIR`, `STORY_BANK_FILE`, `VOICE_PROFILE_FILE`, and `OUTREACH_DIR` as resolved by root `SKILL.md` §Project configuration. When this file is used standalone, resolve `<project-root>/AGENT.md` the same way; without it, use the documented defaults. ## When to use **Single comment:** - User pastes a LinkedIn comment (text or screenshot, ideally with its permalink) and says "reply to this" - An author replied to the user's comment and the user wants to continue the thread - User wants to re-engage a conversation that's gone dormant …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xrjk2fzorx4laeob/f2447c27f5b23e80f96c187136c4abebbf5f08dc0accaeb8bef1bc3cbba15607.json
Then /plugin install linkedin-reply-handler@markdownregistry-xrjk2fzorx4laeob in Claude Code. It installs git:20261117.60125ff, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add sylvan-io/linkedin-skills/linkedin-reply-handler@sha256:f2447c27f5b23e80The line at the top of this page pins the label git:20261117.60125ff, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xrjk2fzorx4laeob)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in sylvan-io/linkedin-skills/linkedin-reply-handler since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of linkedin-reply-handler from somewhere else? Ask it: where did my linkedin-reply-handler come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 10, 2026 and Nov 17, 2026, about one every 10 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.60125ff latest | 2026-11-17 | 60125ff | 27,699 B | A | view · diff |
| git:20261117.a87fbf5 | 2026-11-17 | a87fbf5 | 25,772 B | A | view · diff |
| git:20261010.c865ff8 | 2026-10-10 | c865ff8 | 25,660 B | A | view · diff |
| git:20261010.305a2b7 | 2026-10-10 | 305a2b7 | 25,201 B | A | view · diff |
| git:20261010.d5d24bf | 2026-10-10 | d5d24bf | 23,837 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/linkedin-reply-handler/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (27699 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sylvan-io/linkedin-skills · 2 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xrjk2fzorx4laeob GET https://markdownregistry.com/api/v1/resolve?ref=sylvan-io/linkedin-skills/linkedin-reply-handler GET https://markdownregistry.com/api/v1/blob/f2447c27f5b23e80f96c187136c4abebbf5f08dc0accaeb8bef1bc3cbba15607
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sylvan-io/linkedin-skills
Every file in sylvan-io/linkedin-skills