← ClaudeAtlas

job-hunt-researcherlisted

Use this skill when the user wants to research and compile a verified list of open job positions — e.g. "find me junior developer jobs in X", "search for open positions at Y companies", "who's hiring for Z near me". Systematically searches job boards AND company career pages directly, verifies every single listing before including it (never fabricates a URL), tracks progress in a resumable file so long multi-round searches survive interruptions, and outputs a filterable, checkbox-trackable local HTML job board from a plain JSON file. Also use when the user wants to expand or continue a job search that already has a tracker file and/or a data/jobs.json from a previous run of this skill.
Polykarp-bit/job-hunt-researcher · ★ 0 · Data & Documents · score 62
Install: claude install-skill Polykarp-bit/job-hunt-researcher
# Job Hunt Researcher A repeatable process for building a **verified**, **de-duplicated**, **resumable** list of job openings — plus a zero-backend HTML viewer to browse and track progress against it. Born out of a real, multi-round job search; this file is what that process looks like distilled into something you can run again for any role, any region. See `examples/demo/` for a (fictional) look at the viewer output. ## Before you start: pin down scope with the user Don't guess these — ask, or infer from the conversation, and write them into the tracker file so every later round inherits them: - **Role/field** (e.g. junior software developer, KI/AI developer, data analyst) - **Seniority level wanted** — almost always "no senior/lead/head/manager titles," but confirm the *floor* too (fresh graduate vs. some experience OK vs. explicitly welcomes career changers) - **Region and radius** (a city name is not enough — get a rough km radius or a list of acceptable neighboring towns) - **Hard exclusions** — common ones: apprenticeships (Ausbildung), internships/working-student roles, retraining "bootcamp" programs disguised as jobs, a specific specialization the user does *not* want (e.g. "not IT security") - **Output location** — where `data/jobs.json` and the tracker file should live in the user's project Re-confirm scope changes explicitly stated mid-search (e.g. "actually leave the security roles that are already in there, just stop adding new ones") — write the update