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.
73
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
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-guestendpoints are global and the HTML parsing is country-independent; only the--locationyou pass changes per market.
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.
bun run .agents/skills/linkedin-search/cli/src/cli.ts search --location "<place>" [flags]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.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, industries, and apply link.
# 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| 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.
jobs-guest endpoints — no credentials required.4426311357) — pass them as-is to detail.5c423b4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.