Skip to content

himself65/finance-skills / plugins/social-readers/skills/linkedin-reader

linkedin-reader

Unverified

Read LinkedIn for financial research through opencli: the user's feed, and job search with location, seniority, job type, remote, company, and date filters. Use this skill whenever the user wants to check their LinkedIn feed, see what professionals or analysts are posting about a company, market, or earnings, gauge professional sentiment, or search finance and trading jobs on LinkedIn. Read-only: it cannot post, like, comment, connect, message, or apply.

LinkedIn Skill (Read-Only)

If your host has not already executed the shell probes below (for example, in Codex), run the commands inside the ! wrappers with its shell tool before choosing a setup path. Use the actual output; if shell access is unavailable, report that limitation.

Reads LinkedIn for financial research using opencli, a universal CLI tool that bridges web services to the terminal via browser session reuse.

This skill is read-only. It is designed for financial research: reading professional commentary on markets, monitoring analyst posts, searching finance/trading jobs, and tracking professional sentiment. It does NOT support posting, liking, commenting, connecting, messaging, or any write operations.

Important: opencli reuses your existing Chrome login session — no API keys or cookie extraction needed. Just be logged into linkedin.com in Chrome and have the Browser Bridge extension installed.


Step 1: Ensure opencli Is Installed and Ready

Current environment status:

!`(command -v opencli && opencli doctor 2>&1 | head -5 && echo "READY" || echo "SETUP_NEEDED") 2>/dev/null || echo "NOT_INSTALLED"`

If the status above shows READY, skip to Step 2. If NOT_INSTALLED, install first:

# Install opencli globally
npm install -g @jackwener/opencli

If SETUP_NEEDED, guide the user through setup:

Setup

opencli requires Node.js >= 20 and a Chrome browser with the Browser Bridge extension:

  1. Install the Browser Bridge extension:
    • Download the latest opencli-extension-v{version}.zip from the GitHub Releases page
    • Unzip it, open chrome://extensions in Chrome, and enable Developer mode
    • Click Load unpacked and select the unzipped folder
  2. Login to linkedin.com in Chrome — opencli reuses your existing browser session
  3. Verify connectivity:
opencli doctor

This auto-starts the daemon, verifies the extension is connected, and checks session health.

Common setup issues

SymptomFix
Extension not connectedInstall Browser Bridge extension in Chrome and ensure it's enabled
Daemon not runningRun opencli doctor — it auto-starts the daemon
No session for linkedin.comLogin to linkedin.com in Chrome, then retry
AuthRequiredErrorLinkedIn session expired — refresh linkedin.com in Chrome and log in again

Step 2: Identify What the User Needs

Match the user's request to one of the read commands below, then use the corresponding command from references/commands.md.

User RequestCommandKey Flags
Setup checkopencli doctor—
Home feed / postsopencli linkedin timeline--limit N (default 20, max 100)
Search for jobsopencli linkedin search "QUERY"--location, --limit N (default 10, max 100), --details
Finance job searchopencli linkedin search "QUERY"--experience-level, --job-type, --remote, --company, --date-posted, --start

Step 3: Execute the Command

General pattern

# Read LinkedIn feed posts
opencli linkedin timeline --limit 20 -f json

# Search for finance/trading jobs
opencli linkedin search "quantitative analyst" --limit 10 -f json
opencli linkedin search "portfolio manager" --location "New York" --limit 15 -f json

# Detailed job listings with descriptions
opencli linkedin search "financial analyst" --details --limit 10 -f json

Key rules

  1. Check setup first — run opencli doctor before any other command if unsure about connectivity
  2. Use -f json or -f yaml for structured output when processing data programmatically
  3. Use -f csv when the user wants spreadsheet-compatible output
  4. Use --limit N to control result count — start with 10-20 unless the user asks for more
  5. For job search, use filters — --location, --experience-level, --job-type, --remote, --date-posted to narrow results
  6. Read-only — don't post, like, comment, connect, message, or apply to jobs

Output format flag (-f)

FormatFlagBest for
Table-f table (default)Human-readable terminal output
JSON-f jsonProgrammatic processing, LLM context
YAML-f yamlStructured output, readable
Markdown-f mdDocumentation, reports
CSV-f csvSpreadsheet export

Output columns

Timeline posts include: rank, author, author_url, headline, text, posted_at, reactions, comments, url.

Job search results include: rank, title, company, location, listed, salary, url. With --details: also description, apply_url.


Step 4: Present the Results

Lead with what matters for the user's research question rather than a raw dump. For feed posts, attribute each one (author, headline, text, reactions and comments, URL), highlight market commentary, analyst takes, and earnings reactions, and note the bullish or bearish lean and where views are consensus or contrarian. For job results, give title, company, location, salary when available, posting date, and the listing URL. Keep browser session details private.


Step 5: Diagnostics

If something isn't working, run:

opencli doctor

This checks daemon status, extension connectivity, and browser session health.


Error Reference

ErrorCauseFix
Extension not connectedBrowser Bridge not installed/enabledInstall extension and enable it in Chrome
No sessionNot logged into linkedin.comLogin to linkedin.com in Chrome
AuthRequiredErrorLinkedIn login wall detectedRefresh linkedin.com and log in again
EmptyResultErrorNo results found for queryBroaden search terms or check feed has content
Rate limitedToo many requestsWait a few minutes, then retry

Reference Files

  • references/commands.md — Complete read command reference with all flags, research workflows, and usage examples

Read the reference file when you need exact command syntax, research workflow patterns, or output details.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall