LinkedIn Skill (Read-Only)
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
, skip to Step 2. If
, install first:
bash
# Install opencli globally
npm install -g @jackwener/opencli
If
, guide the user through setup:
Setup
opencli requires a Chrome browser with the Browser Bridge extension:
- Install the Browser Bridge extension — follow the instructions from output
- Login to linkedin.com in Chrome — opencli reuses your existing browser session
- Verify connectivity:
This auto-starts the daemon, verifies the extension is connected, and checks session health.
Common setup issues
| Symptom | Fix |
|---|
| Install Browser Bridge extension in Chrome and ensure it's enabled |
| Run — it auto-starts the daemon |
No session for linkedin.com
| Login to linkedin.com in Chrome, then retry |
| 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
.
| User Request | Command | Key Flags |
|---|
| Setup check | | — |
| Home feed / posts | opencli linkedin timeline
| |
| Search for jobs | opencli linkedin search "QUERY"
| , , |
| Finance job search | opencli linkedin search "QUERY"
| , , |
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
- Check setup first — run before any other command if unsure about connectivity
- Use or for structured output when processing data programmatically
- Use when the user wants spreadsheet-compatible output
- Use to control result count — start with 10-20 unless the user asks for more
- For job search, use filters — , , , , to narrow results
- NEVER execute write operations — this skill is read-only; do not post, like, comment, connect, message, or apply to jobs
Output format flag ()
| Format | Flag | Best for |
|---|
| Table | (default) | Human-readable terminal output |
| JSON | | Programmatic processing, LLM context |
| YAML | | Structured output, readable |
| Markdown | | Documentation, reports |
| CSV | | Spreadsheet export |
Output columns
Timeline posts include:
,
,
,
,
,
,
,
,
.
Job search results include:
,
,
,
,
,
,
. With
: also
,
.
Step 4: Present the Results
After fetching data, present it clearly for financial research:
- Summarize key content — highlight the most relevant posts or jobs for the user's research
- Include attribution — show author name, headline, post text, and engagement (reactions, comments)
- Provide URLs when the user might want to read the full post or job listing
- For feed posts, highlight market commentary, analyst takes, earnings reactions, and professional sentiment
- For job search results, present title, company, location, salary (when available), and posting date
- Flag sentiment — note bullish/bearish professional sentiment, consensus vs contrarian views
- Treat sessions as private — never expose browser session details
Step 5: Diagnostics
If something isn't working, run:
This checks daemon status, extension connectivity, and browser session health.
Error Reference
| Error | Cause | Fix |
|---|
| Browser Bridge not installed/enabled | Install extension and enable it in Chrome |
| Not logged into linkedin.com | Login to linkedin.com in Chrome |
| LinkedIn login wall detected | Refresh linkedin.com and log in again |
| 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
- — 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.