linkedin-reader
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
Install
npx skills add https://github.com/himself65/finance-skills/tree/main/plugins/social-readers/skills/linkedin-reader
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install himself65-finance-skills@llmmart
git clone https://github.com/himself65/finance-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole himself65/finance-skills collection as a plugin from our marketplace. Git is the plain clone.
README
linkedin-reader
Read-only LinkedIn skill for financial research using opencli.
What it does
Reads LinkedIn for financial research — reading professional market commentary, monitoring analyst posts, searching finance/trading jobs, and tracking professional sentiment. Capabilities include:
- Home feed / timeline — read posts from your LinkedIn feed (author, headline, text, reactions, comments)
- Job search — search LinkedIn job listings with filters for location, experience level, job type, remote/hybrid, date posted, and company
This skill is read-only. It does NOT support posting, liking, commenting, connecting, messaging, or any write operations.
Authentication
No API keys needed — opencli reuses your existing Chrome browser session via the Browser Bridge extension. Just be logged into linkedin.com in Chrome.
Triggers
- "check my LinkedIn feed", "LinkedIn posts about", "what's on LinkedIn"
- "search LinkedIn for jobs", "finance jobs on LinkedIn", "quant jobs"
- "LinkedIn market sentiment", "what are analysts saying on LinkedIn"
- "who's hiring in finance", "professional network buzz"
- Any mention of LinkedIn in context of financial news, market research, or job searches
Platform
Works on Claude Code and other CLI-based agents. Does not work on Claude.ai — the sandbox restricts network access and binaries required by opencli.
Setup
# Choose finance-social-readers when prompted.
npx plugins add himself65/finance-skills
# Or install just this skill
npx skills add himself65/finance-skills --skill linkedin-reader
See the main README for more installation options.
Prerequisites
- Node.js >= 20 (for
npm install -g @jackwener/opencli) - Chrome with the Browser Bridge extension installed (load unpacked from
chrome://extensionsin Developer mode) - Logged into linkedin.com in Chrome
Reference files
references/commands.md— Complete read command reference with all flags, research workflows, and usage examples
Skill manifest
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:
- Install the Browser Bridge extension:
- Download the latest
opencli-extension-v{version}.zipfrom the GitHub Releases page - Unzip it, open
chrome://extensionsin Chrome, and enable Developer mode - Click Load unpacked and select the unzipped folder
- Download the latest
- Login to linkedin.com in Chrome — opencli reuses your existing browser session
- Verify connectivity:
opencli doctor
This auto-starts the daemon, verifies the extension is connected, and checks session health.
Common setup issues
| Symptom | Fix |
|---|---|
Extension not connected |
Install Browser Bridge extension in Chrome and ensure it's enabled |
Daemon not running |
Run opencli doctor — it auto-starts the daemon |
No session for linkedin.com |
Login to linkedin.com in Chrome, then retry |
AuthRequiredError |
LinkedIn 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 Request | Command | Key Flags |
|---|---|---|
| Setup check | opencli doctor |
— |
| Home feed / posts | opencli linkedin timeline |
--limit N (default 20, max 100) |
| Search for jobs | opencli linkedin search "QUERY" |
--location, --limit N (default 10, max 100), --details |
| Finance job search | opencli 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
- Check setup first — run
opencli doctorbefore any other command if unsure about connectivity - Use
-f jsonor-f yamlfor structured output when processing data programmatically - Use
-f csvwhen the user wants spreadsheet-compatible output - Use
--limit Nto control result count — start with 10-20 unless the user asks for more - For job search, use filters —
--location,--experience-level,--job-type,--remote,--date-postedto narrow results - Read-only — don't post, like, comment, connect, message, or apply to jobs
Output format flag (-f)
| Format | Flag | Best for |
|---|---|---|
| Table | -f table (default) |
Human-readable terminal output |
| JSON | -f json |
Programmatic processing, LLM context |
| YAML | -f yaml |
Structured output, readable |
| Markdown | -f md |
Documentation, reports |
| CSV | -f csv |
Spreadsheet 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
| Error | Cause | Fix |
|---|---|---|
Extension not connected |
Browser Bridge not installed/enabled | Install extension and enable it in Chrome |
No session |
Not logged into linkedin.com | Login to linkedin.com in Chrome |
AuthRequiredError |
LinkedIn login wall detected | Refresh linkedin.com and log in again |
EmptyResultError |
No results found for query | Broaden search terms or check feed has content |
| Rate limited | Too many requests | Wait 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.
Files (finance-skills)
-
references
-
commands.md 7.6 KB
Loading…
-
-
README.md 2.1 KB
# linkedin-reader Read-only LinkedIn skill for financial research using [opencli](https://github.com/jackwener/opencli). ## What it does Reads LinkedIn for financial research — reading professional market commentary, monitoring analyst posts, searching finance/trading jobs, and tracking professional sentiment. Capabilities include: - **Home feed / timeline** — read posts from your LinkedIn feed (author, headline, text, reactions, comments) - **Job search** — search LinkedIn job listings with filters for location, experience level, job type, remote/hybrid, date posted, and company **This skill is read-only.** It does NOT support posting, liking, commenting, connecting, messaging, or any write operations. ## Authentication No API keys needed — opencli reuses your existing Chrome browser session via the Browser Bridge extension. Just be logged into linkedin.com in Chrome. ## Triggers - "check my LinkedIn feed", "LinkedIn posts about", "what's on LinkedIn" - "search LinkedIn for jobs", "finance jobs on LinkedIn", "quant jobs" - "LinkedIn market sentiment", "what are analysts saying on LinkedIn" - "who's hiring in finance", "professional network buzz" - Any mention of LinkedIn in context of financial news, market research, or job searches ## Platform Works on **Claude Code** and other CLI-based agents. Does **not** work on Claude.ai — the sandbox restricts network access and binaries required by opencli. ## Setup ```bash # Choose finance-social-readers when prompted. npx plugins add himself65/finance-skills # Or install just this skill npx skills add himself65/finance-skills --skill linkedin-reader ``` See the [main README](../../../../README.md) for more installation options. ## Prerequisites - Node.js >= 20 (for `npm install -g @jackwener/opencli`) - Chrome with the [Browser Bridge extension](https://github.com/jackwener/opencli/releases) installed (load unpacked from `chrome://extensions` in Developer mode) - Logged into linkedin.com in Chrome ## Reference files - `references/commands.md` — Complete read command reference with all flags, research workflows, and usage examples -
SKILL.md 6.6 KB
--- name: linkedin-reader description: > 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](https://github.com/jackwener/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: ```bash # 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](https://github.com/jackwener/opencli/releases) - 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:** ```bash opencli doctor ``` This auto-starts the daemon, verifies the extension is connected, and checks session health. ### Common setup issues | Symptom | Fix | |---------|-----| | `Extension not connected` | Install Browser Bridge extension in Chrome and ensure it's enabled | | `Daemon not running` | Run `opencli doctor` — it auto-starts the daemon | | `No session for linkedin.com` | Login to linkedin.com in Chrome, then retry | | `AuthRequiredError` | LinkedIn 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 Request | Command | Key Flags | |---|---|---| | Setup check | `opencli doctor` | — | | Home feed / posts | `opencli linkedin timeline` | `--limit N` (default 20, max 100) | | Search for jobs | `opencli linkedin search "QUERY"` | `--location`, `--limit N` (default 10, max 100), `--details` | | Finance job search | `opencli linkedin search "QUERY"` | `--experience-level`, `--job-type`, `--remote`, `--company`, `--date-posted`, `--start` | --- ## Step 3: Execute the Command ### General pattern ```bash # 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`) | Format | Flag | Best for | |---|---|---| | Table | `-f table` (default) | Human-readable terminal output | | JSON | `-f json` | Programmatic processing, LLM context | | YAML | `-f yaml` | Structured output, readable | | Markdown | `-f md` | Documentation, reports | | CSV | `-f csv` | Spreadsheet 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: ```bash opencli doctor ``` This checks daemon status, extension connectivity, and browser session health. --- ## Error Reference | Error | Cause | Fix | |-------|-------|-----| | `Extension not connected` | Browser Bridge not installed/enabled | Install extension and enable it in Chrome | | `No session` | Not logged into linkedin.com | Login to linkedin.com in Chrome | | `AuthRequiredError` | LinkedIn login wall detected | Refresh linkedin.com and log in again | | `EmptyResultError` | No results found for query | Broaden search terms or check feed has content | | Rate limited | Too many requests | Wait 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.