Claude LinkedIn Assistant plugin
A Claude Code workspace that tracks jobs, finds roles and sends first messages to 1st-degree LinkedIn connections
- 235 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent drives your browser with an active LinkedIn sign-in and sends messages and connection requests in your name
- Reads a resume with personal data and keeps a contact log on disk
- Automated messages may break LinkedIn's rules and lead to an account restriction
Install
- Works in
Manual install
git clone https://github.com/FarzamHejaziK/claude-linkedin-assistant.gitThen put a resume into resumes/, open the folder in the Claude Code desktop app and run /jobs setup. The Claude in Chrome extension is required.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent drives your browser with an active LinkedIn sign-in and sends messages and connection requests in your name
- Reads a resume with personal data and keeps a contact log on disk
- Automated messages may break LinkedIn's rules and lead to an account restriction
This is third-party code. Review the repository files before installing.
What it does
This is a minimal Claude Code workspace where all the logic lives in `/jobs` slash commands. You drop a resume into `resumes/`, and Claude takes the name, target roles, skills and a short pitch from it. An optional `resumes/search_profile.md` states preferences: must-haves, deal-breakers, interest areas, a salary floor. State lives in a `job_tracker.csv` table. Before any command Claude opens Chrome through the Claude in Chrome extension and checks that LinkedIn is signed in under the name on the resume. After that it drives the browser like a person: searches ordinary LinkedIn URLs, opens profiles in tabs and types messages into the real chat. It uses no private LinkedIn API for this. `/jobs find` searches LinkedIn, the web and optionally Indeed, scores results and adds them to the tracker. `/jobs check` shows a dashboard of what is pending and what is stale. `/jobs outreach <Company>` counts 1st-degree contacts at the company and sends them a first message, while requests to 2nd-degree contacts go without a note to conserve the monthly quota of personalized invites. `/jobs daily` runs the whole chain and makes one Git commit. Replies, follow-ups, applications and attachments the author leaves to the human.
Who it is for. Job seekers ready to hand Claude Code the routine: collecting roles, tracking them in a table and sending first messages to contacts at target companies.
Good fit when
- Roles are scattered across LinkedIn, Indeed and web search and you want one scored table
- Target companies already have people you know and you want to send them a templated first message in one pass
- Every morning you want to see what is pending and what stalled: `/jobs check` prints a dashboard
- Any editor opens the table: `job_tracker.csv` reads in Numbers, Excel or VS Code
- Requests to 2nd-degree contacts should go without a note so the monthly quota of personalized invites is not spent
Not a fit when
- You need resume tailoring, reply handling and form auto-fill: those are excluded by design and the author points to a Codex version
- You work in the claude.ai/code web version: it cannot see local files or drive Chrome, so the desktop app is required
- LinkedIn is signed in to the wrong account: commands stop until it is fixed
- You want to get around the platform's limits on automation: messages go out in your name and fall under LinkedIn's rules
Example request
/jobs find: look for new senior backend roles in Berlin from my resume and add the best ones to the tracker, then show the dashboard with /jobs checkLimitations
- You need the Claude Code desktop app (the web version cannot see local files or Chrome), the Claude in Chrome extension and a LinkedIn sign-in in the same browser. LinkedIn is blocked in Russia.
- Messages go out in your name through the browser. Automation may conflict with LinkedIn's rules, and the platform itself caps invitations and messages per day.
- Features are deliberately trimmed: no reply handling, follow-ups, applications, resume tailoring or file uploads. Job statuses are edited by hand in `job_tracker.csv`.
- The last commit dates from June 2026, and Indeed support was added after the original version.
How to disable. Close the project folder in Claude Code and delete it. Disable the Claude in Chrome extension or sign out of LinkedIn in the browser so commands lose access. Your resume and contact logs live only on your disk.
FAQ
How do I start with claude-linkedin-assistant?
Clone the repository, put a resume into `resumes/`, open the folder in the Claude Code desktop app and run `/jobs setup`. After that `/jobs daily` is enough each day.
What do I need besides Claude Code?
The Claude in Chrome extension and a LinkedIn sign-in in the same browser. The Claude Code web version will not do: it cannot see local files or drive Chrome.
What does /jobs outreach do?
Sends a templated first message to people you know at the chosen company. The number of requests depends on how many contacts you already have there, and replies stay with you.
Where do jobs and contacts get stored?
Jobs live in `job_tracker.csv` and a per-company contact log in `outreach/`. The resume and logs are in `.gitignore` by default, so they stay on your disk.
Does it support Indeed?
Yes, optionally. `/jobs setup` asks about Indeed and `/jobs indeed-setup` enables it later and can improve your Indeed profile from the resume. Profile edits are shown before saving.
Discussion
No questions or reviews yet.
Related
PluginsAI Sales Team
AI Sales Team for Claude Code
A set of Claude Code skills and agents: research companies, qualify leads with BANT and MEDDIC, find decision makers, draft outreach and pipeline reports
yandex-tracker-mcp: a Yandex Tracker connector for Claude
Yandex Tracker connector
A connector for claude.ai, Claude Desktop and Claude Code that works with Yandex Tracker API v3 issues, with Yandex sign-in and deletion off by default
A marketplace of 67 Claude Code plugins for sales, marketing, growth and customer success, with agents, commands and skills
goszakupki-med: medical device tender plugin
goszakupki-med
A Claude plugin for medical device tenders under Russian 44-FZ and 223-FZ: tender analysis, spec review and RU-registry alternatives
A skill that searches 15 channels for creators with their own audience, gathers public contacts and appends them to a Google Sheet
SuperJob MCP server
superjob-mcp
An MCP server for the SuperJob job site: vacancies, employers, cities and professions through an AI agent
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Claude LinkedIn Assistant (this card) | no | 235 | ||
| AI Job Search | no | 70,034 | a job search workflow with an agent as a working loop, while here `/jobs` commands in Claude Code drive the browser and send first LinkedIn messages | |
| LinkedIn MCP Server by eliasbiondo | no | not required | 212 | an MCP server that searches people and jobs and reads profiles, while this project sends messages and keeps a job tracker |
README in short
The page explains the tool's purpose and limits, then walks five steps: clone, resume, open the folder in Claude Code, `/jobs setup` and `/jobs daily`. It then describes how everything rests on two state files, a feature table and a list of things deliberately not done, the daily flow, folder layout, tracker format and privacy.