skills/linkedin-scan/SKILL.md
Scan LinkedIn posts for a URL or pasted content, or fetch recent posts by a person/company. Uses cookie auth via browser-cookies (Firefox/Brave/Chrome/Arc) when available, otherwise pasted-text fallback. Returns findings without vault persistence. Sibling to llm-wiki/ingest-linkedin.
npx skillsauth add RonanCodes/ronan-skills linkedin-scanInstall 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.
Pull LinkedIn post(s) and return distilled findings. No file writes.
LinkedIn is unfriendly to scrapers (auth wall, HTML churn, anti-bot). Expect pasted-text mode to be the most reliable path.
/ro:linkedin-scan https://www.linkedin.com/posts/someone-activity-xxxx # one post, cookie auth
/ro:linkedin-scan paste # caller will paste post text
/ro:linkedin-scan @satya-nadella --limit 10 # recent posts by slug (cookie auth)
http → URL mode (cookie auth)paste or empty → prompt caller to paste the post, then parse@ → profile feed mode (cookie auth)linkedin.com via the browser-cookies skill (falls back to firefox-cookies if browser-cookies isn't available)curl -sL \
-H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36" \
-H "$COOKIE_HEADER" \
"<linkedin-url>"
<script type="application/ld+json">...</script> — look for articleBody / textfeed-shared-update-v2__description divsfeed-shared-actor__name span for author, feed-shared-actor__sub-description for headline/ro:linkedin-scan paste instead.Prompt:
Paste the LinkedIn post text. Include the author name on the first line if possible. End with an empty line.
Parse the pasted content:
#hashtags → tags@slug)Same cookie-auth flow as URL mode, hitting https://www.linkedin.com/in/{slug}/recent-activity/all/. Parse the first N posts. Very brittle — LinkedIn's feed markup changes often. If it breaks, tell the caller to open the profile in Firefox and copy-paste the top few posts.
# LinkedIn scan: <target> (<N> results)
1. <Author Name> — <headline if known> (<time ago>)
<post text, trimmed to ~500 chars with "..." if truncated>
Tags: #foo #bar
<linkedin-url if derivable>
2. ...
Never echo back cookie values or session tokens in output.
curl — alwaysbrowser-cookies skill — required for URL / profile-feed modes (or legacy firefox-cookies for Firefox-only setups)llm-wiki/.claude/skills/ingest-linkedin — persists LinkedIn posts into a vault with full YAML frontmatter and wiki source-notes. Use when you want to keep the content./ro:trend-scan — orchestrator./ro:hn-scan, /ro:x-scan, /ro:reddit-scan — other source scanners.browser-cookies — cookie extraction (current); firefox-cookies — legacy Firefox-only fallback./ro:linkedin — write path (official API: posts + draft-mode edits)./ro:linkedin-voyager — ToS-grey read path via unofficial Voyager API (bio, experience, full profile).development
--- name: worktree description: Coordinate multiple agents on one repo via a worktree-lock pool, so two agents never clobber each other's working tree. Acquire the first free slot (main, then beta/gamma… worktrees, created on demand), work there on your own branch, release when you've pushed. Use before modifying any repo that might be in use by another agent (factory, dataforce, etc.), or whenever you're told a repo is being worked on. Backed by `ro worktree`. category: development argument-hin
testing
--- name: ship description: Ship a feature branch the local-CI-first way — run the full local gate, push, open a PR, squash-merge, then deploy, without waiting on GitHub Actions. Use when a branch is ready for main and you want it merged and deployed now. Reads CI policy from `ro ci` (default skips remote CI because GitHub Actions billing keeps hitting limits). Sibling to /ro:gh-ship (waits on GitHub checks) and /ro:cf-ship (the deploy half). Triggers on "ship it", "ship this", "merge and deploy
testing
--- name: setup-logging description: Set up (or audit) the observability stack in a TanStack Start + Cloudflare Workers app so it is "diagnosable by default" — structured logging (logtape) with a request context carrying trace_id + userId + tenant/orgId, a trace_id propagated FE→BE→logs→Sentry→PostHog, Cloudflare Workers observability enabled, and Sentry + PostHog wired. Two modes: `setup` (wire it into an app) and `audit` (check an existing app + report gaps). Use when scaffolding a new app, wh
development
Manage credentials INSIDE the active ~/.claude/.env file — read which token/account to use for a given app (Simplicity vs Dataforce vs Ronan-personal), add or update a secret WITHOUT it passing through the chat (an interactive Terminal window prompts for it), and track secrets that were exposed in a transcript so they get rotated. Sibling to /ro:context (which switches WHICH env file is active). Use when the user wants to add an API key/token/secret, asks "which credential do I use for X", needs the env organized/labelled, or a secret was pasted into the chat and should be rotated.