Job hunting has an annoying loop: read the posting, rewrite the CV, work out So I built jobhunt: eleven skills for the coding agent you already use ▶️ 22-second demo · 🌐 Site · 💻 Code Here's the idea in one picture. The same six lines from one profile, against Most readers stop after the first sc
Job hunting has an annoying loop: read the posting, rewrite the CV, work out So I built jobhunt: eleven skills for the coding agent you already use ▶️ 22-second demo · 🌐 Site · 💻 Code Here's the idea in one picture. The same six lines from one profile, against Most readers stop after the first screenful. On the CV you send everywhere, You say something like: prepare an application for https://boards.greenhouse.io/acme/jobs/42 and it runs, in order: Your profile, once. The first run reads your CV into profile.yaml and stops so you can check it. A model just read your career, so you approve it once and everything after is built on facts you agreed to. The posting. It reads the page in your own browser and pulls out what the job actually asks for. Fit, before. Every requirement is checked against your own work: what backs it, and what's a real gap. A CV for this job. Your strongest lines for this posting move to the top. Fit, after. The same check again, so you can see what the tailoring bought you. Cover letter and PDFs. The letter is written in the posting's language, and you get PDFs of both. Critique. What's still weak, before you send. Outreach. Who to message (alumni first, because they're the ones who reply), the LinkedIn searches that find them, and a draft note. Everything lands in one folder per job. Each skill also works on its own: "how Each skill is two halves: SKILL.md, the judgement half. It holds plain-language instructions for the model: what to read, what to decide, when to stop and ask. A small Python script, the exact half. Argv in, JSON out. It does the scoring, the ordering and the PDFs: anything that should be the same every time. That split is why there's no API key. Your agent is the model, so whatever A CV tool built on a language model has one obvious failure: inventing things. Roles come from your profile. The CV is assembled from roles picked out of your profile, not written from scratch. Added skills are dropped. A skill the model adds that your profile doesn't list is removed, and you're told. Unbacked claims are flagged. If the tailored CV still names something your profile doesn't back, the after score says so: claimed but not evidenced. It also never applies, never logs in and never sends anything. LinkedIn walls Inside Claude Code: /plugin marketplace add mohamedaminehamdi/job-hunter /plugin install jobhunt@jobhunt Any other agent, on macOS or Linux: curl -fsSL https://raw.githubusercontent.com/mohamedaminehamdi/job-hunter/main/install.sh | sh Or download the folders from the site One-click apply on the boards that allow it, jobs found for you, and jobhunt is free for your own job search, and the code is on GitHub. If you try I built jobhunt with Claude Code, and drafted this post with Claude's help.
Key Takeaways #
- •Job hunting has an annoying loop: read the posting, rewrite the CV, work out So I built jobhunt: eleven skills for the coding agent you already use ▶️ 22-second demo · 🌐 Site · 💻 Code Here's the idea in one picture
- •This story was reported by Dev.to , covering developments in thedev space.
- •AI advancements continue to reshape industries — read the full article on Dev.to for complete coverage.
📖 Continue reading the full article: