Keep a job-search pipeline in files across Claude Code sessions
At a glance
A job seeker built a Claude Code workflow to collect job descriptions, tailor a resume and inspect the application funnel. This workflow is listed under Job search, Coding.
- Agents / tools
- Claude
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Clone the author’s Super Tobi repository, create and activate a Python virtual environment, and install the listed `rich`, `httpx`, `requests` and `playwright` packages. Replace the example identity in `CLAUDE.md`, edit the settings and create the life-systems map from its template; open Claude Code and run `/status`. 2) Run `/apply jobs` to scan career pages and store job descriptions in the shared career files. 3) Use `/apply jobs --tailor` to read a stored description, extract role keywords and save a tailored resume. Review the generated resume against your actual experience. 4) Run `/analytics` to inspect the discovered, applied, response and interview stages using the shared application data.
How it went
For one ML Engineer posting, the author reports that his own resume-matching script scored the resume at 38% before tailoring and 84% afterward.
Worth knowing
The score is the author’s tool’s matching score, not evidence of a hiring outcome. The setup may need configuration and access appropriate to the sources used.