mcpbeat Sign in

Linkedin Job Scraper Agent Skill

> Scrapes LinkedIn job postings using the JobSpy library (python-jobspy). Use this skill whenever the user wants to find jobs on LinkedIn, search for open roles, pull job listings, build a job pipeline, source job targets for GTM research, or monitor hiring signals. Even if the user just says "find me some jobs" or "what roles is [company] hiring for", use this skill. It runs a local Python script that outputs a CSV of job postings with title, company, location, salary, job type, description, and direct URLs.

2k tokens
context cost
the whole folder, loaded on every use
3
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
1086
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/gooseworks-ai/goose-skills --skill linkedin-job-scraper

What comes with it

4 300 bytes besides the instruction
scripts/jobspy_scraper.py
skill.meta.json

The instruction itself

13 sections, as written by the author

LinkedIn Scraper

Overview

This skill finds LinkedIn job postings by running tools/jobspy_scraper.py, a thin wrapper

around the JobSpy library. It handles installation,

parameter construction, execution, and result interpretation.

Quick Start

Install the dependency once (requires Python 3.10+):

python3.12 -m pip install -U python-jobspy --break-system-packages

Run the scraper:

python3.12 tools/jobspy_scraper.py \
  --search "software engineer" \
  --location "San Francisco, CA" \
  --results 25 \
  --output .tmp/jobs.csv

Results are saved as CSV and printed as a summary table.


Workflow

Step 1 — Understand the request

Identify from the user's message:

  • Search term — job title, role, or keyword (required)
  • Location — city, state, or "Remote" (optional but recommended)
  • Results wanted — default to 25 if not specified
  • Recencyhours_old filter if user wants recent posts (e.g. "last 48 hours")
  • Company filterlinkedin_company_ids if targeting a specific company
  • Full descriptions — set --fetch-descriptions if user needs job description text

If anything is ambiguous (e.g. "find AI jobs"), pick reasonable defaults and tell the user what you used.

Step 2 — Construct the command

Build the tools/jobspy_scraper.py command using the parameters below.

Always save output to .tmp/ so it's disposable and easy to find.

python tools/jobspy_scraper.py \
  --search "<term>" \
  --location "<location>" \
  --results <N> \
  [--hours-old <N>] \
  [--fetch-descriptions] \
  [--company-ids <id1,id2>] \
  [--job-type fulltime|parttime|contract|internship] \
  [--remote] \
  --output .tmp/<descriptive_filename>.csv

Note: --hours-old and --easy-apply cannot be used together (LinkedIn API constraint).

Step 3 — Run the script

Execute the command. The script will print a progress message and a summary of results found.

If the script is not found at tools/jobspy_scraper.py, check whether the file needs to be created

by reading skills/linkedin-job-scraper/scripts/jobspy_scraper.py and copying it to tools/.

Step 4 — Interpret and present results

After the run:

  • Report how many jobs were found
  • Show a brief table: Title | Company | Location | Salary | Posted
  • Note the output file path so the user can open it
  • If 0 results: suggest broadening the search term or removing the location filter

Parameters Reference

| Flag | Description | Default |

|------|-------------|---------|

| --search | Job title / keywords | required |

| --location | City, state, or country | none |

| --results | Number of results to fetch | 25 |

| --hours-old | Only jobs posted within N hours | none |

| --fetch-descriptions | Fetch full job descriptions (slower) | false |

| --company-ids | Comma-separated LinkedIn company IDs | none |

| --job-type | fulltime, parttime, contract, internship | any |

| --remote | Filter for remote jobs only | false |

| --output | Path for CSV output | .tmp/jobs.csv |


Output Columns

The CSV output includes:

| Column | Description |

|--------|-------------|

| TITLE | Job title |

| COMPANY | Employer name |

| LOCATION | City / State / Country |

| IS_REMOTE | True/False |

| JOB_TYPE | fulltime, contract, etc. |

| DATE_POSTED | When the listing was posted |

| MIN_AMOUNT | Minimum salary |

| MAX_AMOUNT | Maximum salary |

| CURRENCY | Currency code |

| JOB_URL | Direct link to the LinkedIn posting |

| DESCRIPTION | Full job description (if --fetch-descriptions used) |

| JOB_LEVEL | Seniority level (LinkedIn-specific) |

| COMPANY_INDUSTRY | Industry classification |


Common Use Cases

Find recent engineering roles at a startup:

python tools/jobspy_scraper.py --search "growth engineer" --location "New York" \
  --results 50 --hours-old 72 --output .tmp/growth_eng_nyc.csv

Monitor what a specific company is hiring for:

# First find the LinkedIn company ID from the company's LinkedIn URL
python tools/jobspy_scraper.py --search "engineer" --company-ids 1234567 \
  --results 100 --fetch-descriptions --output .tmp/company_hiring.csv

Find remote contract roles:

python tools/jobspy_scraper.py --search "data analyst" --remote \
  --job-type contract --results 30 --output .tmp/remote_contracts.csv

Error Handling

| Error | Fix |

|-------|-----|

| ModuleNotFoundError: jobspy | Run pip install -U python-jobspy |

| 0 results returned | Broaden search term, remove location, increase --results |

| Rate limited / blocked | Wait a few minutes; avoid running back-to-back large scrapes |

| hours_old and easy_apply cannot both be set | Remove one of those flags |


Script Location

The scraper script lives at tools/jobspy_scraper.py.

If it doesn't exist, copy it from skills/linkedin-scraper/scripts/jobspy_scraper.py to tools/:

cp skills/linkedin-job-scraper/scripts/jobspy_scraper.py tools/

Other skills for the same job

different authors, same section of the catalogue
Firecrawl Build Onboarding
by firecrawl
vendor ×1

Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

2k tokens
Facebook Ads Library Search
by browser-act

Searches Meta Ad Library (Facebook/Instagram/WhatsApp ads) by keyword or Facebook page ID and extracts ad details including creatives, copy, CTA, publisher platforms, spend, impressions, reach estimates, and page transparency info. Use when user mentions Meta Ad Library, Facebook ads scraper, Instagram ads data, FB ad library, search Facebook ads, get ads from a Facebook page, scrape Meta ads, Facebook advertising data, ad creative extraction, competitor ads analysis, brand ads monitoring, Meta advertising transparency, political ads Facebook, housing ads Facebook, view all ads from a page, facebook ads search, fb ads library api, facebook ad archive, instagram ad data, get ad creatives.

4k tokens scripts
Indexing
by kostja94

When the user wants to fix indexing issues from Search Console, use noindex, or implement Google Indexing API. Also use when the user mentions "fix indexing," "not indexed," "Crawled - currently not indexed," "discovered - currently not indexed," "index coverage," "noindex," "noindex tag," "pages not indexed," "why not indexed," "request indexing," or "Google Indexing API." For sitemap, use xml-sitemap.

2k tokens
Tavily Map
by tavily-ai

| Discover and list all URLs on a website without extracting content, via the Tavily CLI. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where something is on a domain, or says "map the site", "find the URL for", "what pages are on", "list all pages", or "site structure". Faster than crawling — returns URLs only. Essential when you know the site but not the exact page. Combine with extract for targeted content retrieval.

796 tokens
X Twitter Scraper
by aiskillstore

Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.

62k tokens
Apify Public Registries
by apify
vendor

Look up official company data from European public registries across 11 countries/regions (CZ, SK, PL, DE, UK, NL, RO, HR, SE + EU-level + ESG). Covers company registration, ownership, financial filings, VAT status, ESG data. Use when the user asks to "look up a company", "check registry", "find company info", "look up IČO/KRS/LEI/CRN", "company due diligence", "check VAT status", "find ownership structure", or needs official data from European registries. Reads tracked companies from data/companies.json. Some lookups use Python scripts (stdlib), some fall back to Apify actors for scraping-based registries.

39k tokens scripts
X Twitter Scraper
by lingxling

Use Xquik for X data workflows: tweet search, user lookup, follower export, media downloads, monitors, webhooks, REST API, MCP, SDK setup, and approval-gated account actions.

2k tokens
X Twitter Scraper
by Xquik-dev

Use Xquik for X/Twitter REST, MCP, SDKs, search, filtered exports, monitoring & approved publishing. Not affiliated with X Corp. Trigger for X API alternatives, pricing comparisons, tweet search, user lookup, timelines, follower exports, media, webhooks, bulk extraction, giveaways, or MCP setup. Read-only by default. Require explicit approval for writes, private reads, monitors, webhooks & metered bulk jobs.

62k tokens

How to use it

Copy the folder

Take gooseworks-ai/linkedin-job-scraper from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference pip. Without those the skill loads but fails at the first command.