linkedin-sourcer/SKILL.md
Source and evaluate candidates from LinkedIn using the linkedin_scraper Python library. Use when the user wants to (1) scrape LinkedIn profiles for candidate data, (2) evaluate candidates against a job description, (3) generate boolean search strings for sourcing, (4) produce candidate scorecards, summaries, or comparison tables, or (5) any recruiting/talent-sourcing task involving LinkedIn data.
npx skillsauth add kylemclaren/linkedin-sourcer linkedin-sourcerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Source candidates from LinkedIn, analyze their profiles, and evaluate fit against role requirements using the linkedin_scraper library (v3.0+, Playwright-based, async).
Ensure dependencies are installed before any scraping:
pip install linkedin-scraper
playwright install chromium
An authenticated session file (session.json) is required. If one does not exist, create one:
Programmatic login (using credentials):
python3 scripts/create_session.py --email [email protected] --password PASS
Or via environment variables:
export [email protected]
export LINKEDIN_PASSWORD=mypassword
python3 scripts/create_session.py
Manual login (opens a browser window — use when programmatic login fails due to CAPTCHA/2FA):
python3 scripts/create_session.py
The session file is reusable until LinkedIn expires it. See references/linkedin_scraper_api.md for browser configuration options.
Determine the task type:
Run scripts/scrape_profile.py to extract structured profile data:
python3 scripts/scrape_profile.py "https://linkedin.com/in/username" --session session.json
For multiple profiles:
python3 scripts/scrape_profile.py URL1 URL2 URL3 --delay 2 --output profiles.json
Output is JSON with: name, headline, location, about, experiences, educations, skills.
For inline scraping within custom code, see references/linkedin_scraper_api.md → PersonScraper.
Generate boolean search queries the user can paste into LinkedIn or Google to find candidates. See references/sourcing_workflows.md → Boolean Search String Patterns for templates and examples. Tailor the boolean string to the specific role requirements provided.
After scraping profile(s), evaluate fit against a job description:
references/sourcing_workflows.md → Candidate Scorecard TemplateUse the evaluation heuristics in references/sourcing_workflows.md → Evaluation Heuristics to guide ratings.
For quick single-candidate output, use the Candidate Summary Template instead.
When evaluating multiple candidates for the same role:
references/sourcing_workflows.md → Candidate Comparison Tablescripts/create_session.py with credentials or manual login--delay between requestsSee references/linkedin_scraper_api.md → Error Handling for try/except patterns.
Always use delays between requests (default 2s in scripts). For large batches, increase to 3-5s. Never scrape aggressively — respect LinkedIn's rate limits.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.