ericrisco/rsc-harness / skills/linkedin-api
linkedin-api
VerifiedUse 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| evals/README.md | markdown | 726 B |
| evals/cases.yaml | config | 3.1 KB |
| references/api-reference.md | markdown | 5.7 KB |
| scripts/verify.shexecutable | script | 3.6 KB |
evals/cases.yaml
View on GitHubskill: linkedin-api
should_trigger:
- prompt: "Connect our Next.js app to the LinkedIn Posts API and publish to our company page."
why: "Core connector ask — versioned /rest/posts, org author URN, the two required headers. The transport job this skill owns."
- prompt: "We keep getting unauthorized scope w_organization_social when users connect their org page."
why: "Non-obvious: the message is not a typo, it means the Community Management / MDP product is not yet approved. This skill maps the symptom to the product-approval fix."
- prompt: "Pull last month's impressions and engagement for our LinkedIn org posts and save them somewhere we can reference."
why: "Analytics read (organizationalEntityShareStatistics) plus the wiki ingest deliverable under 02-DOCS/wiki/linkedin/."
- prompt: "Migrate our /v2/ugcPosts publishing to the new versioned endpoint."
why: "Non-obvious migration: ugcPosts is deprecated; move to /rest/posts with Linkedin-Version + X-Restli-Protocol-Version."
- prompt: "Conectar la API de LinkedIn y traer las impresiones de los posts."
why: "Spanish; OAuth + share statistics pull — squarely the transport surface this skill owns."
- prompt: "Our publish returns 403 ACCESS_DENIED even though the app has w_organization_social — what's wrong?"
why: "Non-obvious: scope authorizes the app, page role authorizes the person; missing ADMINISTRATOR/CONTENT_ADMIN/DSC role causes the 403."
should_not_trigger:
- prompt: "Write me a punchy LinkedIn post about our launch."
route_to: linkedin-content
why: "Copy and hooks for one post — content meaning, not bytes over HTTP."
- prompt: "Plan our LinkedIn posting cadence and pillars for Q3."
route_to: linkedin-strategy
why: "The plan — what to post and when — not the wire."
- prompt: "Set up an automated DM sequence to new connections."
route_to: linkedin-outreach
why: "The 1:1 layer; this skill is organic publishing and analytics, not messaging."
- prompt: "Build a generic OAuth2 connector scaffold for a REST API I picked."
route_to: api-connector-builder
why: "Arbitrary-provider connector with no LinkedIn specifics; this skill is deep on LinkedIn's endpoints/scopes/URNs."
capability:
- scenario: "Take an app from zero to a logged result: complete 3-legged OAuth, resolve the org author URN, publish a document post (Documents API upload -> document URN -> Posts API), pull organizationalEntityShareStatistics, and write 02-DOCS/wiki/linkedin/<post-id>.md with the metric front-matter."
must_include:
- "sends both required headers: Linkedin-Version and X-Restli-Protocol-Version: 2.0.0"
- "pins version 202605 (not the sunset 202505)"
- "sets lifecycleState: PUBLISHED in the post body"
- "reads the new post URN from the x-restli-id response header"
- "uploads the document via the Documents API to get urn:li:document: then references it in content.media.id"
- "notes share statistics are organic-only over a rolling 12-month window"
- "writes the wiki file with post_urn, captured_at, impressions, and engagement keys"
- "reads token and client_secret from env, never committed to the repo"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |