linkedin-strategy SKILL.md skillA
linkedin-strategy 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-strategy@git:20260729.80bd629Pins git:20260729.80bd629 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-strategy/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260729.80bd629, committed Jul 29, 2026
- First version recorded
- Jun 2, 2026
- Size
- 13,266 bytes
- Repository stars
- 236
- License
- MIT
Use when a LinkedIn presence — personal brand or company page — needs an account-level decision spanning months: positioning and point of view, three to five content pillars, posting cadence, whether content lives on the founder's profile or the company page, and the social-selling rhythm, read from and written back to the presence's own learning wiki. NOT writing the post copy or hook (that is `linkedin-content`), NOT building a carousel deck (that is `linkedin-carousels`), NOT sending DMs…
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 Strategy — The Presence as a System, Not the Next Post *You operate at account/presence altitude.* You decide the **territory** (what this presence is known for, who it is for) and the **system** (pillars, cadence, where content lives, the social-selling rhythm) over months. You never write the post, build the carousel, run the DMs, or hit the API — those are single-asset jobs you route out. Mixing altitudes is the #1 reason LinkedIn advice goes generic: an account-level question answered with a tactic about one post produces noise and regresses to blog-post defaults. Your spine is a read/write loop with the presence's own history. You **read** the accumulated learnings before deciding and **write** the decision back, so the next session compounds instead of restarting from a generic "post 3 times a week" template. ## Altitude boundary — route single-asset work out | The ask | Skill | Why it is not you | |---|---|---| | Post copy, hook, body for one update | `../linkedin-content/SKILL.md` | You set the pillar and POV; content writes inside it. | | A carousel / document-post deck | `../linkedin-carousels/SKILL.md` | A single asset's format craft, not the system. | …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/linkedin-strategy@sha256:4a651967196a7d4aThe line at the top of this page pins the label git:20260729.80bd629, 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_tmrkhng67us77xk2)
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 Jul 29, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260729.80bd629 latest | 2026-07-29 | 80bd629 | 13,266 B | A | view · diff |
| git:20260628.e37ed23 | 2026-06-28 | e37ed23 | 13,679 B | A | view · diff |
| git:20260602.d5540f8 | 2026-06-02 | d5540f8 | 13,170 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 (13266 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_tmrkhng67us77xk2 GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/linkedin-strategy GET https://markdownregistry.com/api/v1/blob/4a651967196a7d4a6dc69c084c66fb208837fadbb6a80e490d689bafae8ff77a
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.