sensitive. Your name, contact details and employment history are written into tracked files, so keep the fork private if you are not contributing back.
Who it is forA job seeker who has found a specific posting and needs a tailored CV and cover letter without writing them from scratch.
The problemRewriting a CV and cover letter for every posting takes hours and is easy to do inconsistently.
The outcomeA fit evaluation, a drafted CV and cover letter reviewed by a second agent, and a revised final output ready for your review.
What you need first
- Claude Code (Pro, Max, Team subscription or Anthropic API credits)
- Python 3.10+
- Bun
- A LaTeX distribution with lualatex and xelatex
- git and the gh CLI to fork the repo
- Your CV, past applications and other career documents to load into /setup
Steps
gh repo fork MadsLorentzen/ai-job-search --clonepython3 tools/install_portal_clis.py- Run
claudeinside the repo, then run/setupand fill in your profile from your documents. - Run
/apply https://jobindex.dk/job/1234567with the posting URL, or run/applyand paste the job description if the URL cannot be fetched. - Read the evaluation, the drafted CV and the cover letter, and edit anything that is wrong before you send it.
Prompt for your agent
In the ai-job-search repo, run /apply on the posting at <posting URL>. Expect a fit evaluation, a tailored LaTeX CV and cover letter, and a reviewer critique with the final revised output. Verify that every claim in the CV and cover letter appears in your own profile files before sending.
Caveat. The README says postings are untrusted input and that agentic defenses are not a sandbox, so skim what was fetched and written before you send anything.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page