linkedin-jobs
LinkedIn Jobs
Requires BRIGHTDATA_API_KEY environment variable.
Two operations: search (discover jobs by criteria) and fetch (get a specific job by URL or ID). Both return full raw JSON.
Search jobs
Cost: ~$1.50 per 1k records. Always use --limit to control costs. Default limit is 25.
Script paths below are relative to this skill's directory.
python3 scripts/search_linkedin_jobs.py "software engineer" \
--location "United States" \
--remote Remote \
--time-range "Past month" \
--job-type Full-time \
--experience "Mid-Senior level" \
--limit 25
keyword and --location are required. All other flags are optional.
| Flag | Valid values |
|---|---|
--limit |
Max results (default 25). Keep low to control costs. |
--remote |
Remote | On-site | Hybrid |
--time-range |
"Past 24 hours" | "Past week" | "Past month" (default) |
--job-type |
Full-time | Part-time | Contract | Temporary | Volunteer |
--experience |
"Entry level" | Associate | "Mid-Senior level" | Director | Executive | Internship |
--company |
Company name string |
--country |
Country code (e.g. US, GB) |
Returns an array of job objects.
Fetch a specific job
Takes ~30 seconds. Accepts a full LinkedIn URL or numeric job ID.
python3 scripts/fetch_linkedin_job.py 4358573391
python3 scripts/fetch_linkedin_job.py "https://www.linkedin.com/jobs/view/4358573391"
Returns a single job object.
Key output fields
job_posting_id, job_title, company_name, job_location, job_summary, job_posted_date, job_employment_type, job_seniority_level, job_num_applicants, base_salary, is_easy_apply, application_availability, url, apply_link, job_description_formatted.
More from its-a-unixsystem/skills
humanizer-german
|
3gitkraken-cli
Use the GitKraken CLI (gk) for git operations instead of raw git/gh commands. Activate this skill whenever performing git operations like committing, creating PRs, pushing, resolving conflicts, explaining changes, generating changelogs, or managing branches and work items. Even if the user doesn't mention "gk" or "GitKraken" explicitly, use gk commands for any git workflow where gk has a matching command, falling back to raw git only for operations gk doesn't cover.
3gk-cli
Use the GitKraken CLI (gk) for git operations instead of raw git/gh commands. Activate this skill whenever performing git operations like committing, creating PRs, pushing, resolving conflicts, explaining changes, generating changelogs, or managing branches and work items. Even if the user doesn't mention "gk" or "GitKraken" explicitly, use gk commands for any git workflow where gk has a matching command, falling back to raw git only for operations gk doesn't cover.
1