skills/linkedin/SKILL.md
Manage your LinkedIn via the official API — create posts, fetch your profile, and draft copy for bio/experience edits. Use when user wants to post to LinkedIn, share an update, check their LinkedIn identity, or revise their profile/headline/about.
npx skillsauth add RonanCodes/ronan-skills linkedinInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Official LinkedIn API (OAuth 2.0) for creating posts from your personal profile. Profile-section edits (bio, experience, jobs) have no public write API — handled in draft-only mode: the skill generates the copy, copies it to clipboard, and opens the LinkedIn edit UI for you to paste + save.
/ro:linkedin auth # one-time OAuth (token lasts ~60 days)
/ro:linkedin post "Hello LinkedIn 👋" # publish a text post to your feed
/ro:linkedin me # show profile identity (userinfo)
/ro:linkedin draft about "New about-section copy..." # draft-edit mode: clipboard + open editor
/ro:linkedin draft headline "Staff Engineer @ ..."
/ro:linkedin draft experience # just open the add-position form
| Arg | Script |
|-----|--------|
| auth | scripts/auth.py |
| post <text> | scripts/post.sh |
| me | scripts/me.sh |
| draft <section> [text] | scripts/draft-edit.sh |
Pass all trailing args through verbatim.
http://localhost:8765/callback~/.claude/.env:
LINKEDIN_CLIENT_ID=...
LINKEDIN_CLIENT_SECRET=...
Then chmod 600 ~/.claude/.env./ro:linkedin auth — browser opens, you approve, token is written back to ~/.claude/.env.The access token lasts ~60 days. post / me warn when <7 days remain and fail hard when expired — re-run auth to refresh.
/ro:linkedin-voyager profile <slug> (ToS-grey).draft mode is the answer: the skill generates the copy, pbcopys it, and opens the right LinkedIn form URL. You paste + save.w_organization_social scope + an org URN. Not wired. Ask to extend.w_member_social scope. LinkedIn restricts these to partners. Use the paid linkedin-cli (Linked API) if you need them.~/.claude/.env (mode 0600). Never committed.auth.py only binds to localhost and validates the OAuth state parameter.See reference.md for: OAuth flow internals, /rest/posts request shape, error codes, scope reference, and how to extend for company pages.
ro:linkedin-scan — read-only LinkedIn scraper (light, public-facing HTML).ro:linkedin-voyager — ToS-grey sibling: reads bio/experience/full profile via the unofficial Voyager API using browser cookies. Use when the official API can't give you what you need. Ban risk — see its SKILL.md.ro:browser-cookies — shared cookie extractor used by scan + voyager.ro:write-copy — apply style rules before drafting a post or about section.development
Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
devops
Run a night-shift against a collaborator's Linear board. Pulls the team's Grilled tickets (/ro:linear-grill moves a ticket to Grilled once its questions are answered), VERIFIES the questions were actually answered (unanswered → bounce the ticket to the "Question for <name>" state), mirrors verified tickets to ephemeral GitHub issues with ready-for-agent, then runs the standard /ro:night-shift machinery on GitHub. Tail-calls /ro:linear-update for everything that merged + deployed. Triggers on "linear nightshift", "nightshift linear", "drain the linear board", "run the shift off linear", "/ro:linear-nightshift".
development
Grill a collaborator's Linear tickets and move every processed ticket to where it belongs. Resolves the board from the repo's .ro-linear.json, reads the collaborator's Backlog / Ready-for-agent issues, then per ticket either posts 3-5 decision-extracting questions (state moves to "Question for <name>") or confirms it build-ready (state moves to "Grilled", the gate /ro:linear-nightshift consumes); shipped-and-confirmed tickets close as Done. The async-collaborator counterpart of /ro:day-shift for people who never touch GitHub. Triggers on "grill linear", "grill eoin's tickets", "linear grill", "add questions to the linear tickets", "/ro:linear-grill".
development
--- name: about-page description: Add a standard About page to any web app, what it is, the tech stack, and an FAQ, wired into a footer link with a sticky footer. Built with Spartan + Tailwind (the canonical component layer) and falls back to semantic HTML so it ships reliably. Use whenever building, polishing, or shipping an app, every app should have one. Triggers on "add an about page", "about page", "footer about link", or as a standard step in app build/polish. category: frontend argument-h