Ayobami AdegokeandNavakanth Reddy Dumpa
3d296448bd
* feat(linkedin-search): add active status verification for job postings * fix(linkedin-search): scope closed-posting detection to the top card, pin with tests (#280) The first version matched five markers against the whole document, so recruiter boilerplate quoting 'no longer accepting applications' in a description flagged a live job CLOSED. Detection now stops where the description markup begins and matches only the two markers real closed pages carry (closed-job__flavor and the banner text, verified against live guest pages); the three speculative phrases are dropped. Four new fixture tests pin both directions plus the two description false-positive cases - the false-positive pair fails on the unscoped version. * feat(scrape): mark closed-at-source LinkedIn postings expired, never drop (#280) /scrape Step 2 now consumes linkedin-search detail's isActive: a job whose posting page renders the closed banner is written to seen_jobs.json with status expired rather than silently dropped, per the /rank marking pattern - the fix for the ghost-jobs class in #331. isActive: true is documented as absence of the banner, not proof the posting is open. --------- Co-authored-by: Navakanth Reddy Dumpa <navkanthr@gmail.com>
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. |