linkedin-content SKILL.md skillA
linkedin-content from ericrisco/rsc-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ericrisco/rsc-harness/linkedin-content@git:20261011.c7821cdPins git:20261011.c7821cd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ericrisco/rsc-harness
- Path
skills/linkedin-content/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261011.c7821cd, committed Oct 11, 2026
- First version recorded
- Jun 2, 2026
- Size
- 16,112 bytes
- Repository stars
- 236
- License
- MIT
Use when writing the actual words of one LinkedIn feed post — turning a raw idea, story or asset into ready-to-paste copy: a text post, a document/carousel cover with slide copy and caption, or a short native-video script. Covers fixing a weak hook, reformatting a wall of text for the mobile feed, and a CTA that provokes a real comment. NOT planning what or when to post (that is `linkedin-strategy`), NOT designing the carousel slides and PDF export (that is `linkedin-carousels`), NOT DM…
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 Content — The Words a Human Pastes Into the Feed *You write the copy of one LinkedIn post.* You take a raw idea, a story, or an asset and turn it into finished text the user pastes straight into the composer. You do not pick the topic or the day, you do not design the carousel pixels, you do not write DMs, and you do not call the API. You hand over words. **The one rule that governs every line: the 2026 algorithm pays for dwell time and comments, not likes or clicks.** That dwell drives ranking is not a marketing claim — LinkedIn's own engineering team documents it: they train a "Long Dwell" classifier and feed per-post dwell into the ranking model precisely because dwell captures the passive readers that likes miss (LinkedIn Engineering, "Leveraging Dwell Time to Improve Member Experiences on the LinkedIn Feed", Oct 2024 — [S1]). The *size* of the gap is reported by practitioner analyses, not LinkedIn: posts with 0–3s dwell are reported to average ~1.2% engagement vs. ~15.6% at 61+s, a ~13x gap ([S2], corroborated by [S3]). Treat the mechanism as solid and the multiplier as directional. A 30-second read beats 50 quick likes. So every line you write has exactly one… …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/linkedin-content@sha256:9c1aedbc3f5bef1bThe line at the top of this page pins the label git:20261011.c7821cd, 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_wymeclturrnaupc4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 2, 2026 and Oct 11, 2026, about one every 66 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.c7821cd latest | 2026-10-11 | c7821cd | 16,112 B | A | view · diff |
| git:20260729.80bd629 | 2026-07-29 | 80bd629 | 15,520 B | A | view · diff |
| git:20260602.d5540f8 | 2026-06-02 | d5540f8 | 15,949 B | A | view |
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 (16112 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
ericrisco/rsc-harness · 236 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wymeclturrnaupc4 GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/linkedin-content GET https://markdownregistry.com/api/v1/blob/9c1aedbc3f5bef1b5ce13d9479b1c3a29f3d4e52e133e61fa55bb0e653af5331
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 ericrisco/rsc-harness
Every file in ericrisco/rsc-harness