Menu
LinkedIn integration for reading feed, profiles, connections, search results, and messages using browser automation
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | |
| description | LinkedIn integration for reading feed, profiles, connections, search results, and messages using browser automation |
| version | 0.2.0 |
| tools | ["Bash","mcp__claude-in-chrome__tabs_context_mcp","mcp__claude-in-chrome__navigate","mcp__claude-in-chrome__read_page","mcp__claude-in-chrome__computer","mcp__claude-in-chrome__find"] |
| alwaysApply | false |
Access LinkedIn data through browser automation. This approach is reliable because it uses your actual browser session, avoiding LinkedIn's aggressive bot detection that blocks API-only traffic.
Create a dedicated Chrome profile for automation:
In your automation profile:
Before using LinkedIn commands:
When the user asks for LinkedIn data, use the claude-in-chrome tools to navigate and extract information.
Always start by checking the browser connection:
1. Call mcp__claude-in-chrome__tabs_context_mcp with createIfEmpty: true
2. If not connected, ask user to open Chrome with their automation profile
3. Create a new tab or use existing one
When user asks to see their LinkedIn feed:
1. Navigate to https://www.linkedin.com/feed/
2. Use read_page to extract feed content
3. Parse and format the feed items
Example flow:
mcp__claude-in-chrome__navigate to https://www.linkedin.com/feed/mcp__claude-in-chrome__read_page with filter: "all" to get post contentWhen user asks about a LinkedIn profile:
1. Navigate to https://www.linkedin.com/in/{username}/
2. Use read_page to extract profile information
3. Parse name, headline, about, experience, etc.
When user wants to search LinkedIn:
People: https://www.linkedin.com/search/results/people/?keywords={query}
Jobs: https://www.linkedin.com/search/results/jobs/?keywords={query}
Companies: https://www.linkedin.com/search/results/companies/?keywords={query}
Posts: https://www.linkedin.com/search/results/content/?keywords={query}
When user wants to check messages:
1. Navigate to https://www.linkedin.com/messaging/
2. Use read_page to extract conversation list
3. Click on a conversation to read messages
Look for these patterns in the accessibility tree:
Navigate to profile and extract:
Parse result items containing:
1. Connect to Chrome: tabs_context_mcp
2. Navigate: navigate to linkedin.com/feed/
3. Wait for load: computer action=wait duration=2
4. Read content: read_page with depth=10
5. Parse and summarize top posts
1. Connect to Chrome: tabs_context_mcp
2. Navigate: navigate to linkedin.com/search/results/people/?keywords=John%20Smith
3. Read results: read_page filter=interactive
4. Present matching profiles
1. Connect to Chrome: tabs_context_mcp
2. Navigate: navigate to linkedin.com/in/me/
3. Read profile: read_page
4. Summarize profile stats, recent activity
The CLI tool is available but LinkedIn often invalidates API sessions:
# Install
cd /Users/derekrein/Code/cyberdrk305/linkedin && npm install && npm run build && npm link
# Commands (may require fresh cookies frequently)
linkedin setup # Setup instructions
linkedin check # Verify credentials
linkedin whoami # Show logged-in user
linkedin feed -n 10 # Get feed posts
linkedin profile <username> # View profile
If using the CLI, you'll need to manually extract cookies:
li_at and JSESSIONID valueslinkedin setup --li-at "VALUE" --jsessionid "VALUE"Note: LinkedIn aggressively invalidates these sessions after a few API calls.