mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-11-11 17:37:59 +00:00
Thomas Christian VangandClaude Sonnet 5.5
7432228340
* fix(scrape): send one plain term per CLI call and make portals state their query syntax (#536) search-queries.md is written in Google syntax, and Step 1b said to translate its terms into portal flags without saying that OR and quotes do not survive the translation. - job-scraper Step 1b: one plain term per CLI call, never OR or a combined string; results merge across calls (Step 2 dedups on URL). Quoting follows the portal's own SKILL.md. - Portal SKILL.md files carry a one-line "Query syntax:" note; /add-portal asks the generator to write it for new portals. - search-queries.md: site: blocks are labelled WebSearch-only and each priority gains a plain-terms block for the CLIs. - tests/test_scrape_contract.py: every installed portal SKILL.md must carry the Query syntax line; the portal list is derived from the skills tree. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * fix(scrape): fall back to site: terms for placeholder blocks; update freehire query syntax Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore: drop the CHANGELOG hunk, frozen by #800 (release notes come from the PR title) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * fix(scrape): dedup the pool by URL before Step 2 and give each portal's literal quote form Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * fix(add-portal): compare the portal's reported total, not capped rows, when probing query syntax Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
106 lines
4.6 KiB
Markdown
106 lines
4.6 KiB
Markdown
---
|
|
name: linkedin-search
|
|
version: 1.0.0
|
|
description: >
|
|
Use this skill whenever the user wants to search for jobs in any location or
|
|
market, find job listings, or look up a specific job posting — in any country,
|
|
city, or remotely. Invoke for open positions, vacancies, and hiring across any
|
|
sector or role (software, data, design, marketing, finance, legal, operations,
|
|
etc.). The location is always supplied explicitly by the user. Trigger phrases:
|
|
find a job, job search, search for jobs, job openings, vacancies, hiring,
|
|
positions open, remote jobs, "are there any X jobs in <place>", look up this
|
|
job posting.
|
|
context: fork
|
|
enabled: true # set to false to keep this portal installed but have /scrape skip it
|
|
allowed-tools: Bash(bun run .agents/skills/linkedin-search/cli/src/cli.ts *)
|
|
---
|
|
|
|
# LinkedIn Search Skill
|
|
|
|
Search live job listings from LinkedIn's public job board for **any country/region**
|
|
(and remote). No authentication, no API key, and **zero runtime dependencies** — it runs
|
|
with just `bun`. The location is always passed explicitly, so the same skill works for a
|
|
forker in any market out of the box.
|
|
|
|
> This is a country-agnostic worked example of the repo's job-portal-skill pattern.
|
|
> LinkedIn's `jobs-guest` endpoints are global and the HTML parsing is country-independent;
|
|
> only the `--location` you pass changes per market.
|
|
|
|
## ⚠️ Personal use only
|
|
|
|
This uses LinkedIn's public job pages; automated access is against LinkedIn's Terms of
|
|
Service, so **keep volume low and don't use it commercially or for bulk data collection.**
|
|
Run it on your own responsibility.
|
|
|
|
## When to use this skill
|
|
|
|
- Search for job openings in a given location (any country/city) or remotely
|
|
- Filter by recency (posted today / last 7 / 14 / 30 days) or workplace type (remote/hybrid/onsite)
|
|
- Get the full description of a specific job listing
|
|
|
|
## Commands
|
|
|
|
### Search job listings
|
|
|
|
```bash
|
|
bun run .agents/skills/linkedin-search/cli/src/cli.ts search --location "<place>" [flags]
|
|
```
|
|
|
|
Query syntax: phrase quoting not honoured; OR not verified.
|
|
|
|
Key flags:
|
|
- `--location <text>` / `-l <text>` — **required.** A LinkedIn place string, e.g. `"Mumbai, Maharashtra, India"`, `"Berlin, Germany"`, `"London, United Kingdom"`, or `"Remote"`.
|
|
- `--query <text>` / `-q <text>` — keyword search (title, skill, role). Recommended.
|
|
- `--jobage <days>` — posted within N days: `1`, `7`, `14`, `30`. Omit for all postings.
|
|
- `--jobage-minutes <n>` — posted within N minutes (sub-day precision, e.g. `30`). Conflicts with `--jobage` — pass only one.
|
|
- `--remote <mode>` — `remote`, `hybrid`, or `onsite` (workplace-type filter).
|
|
- `--page <n>` — page number (1-indexed, 10 results per page).
|
|
- `--limit <n>` / `-n <n>` — cap total results emitted (client-side).
|
|
- `--format json|table|plain` — default `json`.
|
|
|
|
### Fetch full job detail
|
|
|
|
```bash
|
|
bun run .agents/skills/linkedin-search/cli/src/cli.ts detail <id|url> [--format json|plain]
|
|
```
|
|
|
|
`id` is the job ID from `search` results (e.g. `4426311357`). You may also pass a full
|
|
LinkedIn `jobs/view/...` URL or a `urn:li:jobPosting:...` URN. Returns the full description,
|
|
seniority, employment type, job function, and industries.
|
|
|
|
## Usage examples
|
|
|
|
```bash
|
|
# Data engineer roles in Bengaluru, last 30 days
|
|
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "data engineer" -l "Bengaluru, Karnataka, India" --jobage 30 --format table
|
|
|
|
# Product manager roles in Berlin, remote
|
|
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "product manager" -l "Berlin, Germany" --remote remote --format table
|
|
|
|
# Any role, fully remote
|
|
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "paralegal" -l "Remote" --format table
|
|
|
|
# Engineer roles, remote, posted in the last 30 minutes
|
|
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "engineer" -l "Remote" --jobage-minutes 30 --format table
|
|
|
|
# Full details for a specific job
|
|
bun run .agents/skills/linkedin-search/cli/src/cli.ts detail 4426311357 --format plain
|
|
```
|
|
|
|
## Output formats
|
|
|
|
| Format | Best for |
|
|
|--------|----------|
|
|
| `json` | Default — programmatic use, passing IDs to `detail` |
|
|
| `table` | Quick human-readable scanning |
|
|
| `plain` | Reading a single job's full detail (`detail` command) |
|
|
|
|
All errors are written to **stderr** as `{ "error": "...", "code": "..." }` and the process exits with code `1`.
|
|
|
|
## Notes
|
|
|
|
- Data is from LinkedIn's public `jobs-guest` endpoints — no credentials required.
|
|
- Page size is fixed at 10 results per page.
|
|
- LinkedIn may rate-limit; the CLI retries 429/5xx with exponential backoff. Keep volume low (see ToS note above).
|
|
- Job IDs are numeric (e.g. `4426311357`) — pass them as-is to `detail`.
|