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

How to generate an offline dashboard of your pipeline with AI Job Search

Turn your tracker and application archives into a self-contained HTML report you can open offline.

Who it is forA job seeker with many tracked applications who wants a visual overview of the funnel and outcomes.

The problemA spreadsheet of applications is hard to read at a glance, and funnel patterns stay hidden.

The outcomeA single HTML file with stat cards, charts and a filterable applications table that opens in a browser without internet.

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 add at least one entry with /apply or /outcome.
  4. Run /html-report to build the dashboard from job_search_tracker.csv and the application archives.
  5. Open the generated HTML file in a browser and filter the table to check that the counts match your tracker.

Prompt for your agent

In the ai-job-search repo, run /html-report. Expect a self-contained HTML dashboard built from job_search_tracker.csv and the application archives. Verify that the stat card totals match the row count in job_search_tracker.csv.

Caveat. The dashboard reflects only what is in your tracker and archives, so re-run /html-report after each /apply or /outcome to keep it current.

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