Job scraper

Search for job postings across LinkedIn and Indeed.

How to use it

  1. Hit Copy the whole skill.
  2. Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
    ChatGPT: make a Project and paste it into Instructions.
    Neither? Paste it at the top of a new chat — it works for that chat.
  3. Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit gooseworks-ai/goose-skills/skills/lead-generation/capabilities/job-scraper#main ~/.claude/skills/job-scraper

For one project only, change the path to .claude/skills/job-scraper.

Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Show the full text270 lines
job-scraper/SKILL.md270 lines10.1 KBpushed 96d agoRawView on GitHub

Job Scraper

Search for job postings across LinkedIn and Indeed using Apify. Find open roles by keyword, location, company, or job type. Use for hiring signal detection, GTM research, or competitive intelligence.

No LinkedIn cookies. No Indeed login. Just search queries in, structured job data out.

When to Auto-Load

Load this skill when:

  • User says "find jobs", "who is hiring", "what roles is [company] hiring for"
  • User wants hiring signals ("find companies growing their AI team")
  • User wants competitive intelligence ("what is [competitor] hiring for")
  • User says "job search", "open roles", "job listings", "job postings"

Prerequisites

Apify API Token

Required for both LinkedIn and Indeed scraping. Set in .env:

APIFY_API_TOKEN=your_token_here

No LinkedIn cookies, Indeed login, or any platform credentials needed. That's the only setup.


Sources

This skill searches two job platforms via Apify actors:

Source Apify Actor Best For Cost
LinkedIn automation-lab/linkedin-jobs-scraper B2B, tech, SaaS, enterprise roles. Has seniority level, job function, industries. ~$0.002/job
Indeed borderline/indeed-scraper Broadest coverage. Richest data — salary, company details, ratings, contacts, street addresses. ~$0.004/job

Source Selection Logic

Do NOT ask the user which source to use unless genuinely ambiguous. Decide based on context:

  1. User specifies a source → use that source only.
  2. Context strongly suggests one source:
    • B2B/tech/SaaS roles, enterprise companies, seniority-level filtering → LinkedIn
    • Hourly/blue-collar roles, local/retail jobs, salary-focused search → Indeed
    • Company hiring research ("what is Stripe hiring for") → LinkedIn (better company filtering)
  3. No clear signal → search both sources, deduplicate results by job title + company name, present combined results.

After deciding, tell the user which source(s) you're searching and why. Don't ask — inform.


Workflow

Phase 0: Understand the Request

Extract from the user's message:

  • Search term — job title, role, or keyword (required)
  • Location — city, state, country, or "Remote" (optional)
  • Company — specific company name (optional)
  • Recency — "recent", "last week", "last 30 days" (optional)
  • Job type — fulltime, parttime, contract, internship (optional)
  • Remote — whether to filter for remote jobs (optional)
  • Result count — how many results they want (default: 25)

If anything is ambiguous, pick reasonable defaults and tell the user what you chose. Do not ask clarifying questions for things you can reasonably infer.

Phase 1: Search

LinkedIn — automation-lab/linkedin-jobs-scraper

API call:

curl -X POST "https://api.apify.com/v2/acts/automation-lab~linkedin-jobs-scraper/runs?token=$APIFY_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "searchQuery": "AI engineer",
    "location": "San Francisco",
    "maxItems": 25
  }'

Input fields:

Field Type Description
searchQuery string Job title or keywords (required)
location string City, state, or country (optional)
maxItems integer Max jobs to return (default: 50)

Polling for results:

# Check run status (poll every 10s)
curl "https://api.apify.com/v2/acts/automation-lab~linkedin-jobs-scraper/runs/{RUN_ID}?token=$APIFY_API_TOKEN"

# When status is SUCCEEDED, fetch results
curl "https://api.apify.com/v2/datasets/{DATASET_ID}/items?token=$APIFY_API_TOKEN"

Output fields per job:

  • title — Job title
  • companyName — Company name
  • companyLinkedinUrl — Company LinkedIn page
  • companyLogo — Logo URL
  • location — City, state
  • salary — Salary text (when available)
  • employmentType — Full-time, Part-time, Contract, etc.
  • seniorityLevel — Entry, Mid-Senior, Director, Executive, etc.
  • jobFunction — Engineering, Sales, Marketing, etc.
  • industries — Industry classification
  • descriptionText — Full job description (plain text)
  • descriptionHtml — Full job description (HTML)
  • applicantsCount — Number of applicants
  • postedAt — When posted (e.g., "6 days ago")
  • url — Direct link to the LinkedIn job posting
  • applyUrl — Direct apply URL

Indeed — borderline/indeed-scraper

API call:

curl -X POST "https://api.apify.com/v2/acts/borderline~indeed-scraper/runs?token=$APIFY_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "AI engineer",
    "location": "San Francisco, CA",
    "country": "us",
    "maxResults": 25
  }'

Input fields:

Field Type Description
query string Job title or keywords (required)
location string City and state (optional)
country string Lowercase 2-letter country code (required). Common: us, uk, ca, de, fr, in, au
maxResults integer Max jobs to return

Important: The country field is required for Indeed. If the user doesn't specify a country, default to us. Use lowercase 2-letter codes only.

Output fields per job:

  • title — Job title
  • companyName — Company name
  • companyDescription — Company description
  • companyNumEmployees — Company size
  • companyRevenue — Company revenue range
  • companyUrl — Company Indeed page
  • location — Object with city, postalCode, country, formattedAddressShort, latitude, longitude, streetAddress
  • salary — Object with salaryCurrency, salaryMin, salaryMax, salaryText, salaryType (hourly/yearly)
  • descriptionText — Full job description (plain text)
  • descriptionHtml — Full job description (HTML)
  • datePublished — Posted date (YYYY-MM-DD)
  • age — Human-readable age ("24 days ago")
  • expired — Whether job is still active
  • isRemote — Remote flag
  • jobType — Employment type
  • jobUrl — Direct Indeed job URL
  • applyUrl — Direct apply URL
  • rating — Company rating and review count
  • emails — Contact emails (when available)
  • attributes — Job attributes list (benefits, requirements, etc.)
  • hiringDemand — Urgent hire / high volume hiring flags

Phase 2: Filter & Deduplicate

Recency Filtering

If the user asked for recent jobs, filter results by date:

  • LinkedIn: Use postedAt field (e.g., "6 days ago") — parse the text to determine recency.
  • Indeed: Use datePublished field (YYYY-MM-DD) — compare against today's date.

Remove jobs older than what the user requested. If no recency filter specified, still remove jobs older than 30 days by default to avoid stale data.

Deduplication (when using both sources)

When searching both LinkedIn and Indeed, the same job may appear on both platforms. Deduplicate by matching:

  1. Normalize company name (lowercase, strip "Inc", "LLC", "Corp", etc.)
  2. Normalize job title (lowercase)
  3. If company name AND job title match, keep the result with richer data (prefer Indeed for salary data, LinkedIn for seniority level)

Phase 3: Present Results

Show results as a summary table:

Source: LinkedIn + Indeed (deduplicated)
Jobs found: {count}
Location: {location}
Search: "{query}"

| # | Title | Company | Location | Salary | Posted | Source |
|---|-------|---------|----------|--------|--------|--------|
| 1 | AI Engineer | Stripe | SF, CA | $200K-$300K | 3 days ago | LinkedIn |
| 2 | ML Engineer | Meta | Menlo Park, CA | $58.65/hr | Mar 14 | Indeed |
| ... |

After the table:

  • Note how many were filtered for recency
  • Note how many duplicates were removed
  • Provide the total cost of the search

If the user wants more detail on a specific job, show the full description.

Phase 4: Export (Optional)

If the user wants to save results:

{search-term}-jobs-{YYYY-MM-DD}.csv

CSV columns:

title, company, location, salary, employment_type, seniority_level, posted_date, job_url, apply_url, description, source

Normalize fields across sources so the CSV has a consistent schema regardless of whether the job came from LinkedIn or Indeed.


Cost Estimates

Search LinkedIn Only Indeed Only Both Sources
25 jobs ~$0.05 ~$0.10 ~$0.15
50 jobs ~$0.10 ~$0.20 ~$0.30
100 jobs ~$0.20 ~$0.40 ~$0.60

LinkedIn is cheaper per job. Indeed returns richer data per job. Both together give the most complete picture.


Common Use Cases

Hiring signal detection: "Find companies hiring AI engineers in SF" → Search both sources, group by company, rank by number of open roles. Companies with 5+ AI roles are actively building.

Competitive intelligence: "What is Anthropic hiring for?" → Search LinkedIn with searchQuery: "Anthropic". Shows their open roles, team growth, and strategic priorities.

Salary research: "What do ML engineers make in NYC?" → Search Indeed (richer salary data). Filter to NYC, aggregate salary ranges.

GTM prospecting: "Find companies hiring for VP of Sales" → These companies are scaling their sales org and may need sales tools. Export the company list for outreach.


Error Handling

Error Fix
APIFY_API_TOKEN not set Ask user to add it to .env
Indeed: Missing country input Add country field with lowercase 2-letter code (default: us)
LinkedIn: 0 results Broaden search query or remove location filter
Indeed: 999 results returned The maxResults field may not cap results. Filter client-side.
Apify run fails or times out Retry once. If still fails, try the other source.
Stale results (30+ days old) Apply recency filter. Warn user about data freshness.
1---
2name: job-scraper
3description: >
4 Search for job postings across LinkedIn and Indeed. Use when users want to find open roles,
5 monitor hiring signals, identify companies hiring for specific positions, or research
6 competitor hiring activity. Returns job title, company, location, salary, description,
7 seniority level, and direct apply URLs. No login or cookies required.
8tags: [lead-generation, research]
9---
10 
11# Job Scraper
12 
13Search for job postings across LinkedIn and Indeed using Apify. Find open roles by keyword, location, company, or job type. Use for hiring signal detection, GTM research, or competitive intelligence.
14 
15No LinkedIn cookies. No Indeed login. Just search queries in, structured job data out.
16 
17## When to Auto-Load
18 
19Load this skill when:
20- User says "find jobs", "who is hiring", "what roles is [company] hiring for"
21- User wants hiring signals ("find companies growing their AI team")
22- User wants competitive intelligence ("what is [competitor] hiring for")
23- User says "job search", "open roles", "job listings", "job postings"
24 
25## Prerequisites
26 
27### Apify API Token
28 
29Required for both LinkedIn and Indeed scraping. Set in `.env`:
30 
31```
32APIFY_API_TOKEN=your_token_here
33```
34 
35No LinkedIn cookies, Indeed login, or any platform credentials needed. That's the only setup.
36 
37---
38 
39## Sources
40 
41This skill searches two job platforms via Apify actors:
42 
43| Source | Apify Actor | Best For | Cost |
44|--------|------------|----------|------|
45| **LinkedIn** | `automation-lab/linkedin-jobs-scraper` | B2B, tech, SaaS, enterprise roles. Has seniority level, job function, industries. | ~$0.002/job |
46| **Indeed** | `borderline/indeed-scraper` | Broadest coverage. Richest data — salary, company details, ratings, contacts, street addresses. | ~$0.004/job |
47 
48### Source Selection Logic
49 
50**Do NOT ask the user which source to use unless genuinely ambiguous.** Decide based on context:
51 
521. **User specifies a source** → use that source only.
532. **Context strongly suggests one source:**
54 - B2B/tech/SaaS roles, enterprise companies, seniority-level filtering → **LinkedIn**
55 - Hourly/blue-collar roles, local/retail jobs, salary-focused search → **Indeed**
56 - Company hiring research ("what is Stripe hiring for") → **LinkedIn** (better company filtering)
573. **No clear signal** → search **both sources**, deduplicate results by job title + company name, present combined results.
58 
59After deciding, **tell the user which source(s) you're searching and why.** Don't ask — inform.
60 
61---
62 
63## Workflow
64 
65### Phase 0: Understand the Request
66 
67Extract from the user's message:
68- **Search term** — job title, role, or keyword (required)
69- **Location** — city, state, country, or "Remote" (optional)
70- **Company** — specific company name (optional)
71- **Recency** — "recent", "last week", "last 30 days" (optional)
72- **Job type** — fulltime, parttime, contract, internship (optional)
73- **Remote** — whether to filter for remote jobs (optional)
74- **Result count** — how many results they want (default: 25)
75 
76If anything is ambiguous, pick reasonable defaults and tell the user what you chose. Do not ask clarifying questions for things you can reasonably infer.
77 
78### Phase 1: Search
79 
80#### LinkedIn — `automation-lab/linkedin-jobs-scraper`
81 
82**API call:**
83```bash
84curl -X POST "https://api.apify.com/v2/acts/automation-lab~linkedin-jobs-scraper/runs?token=$APIFY_API_TOKEN" \
85 -H "Content-Type: application/json" \
86 -d '{
87 "searchQuery": "AI engineer",
88 "location": "San Francisco",
89 "maxItems": 25
90 }'
91```
92 
93**Input fields:**
94| Field | Type | Description |
95|-------|------|-------------|
96| `searchQuery` | string | Job title or keywords (required) |
97| `location` | string | City, state, or country (optional) |
98| `maxItems` | integer | Max jobs to return (default: 50) |
99 
100**Polling for results:**
101```bash
102# Check run status (poll every 10s)
103curl "https://api.apify.com/v2/acts/automation-lab~linkedin-jobs-scraper/runs/{RUN_ID}?token=$APIFY_API_TOKEN"
104 
105# When status is SUCCEEDED, fetch results
106curl "https://api.apify.com/v2/datasets/{DATASET_ID}/items?token=$APIFY_API_TOKEN"
107```
108 
109**Output fields per job:**
110- `title` — Job title
111- `companyName` — Company name
112- `companyLinkedinUrl` — Company LinkedIn page
113- `companyLogo` — Logo URL
114- `location` — City, state
115- `salary` — Salary text (when available)
116- `employmentType` — Full-time, Part-time, Contract, etc.
117- `seniorityLevel` — Entry, Mid-Senior, Director, Executive, etc.
118- `jobFunction` — Engineering, Sales, Marketing, etc.
119- `industries` — Industry classification
120- `descriptionText` — Full job description (plain text)
121- `descriptionHtml` — Full job description (HTML)
122- `applicantsCount` — Number of applicants
123- `postedAt` — When posted (e.g., "6 days ago")
124- `url` — Direct link to the LinkedIn job posting
125- `applyUrl` — Direct apply URL
126 
127#### Indeed — `borderline/indeed-scraper`
128 
129**API call:**
130```bash
131curl -X POST "https://api.apify.com/v2/acts/borderline~indeed-scraper/runs?token=$APIFY_API_TOKEN" \
132 -H "Content-Type: application/json" \
133 -d '{
134 "query": "AI engineer",
135 "location": "San Francisco, CA",
136 "country": "us",
137 "maxResults": 25
138 }'
139```
140 
141**Input fields:**
142| Field | Type | Description |
143|-------|------|-------------|
144| `query` | string | Job title or keywords (required) |
145| `location` | string | City and state (optional) |
146| `country` | string | Lowercase 2-letter country code (required). Common: `us`, `uk`, `ca`, `de`, `fr`, `in`, `au` |
147| `maxResults` | integer | Max jobs to return |
148 
149**Important:** The `country` field is required for Indeed. If the user doesn't specify a country, default to `us`. Use lowercase 2-letter codes only.
150 
151**Output fields per job:**
152- `title` — Job title
153- `companyName` — Company name
154- `companyDescription` — Company description
155- `companyNumEmployees` — Company size
156- `companyRevenue` — Company revenue range
157- `companyUrl` — Company Indeed page
158- `location` — Object with `city`, `postalCode`, `country`, `formattedAddressShort`, `latitude`, `longitude`, `streetAddress`
159- `salary` — Object with `salaryCurrency`, `salaryMin`, `salaryMax`, `salaryText`, `salaryType` (hourly/yearly)
160- `descriptionText` — Full job description (plain text)
161- `descriptionHtml` — Full job description (HTML)
162- `datePublished` — Posted date (YYYY-MM-DD)
163- `age` — Human-readable age ("24 days ago")
164- `expired` — Whether job is still active
165- `isRemote` — Remote flag
166- `jobType` — Employment type
167- `jobUrl` — Direct Indeed job URL
168- `applyUrl` — Direct apply URL
169- `rating` — Company rating and review count
170- `emails` — Contact emails (when available)
171- `attributes` — Job attributes list (benefits, requirements, etc.)
172- `hiringDemand` — Urgent hire / high volume hiring flags
173 
174### Phase 2: Filter & Deduplicate
175 
176#### Recency Filtering
177 
178If the user asked for recent jobs, filter results by date:
179- **LinkedIn:** Use `postedAt` field (e.g., "6 days ago") — parse the text to determine recency.
180- **Indeed:** Use `datePublished` field (YYYY-MM-DD) — compare against today's date.
181 
182Remove jobs older than what the user requested. If no recency filter specified, still remove jobs older than 30 days by default to avoid stale data.
183 
184#### Deduplication (when using both sources)
185 
186When searching both LinkedIn and Indeed, the same job may appear on both platforms. Deduplicate by matching:
1871. Normalize company name (lowercase, strip "Inc", "LLC", "Corp", etc.)
1882. Normalize job title (lowercase)
1893. If company name AND job title match, keep the result with richer data (prefer Indeed for salary data, LinkedIn for seniority level)
190 
191### Phase 3: Present Results
192 
193Show results as a summary table:
194 
195```
196Source: LinkedIn + Indeed (deduplicated)
197Jobs found: {count}
198Location: {location}
199Search: "{query}"
200 
201| # | Title | Company | Location | Salary | Posted | Source |
202|---|-------|---------|----------|--------|--------|--------|
203| 1 | AI Engineer | Stripe | SF, CA | $200K-$300K | 3 days ago | LinkedIn |
204| 2 | ML Engineer | Meta | Menlo Park, CA | $58.65/hr | Mar 14 | Indeed |
205| ... |
206```
207 
208After the table:
209- Note how many were filtered for recency
210- Note how many duplicates were removed
211- Provide the total cost of the search
212 
213If the user wants more detail on a specific job, show the full description.
214 
215### Phase 4: Export (Optional)
216 
217If the user wants to save results:
218 
219```
220{search-term}-jobs-{YYYY-MM-DD}.csv
221```
222 
223CSV columns:
224```
225title, company, location, salary, employment_type, seniority_level, posted_date, job_url, apply_url, description, source
226```
227 
228Normalize fields across sources so the CSV has a consistent schema regardless of whether the job came from LinkedIn or Indeed.
229 
230---
231 
232## Cost Estimates
233 
234| Search | LinkedIn Only | Indeed Only | Both Sources |
235|--------|-------------|------------|-------------|
236| 25 jobs | ~$0.05 | ~$0.10 | ~$0.15 |
237| 50 jobs | ~$0.10 | ~$0.20 | ~$0.30 |
238| 100 jobs | ~$0.20 | ~$0.40 | ~$0.60 |
239 
240LinkedIn is cheaper per job. Indeed returns richer data per job. Both together give the most complete picture.
241 
242---
243 
244## Common Use Cases
245 
246**Hiring signal detection:**
247"Find companies hiring AI engineers in SF" → Search both sources, group by company, rank by number of open roles. Companies with 5+ AI roles are actively building.
248 
249**Competitive intelligence:**
250"What is Anthropic hiring for?" → Search LinkedIn with `searchQuery: "Anthropic"`. Shows their open roles, team growth, and strategic priorities.
251 
252**Salary research:**
253"What do ML engineers make in NYC?" → Search Indeed (richer salary data). Filter to NYC, aggregate salary ranges.
254 
255**GTM prospecting:**
256"Find companies hiring for VP of Sales" → These companies are scaling their sales org and may need sales tools. Export the company list for outreach.
257 
258---
259 
260## Error Handling
261 
262| Error | Fix |
263|-------|-----|
264| `APIFY_API_TOKEN` not set | Ask user to add it to `.env` |
265| Indeed: `Missing country input` | Add `country` field with lowercase 2-letter code (default: `us`) |
266| LinkedIn: 0 results | Broaden search query or remove location filter |
267| Indeed: 999 results returned | The `maxResults` field may not cap results. Filter client-side. |
268| Apify run fails or times out | Retry once. If still fails, try the other source. |
269| Stale results (30+ days old) | Apply recency filter. Warn user about data freshness. |
270 

Discussion

Alternatives

Also in Company & contact data