← ClaudeAtlas

linkedin-outreachlisted

Job-search outreach on LinkedIn with a local dashboard (Outreach Desk). Finds people in the user's field country by country (Apollo or LinkedIn search), sends connection requests, checks who accepted, drafts and sends thank-you, CV and follow-up messages with the user's approval, and tracks everything on a dashboard at http://localhost:4877. Use when the user says "run today's outreach", "check who accepted", "start a campaign for <country>", "draft messages", "who replied", "open the outreach desk", "Run the Outreach Desk queue", "Watch the Outreach Desk", "set up linkedin outreach", or anything about LinkedIn connection requests, networking for a job search or the outreach pipeline, even if they don't name the skill.
theommishra-dev/linkedin-outreach · ★ 0 · AI & Automation · score 72
Install: claude install-skill theommishra-dev/linkedin-outreach
# LinkedIn Outreach The user is looking for a job. One country campaign at a time, they connect with people in their field, thank them when they accept, then send their CV and ask for help getting a position. Claude does the research, writing and tracking. LinkedIn actions happen in the visible Playwright browser at human pace, and **nothing is sent without the user's approval**. `<skill>` below means this skill's base directory (given when the skill loads). Run Python with plain `python3` (standard library only), unless the project has its own rule, e.g. a CLAUDE.md that says to use a `.venv`: then use that interpreter. ## Step 0, every time: open the dashboard and watch it Before anything else, whatever the user asked for: 1. `python3 "<skill>/app/launch.py" --if-closed` It starts the local server if needed and opens http://localhost:4877, unless a dashboard tab is already open. The user watches it while you work. 2. **Start the desk watcher** (workflow E) if this session doesn't already have one running. Without it, a **Run changes** press on the dashboard never reaches Claude and the user's approved changes just sit there. Then check `<skill>/data/profile.md`. If it doesn't exist, run **workflow F (first-time setup)** before anything else. ## Where things are | What | Where | |---|---| | Dashboard (single source of truth) | http://localhost:4877, code in `<skill>/app/`, data in `<skill>/data/db.json` | | The user's profile: target roles, keywords, countries, comm