linkedin-api SKILL.md skillA
linkedin-api 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-api@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-api/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260729.80bd629, committed Jul 29, 2026
- First version recorded
- Jun 2, 2026
- Size
- 11,813 bytes
- Repository stars
- 236
- License
- MIT
Use when wiring an app to LinkedIn's organic Posts / Community Management API — 3-legged OAuth, publishing text, article or document posts to a member profile or company page, and pulling impressions, engagement and follower stats into a durable feedback record. NOT writing the post copy (that is `linkedin-content`), NOT planning cadence (that is `linkedin-strategy`), NOT DM sequences (that is `linkedin-outreach`).
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 API: publish and pull analytics over the wire You own the **transport**. Auth headers, scopes, URNs, request shapes, rate-limit handling, token refresh, and the write that turns post performance into a durable feedback log. You do **not** decide what to post or why. **Decision line:** if the question is *which HTTP call, which header, which scope, which URN, how do I store the numbers* → you. If it is about the *meaning* of the content → a sibling. - Words, hooks, CTA for one post → `linkedin-content` (planned sibling). - Cadence, pillars, audience plan → `linkedin-strategy` (planned sibling). - The multi-slide PDF artifact → `linkedin-carousels` (planned sibling) builds it; you only upload the resulting document URN. - DMs, connection requests, sequences → `linkedin-outreach` (planned sibling). - Generic OAuth2 / webhook scaffolding with no LinkedIn specifics → `../api-connector-builder/SKILL.md`, `../webhooks/SKILL.md`. ## Prereqs: app + products + scopes You configure this on the LinkedIn Developer portal once, before any code runs. 1. Create a developer app, associate it with a company page (required to request org products). …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/linkedin-api@sha256:f323ea9d7e8d992fThe 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_nclousvcr62vxm2o)
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 | 11,813 B | A | view · diff |
| git:20260628.e37ed23 | 2026-06-28 | e37ed23 | 12,200 B | A | view · diff |
| git:20260602.d5540f8 | 2026-06-02 | d5540f8 | 11,417 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 (11813 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_nclousvcr62vxm2o GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/linkedin-api GET https://markdownregistry.com/api/v1/blob/f323ea9d7e8d992fc47b539f736ee0c1159664319aec5f4884f5965c4d4533c8
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.