Case study · Tooling
Job-hunting with Claude Code skills.
Three skills that handle the mechanical work — finding, scoring, importing, drafting — so the human bit (judgement, follow-up, the actual conversation) gets all the attention.
- Role
- Builder
- Stack
- Claude Code · Playwright · Supabase
- Status
- Iterating weekly
- Year
- 2026
Why
The hardest part of a job search isn't the writing — it's deciding which roles are worth the writing. Most job-hunt tools give you more noise. This one removes it.
The skills don't apply for jobs. They just make sure I never apply for the wrong one.
The three skills
job-search opens LinkedIn in a real browser via Playwright, works through the results, scores each role against my profile, and imports new matches directly into the Pi job tracker — skipping anything already in there. One command, a full LinkedIn sweep, zero copy-paste.
job-import takes any job posting URL — LinkedIn, Jobserve, CWJobs, Totaljobs, Adzuna — scrapes the details, scores fit, and adds it to the tracker. Useful when something lands in my inbox or gets shared on Slack.
job-cover works through tracker entries that are missing cover notes, reads the JD and my profile, and drafts tailored outreach for each — referencing something specific about the role rather than producing a template.
What's still rough
The scoring prompt is too generous when a role sounds like a fit but the team-shape or remit is wrong. The next iteration will weight leadership context and actual delivery scope harder than job-title keywords. The cover drafts also want a tougher edit pass — they're good but slightly too long.
What it gave back
A much shorter list of higher-quality conversations, and the mental space to actually prepare for them. The job hunt becomes a workflow instead of a weight.