DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to record application outcomes and draft follow-ups with AI Job Search

Log interviews, offers and silence, then get drafted follow-ups for applications that went quiet.

Who it is forA job seeker with several open applications who loses track of which ones need a nudge or a record update.

The problemOpen applications go quiet and outcomes are scattered across inboxes and notes, so follow-ups get missed.

The outcomeEach application archived with its outcome, a list of stale applications, and short follow-up drafts you can send yourself.

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

  1. gh repo fork MadsLorentzen/ai-job-search --clone
  2. python3 tools/install_portal_clis.py
  3. Run claude inside the repo and record a result with /outcome for each application that has changed status.
  4. Run /outcome followup to list open applications that have gone quiet, using the default 10 days.
  5. Review each drafted follow-up and send it yourself, since the command only drafts and never sends.

Prompt for your agent

In the ai-job-search repo, run /outcome followup. Expect a list of open applications quiet for 10 days or more and a short draft for each, using only claims from materials you already submitted. Verify that each draft contains no new claims and that no draft was sent.

Caveat. The follow-up drafts are limited to at most two per application, and the README says the command never sends anything, so the sending step is yours.

Share: 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