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

How to get daily alerts when shortlisted companies post a match with Jobradar

Set a shortlist of companies and receive email plus desktop alerts when a scored opening clears your threshold.

Credentials. Your LLM key and Gmail App Password are stored in run.sh, so keep that file private and do not commit it to a public repo.

Who it is forA job seeker with a few target employers in mind who is tired of refreshing career pages each morning.

The problemCareer pages change without notice, and checking several boards every day takes time and still misses new postings.

The outcomeYou receive a daily alert, by email and desktop notification, only when a shortlisted company opens a role that scores at or above your minimum.

What you need first

  • Python 3.11 or newer
  • A Mac, because the scheduled runs use launchd
  • Your resume as a PDF file
  • An LLM API key for an OpenAI-compatible endpoint (the default is xkiro)
  • A Gmail App Password, which needs 2FA turned on for the account first

Steps

  1. Run git clone https://github.com/suvamneog/jobradar.git and then cd jobradar.
  2. Run ./install.sh to set up the project and register the launchd jobs.
  3. Put your resume PDF in the folder and set resume_path to it in config.yaml.
  4. Run cp run.example.sh run.sh, then fill in your LLM key and Gmail App Password.
  5. Set alerts.companies and alerts.min_score in config.yaml, then run ./run.sh test to confirm the test email arrives.

Prompt for your agent

In the jobradar repo, set up the project, put <resume.pdf> in place as the resume, and set alerts.companies in config.yaml to <company list>. Run ./run.sh test and confirm a test email is sent, then report the result. Verify that the test email arrives in the inbox before reporting success.

Caveat. Alerts only run on a Mac because the daily schedule is registered through launchd during install.

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