Ayobami Adegoke
8cbab6823e
normalizeId took the first 6+-digit path segment from ANY URL, so a Greenhouse or Lever apply link - the kind a posting's own page hands out and a user pastes back into detail - was reduced to that number and the handler fetched jobPosting/<number> from LinkedIn: whatever job carried that id came back with exit 0, or NOT_FOUND if none did, never an error about the input. Driving the real handler with a stubbed fetch, https://boards.greenhouse.io/acme/jobs/4567890 requested .../jobPosting/4567890. Every other portal CLI rejects an off-host detail URL with BAD_ID (the #447 shape); linkedin was the one still trusting the digits. Parse URLs for real: a linkedin.com host (apex or any subdomain, scheme optional) plus a /jobs/view/<slug->id path yields the id; other hosts, look-alike and userinfo hosts, and linkedin.com profile or search URLs exit 1 with the stderr-JSON BAD_ID contract before any request. Bare ids, URNs, and slash-free title slugs are unchanged. Four new normalizeId cases and a new detail-input.test.ts that drives runDetail and the CLI with fetch stubbed; five cases fail on the old pattern.
linkedin-cli
CLI for searching jobs on LinkedIn's public job listings, for any country/region (and remote), across any sector.
Data source: LinkedIn jobs-guest endpoints (seeMoreJobPostings/search and jobPosting/<id>).
Authentication: None required.
Dependencies: None (plain bun + fetch). bun install is optional and only pulls dev type defs.
Personal use only. This uses LinkedIn's public job pages; automated access is against LinkedIn's Terms of Service. Keep volume low, don't use it commercially or for bulk data collection, and run it on your own responsibility.
Installation
cd .agents/skills/linkedin-search/cli
bun install # optional — only installs TypeScript dev types
The CLI runs without any install because it has zero runtime dependencies.
Commands
| Command | Description |
|---|---|
search |
Search for job listings (--location required) |
detail |
Fetch full detail for a single job listing |
search accepts --format json|table|plain (default json); detail accepts --format json|plain.
All errors are written to stderr as { "error": "...", "code": "..." } with exit code 1.
Quick examples
# Software roles in Hyderabad, last 7 days
bun run src/cli.ts search -q "backend engineer" -l "Hyderabad, Telangana, India" --jobage 7 --format table
# Design roles in London
bun run src/cli.ts search -q "product designer" -l "London, United Kingdom" --format table
# Fully remote
bun run src/cli.ts search -q "technical writer" -l "Remote" --remote remote --format table
# Full detail for one job
bun run src/cli.ts detail 4426311357 --format plain
See ../SKILL.md for the full flag reference and the Terms-of-Service note.
Search flags
| Flag | Alias | Description |
|---|---|---|
--location |
-l |
Required. Place string, e.g. "Mumbai, Maharashtra, India", "Berlin, Germany", "Remote". |
--query |
-q |
Keywords (title / skill / role). Recommended. |
--jobage |
Posted within N days: 1, 7, 14, 30. |
|
--remote |
remote | hybrid | onsite. |
|
--page |
1-indexed page (10 results/page). | |
--limit |
-n |
Cap results emitted. |
--format |
json | table | plain. |