Job Posting Scraper
MadsLorentzen/ai-job-search
Finds new job postings that match your profile through installed portal-search CLIs, dedupes against past runs and your application tracker, and rates each one's fit.
Search LinkedIn job listings and extract full job details. An agent skill from browser-act/skills.
$ npx skills add browser-act/skills --skill linkedin-jobs-search -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install browser-act/skills linkedin-jobs-search --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/solutions/lead-generation/linkedin-jobs-search .claude/skills/linkedin-jobs-search && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linkedin-jobs-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/lead-generation/linkedin-jobs-search into .claude/skills/linkedin-jobs-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-jobs-search", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/browser-act/skills/tree/main/solutions/lead-generation/linkedin-jobs-searchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add browser-act/skills --skill linkedin-jobs-search -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install browser-act/skills linkedin-jobs-search --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/solutions/lead-generation/linkedin-jobs-search .agents/skills/linkedin-jobs-search && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linkedin-jobs-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/lead-generation/linkedin-jobs-search into .agents/skills/linkedin-jobs-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-jobs-search", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add browser-act/skills --skill linkedin-jobs-search -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install browser-act/skills linkedin-jobs-search --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/solutions/lead-generation/linkedin-jobs-search .cursor/skills/linkedin-jobs-search && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linkedin-jobs-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/lead-generation/linkedin-jobs-search into .cursor/skills/linkedin-jobs-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-jobs-search", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/browser-act/skills.git --path solutions/lead-generation/linkedin-jobs-search--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add browser-act/skills --skill linkedin-jobs-search -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install browser-act/skills linkedin-jobs-search --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/solutions/lead-generation/linkedin-jobs-search .gemini/skills/linkedin-jobs-search && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linkedin-jobs-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/lead-generation/linkedin-jobs-search into .gemini/skills/linkedin-jobs-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-jobs-search", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install browser-act/skills linkedin-jobs-searchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add browser-act/skills --skill linkedin-jobs-search -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/solutions/lead-generation/linkedin-jobs-search .github/skills/linkedin-jobs-search && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-jobs-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/lead-generation/linkedin-jobs-search into .github/skills/linkedin-jobs-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-jobs-search", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add browser-act/skills --skill linkedin-jobs-search -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install browser-act/skills linkedin-jobs-search --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/browser-act/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/solutions/lead-generation/linkedin-jobs-search .opencode/skills/linkedin-jobs-search && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-jobs-search" agent skill from https://github.com/browser-act/skills/tree/main/solutions/lead-generation/linkedin-jobs-search into .opencode/skills/linkedin-jobs-search/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-jobs-search", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
linkedin-jobs-searchSearch LinkedIn job listings and extract full job details. An agent skill from browser-act/skills.
Linkedin Jobs Search is an agent skill from browser-act/skills. Search LinkedIn job listings and extract full job details. Supports filtering by work type (remote/on-site/hybrid), contract type (full-time/part-time/contract/internship), experience level, date posted, and company. Returns job title, company, location, work type, contract type, experience level, posted date, applicant count, job description, salary, and direct job URLs. Use when user mentions linkedin jobs, linkedin job search, scrape linkedin jobs, extract linkedin job listings, find jobs on linkedin, job…
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/job-detail.py` and `scripts/search-jobs.py`).
It sits in Business, Finance & HR, covering Recruiting and HR, Web scraping and Job search and resumes. It works with LinkedIn and Python. The repository describes itself as: Browser automation CLI built for AI agents. Break through anti-bot walls, hand off to humans across platforms when stuck. Parallel multi-task execution, independent multi-session… The licence is MIT.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 11c057b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
linkedin.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Linkedin Jobs Search loads about 2.5k tokens when it runs. Until then it costs about 193 tokens; SKILL.md has 916 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from browser-act/skills at commit 11c057b, republished under its MIT licence (© browser-act). 916 words, ~2,481 tokens.
.claude/skills/linkedin-jobs-search/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.keywords + location + filters → paginated job list with full details
All process output to user (progress updates, process notifications) follows the user's language.
Search LinkedIn job listings with full filter support, extract complete job data with full field coverage.
https://www.linkedin.com/jobs/search/ must have been visited at least once so the CSRF token cookie is set.If browser-act has been confirmed available in the current session → skip this step.
Invoke browser-act via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry.
If login status for LinkedIn has been confirmed in the current session → skip this step.
Otherwise: open https://www.linkedin.com and observe the page:
User refuses or cannot log in → terminate execution.
This Skill's operational boundary = what the user can manually do in their browser. It accesses LinkedIn through the user's logged-in browser, only reading data already available to the user. JS code is encapsulated in Python files under the
scripts/directory, invoked viaeval "$(python scripts/xxx.py {params})".$(...)is bash syntax; it is recommended to use the bash tool for execution.
eval "$(python scripts/search-jobs.py '{keywords}' '{location}' --count {count} --start {start} --work-type {work_type} --job-type {job_type} --experience {experience} --time-posted {time_posted} --company-ids {company_ids})"
Parameters:
keywords: job title or search keywords (e.g., software engineer, data analyst)location: location name (e.g., United States, New York, San Francisco Bay Area)--count: results per API call, default 25, max 100--start: pagination offset, default 0. Increment by count for each page--work-type: work arrangement filter — 1=On-site, 2=Remote, 3=Hybrid (optional)--job-type: contract type filter — F=Full-time, P=Part-time, C=Contract, T=Temporary, I=Internship, V=Volunteer (optional)--experience: experience level filter — 1=Internship, 2=Entry, 3=Associate, 4=Mid-Senior, 5=Director (optional)--time-posted: recency filter — r86400=24h, r604800=7 days, r2592000=30 days (optional)--company-ids: comma-separated LinkedIn company numeric IDs (optional, e.g., 76987811,1441)Output example:
{
"total": 36015,
"start": 0,
"count": 5,
"jobs": [
{
"id": "4416832078",
"title": "Lead Frontend Software Engineer",
"company": "RowsOne",
"location": "Boca Raton, FL",
"workType": "Remote",
"jobUrl": "https://www.linkedin.com/jobs/view/4416832078",
"companyUrl": "https://www.linkedin.com/company/rowsone"
}
]
}Error handling: If {"error": true} is returned, check that the browser is still logged in to LinkedIn and navigate to https://www.linkedin.com/jobs/search/ to refresh the session, then retry once.
eval "$(python scripts/job-detail.py '{job_id}')"
Parameters:
job_id: numeric LinkedIn job posting ID (from id field in search results)Output example:
{
"id": "4416832078",
"title": "Lead Frontend Software Engineer",
"company": "RowsOne",
"companyUrl": "https://www.linkedin.com/company/rowsone",
"location": "Boca Raton, FL",
"workType": "Remote",
"contractType": "Full-time",
"experienceLevel": "Mid-Senior level",
"listedAt": "2026-05-26T16:14:30.000Z",
"applicantCount": 37,
"description": "Lead Frontend Engineer (React / Next.js)...",
"salary": null,
"jobUrl": "https://www.linkedin.com/jobs/view/4416832078"
}Error handling: HTTP 404 means job has been removed or ID is invalid. If {"error": true, "message": "HTTP 403"}, the LinkedIn session may have expired — navigate back to LinkedIn and verify login, then retry.
For complete output with all fields (description, contract type, experience level, posted date):
Batch script template (bash):
#!/bin/bash
SESSION="fb_explore"
KEYWORDS="software engineer"
LOCATION="United States"
TOTAL_ROWS=50
COUNT=25
OUTPUT_FILE="output/jobs.jsonl"
offset=0
collected=0
while [ $collected -lt $TOTAL_ROWS ]; do
batch_count=$((TOTAL_ROWS - collected))
[ $batch_count -gt $COUNT ] && batch_count=$COUNT
result=$(browser-act --session $SESSION eval "$(python scripts/search-jobs.py "$KEYWORDS" "$LOCATION" --count $batch_count --start $offset)")
echo "$result" | python -c "
import json, sys
data = json.loads(sys.stdin.read())
for job in data.get('jobs', []):
print(json.dumps(job))
" >> output/jobs_basic.jsonl
job_ids=$(echo "$result" | python -c "import json,sys; [print(j['id']) for j in json.loads(sys.stdin.read()).get('jobs',[])]")
for job_id in $job_ids; do
detail=$(browser-act --session $SESSION eval "$(python scripts/job-detail.py $job_id)")
echo "$detail" >> $OUTPUT_FILE
sleep 1
done
page_count=$(echo "$result" | python -c "import json,sys; print(json.loads(sys.stdin.read()).get('count',0))")
[ "$page_count" -eq 0 ] && break
collected=$((collected + page_count))
offset=$((offset + page_count))
sleep 2
done
echo "Done. Collected $collected jobs."Note: Add sleep 1 between detail calls to avoid rate limiting. For large batches (>200 jobs), use multiple browser sessions in parallel — each session counts independently toward rate limits.
Filter values are hardcoded in scripts; no dynamic enumeration needed.
Work type (--work-type): 1=On-site, 2=Remote, 3=Hybrid
Contract type (--job-type): F=Full-time, P=Part-time, C=Contract, T=Temporary, I=Internship, V=Volunteer
Experience level (--experience): 1=Internship, 2=Entry level, 3=Associate, 4=Mid-Senior level, 5=Director
Time posted (--time-posted): r86400=Past 24 hours, r604800=Past week, r2592000=Past month
API Pagination: parameter --start, type: page-offset, start value: 0. Next page: increment by --count value. Termination: when count in response is 0, or start >= total, or start >= rows target.
LinkedIn typically returns results up to start=1000 maximum regardless of total.
result count >= 1 and jobs[0].id is non-null
total shows a higher numberexperienceLevel may be null for many postings — companies do not always fill in this fieldsalary is null for most postings; LinkedIn only shows salary when the employer explicitly provides itsleep 1 between detail callsJSESSIONID cookie set at login--count 3 first to confirm the script runs correctly before scaling up.jsonl file line-by-line so the job can resume from a specific offset on failurePath: {working-directory}/browser-act-skill-forge-memories/linkedin-job-search-linkedin-jobs-search.memory.md (working directory is determined by the Agent running the Skill, typically the project root or current working directory)
Before execution: If the file exists, read it first — it records unexpected situations encountered during past executions (e.g., a strategy has become ineffective); adjust strategy order accordingly.
After execution: If an unexpected situation is encountered (strategy became ineffective, page redesigned, anti-scraping upgraded, better path discovered), append a line:
{YYYY-MM-DD}: {what happened} → {conclusion}
Normal execution does not write to the file. Do not record what keywords were used or how many results were returned — those are task outputs, not experience.
© browser-act, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in solutions/lead-generation/linkedin-jobs-search of browser-act/skills.
Open the folder on GitHubat commit 11c057b
Linkedin Jobs Search next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linkedin Jobs Search this skillbrowser-act/skills | 6.1k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Job Posting ScraperMadsLorentzen/ai-job-search | 45k | — | ~5.7k | Automated safety check: Pass | MIT | |
| Job Application Managerreactive-resume/reactive-resume | 44k | — | ~13k | Automated safety check: Pass | MIT | |
| Apify Buying Signal Detectionapify/awesome-skills | 266 | — | ~5.1k | Automated safety check: Notes | Apache-2.0 | |
| Company Hiring Intelligencetinyfish-io/tinyfish-cookbook | 2.2k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Bright Data MCPbrightdata/skills | 264 | 1 repos | ~3.7k | Automated safety check: Pass | MIT |
MadsLorentzen/ai-job-search
Finds new job postings that match your profile through installed portal-search CLIs, dedupes against past runs and your application tracker, and rates each one's fit.
reactive-resume/reactive-resume
Runs the job-search pipeline. An agent skill from reactive-resume/reactive-resume.
apify/awesome-skills
Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises)…
tinyfish-io/tinyfish-cookbook
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents.
brightdata/skills
Bright Data MCP handles ALL web data operations. An agent skill from brightdata/skills.
mohitagw15856/pm-claude-skills
Write cold outreach and networking messages that actually get replies.
browser-act/skills
Fetches structured Amazon product details such as title, price, ratings and availability for a given ASIN through BrowserAct's lookup API template.
browser-act/skills
Extracts structured Amazon product data for a keyword and marketplace through the BrowserAct API, including titles, prices, ratings, reviews, sales volume and promotions.
browser-act/skills
Pulls Amazon product details, competing seller prices and seller ratings for a given ASIN through the BrowserAct API, without browser automation.
browser-act/skills
Analyzes a competitor's Amazon listing by ASIN with BrowserAct data extraction, then reports what it does well, where the market has gaps and opportunity points for your own listing.
browser-act/skills
Pulls structured Amazon search results (titles, ASINs, prices, ratings, specifications) for a keyword and brand through BrowserAct's Amazon Product API template.
browser-act/skills
Collects structured product data from Amazon search results for a keyword and optional brand, using a BrowserAct script, for market and competitor research.
Categories
Search LinkedIn job listings and extract full job details. An agent skill from browser-act/skills. Linkedin Jobs Search is an agent skill from browser-act/skills. Search LinkedIn job listings and extract full job details.
Linkedin Jobs Search fits situations like: user mentions linkedin jobs; linkedin job search; scrape linkedin jobs; extract linkedin job listings.
Run `npx skills add browser-act/skills --skill linkedin-jobs-search -a claude-code`. Or copy the skill folder (solutions/lead-generation/linkedin-jobs-search in browser-act/skills) into .claude/skills/linkedin-jobs-search in your project. Claude Code loads it when a task matches its description.
Run `npx skills add browser-act/skills --skill linkedin-jobs-search -a codex`. Or copy the skill folder (solutions/lead-generation/linkedin-jobs-search in browser-act/skills) into .agents/skills/linkedin-jobs-search in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add browser-act/skills --skill linkedin-jobs-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin-jobs-search, .gemini/skills/linkedin-jobs-search, .github/skills/linkedin-jobs-search and .opencode/skills/linkedin-jobs-search in your project.
Going by SKILL.md and its folder, Linkedin Jobs Search needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
SKILL.md names 1 domain. In commands or code: linkedin.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Linkedin Jobs Search is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Linkedin Jobs Search: Job Posting Scraper (MadsLorentzen/ai-job-search, 45k stars), Job Application Manager (reactive-resume/reactive-resume, 44k stars), Apify Buying Signal Detection (apify/awesome-skills, 266 stars) and Company Hiring Intelligence (tinyfish-io/tinyfish-cookbook, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
browser-act (a GitHub organization) maintains it in browser-act/skills, which has 6,126 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on August 24, 2026.
Source: browser-act/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.