Who it is forA job seeker running many applications at once who loses track of status, deadlines and interviews.
The problemApplications spread across email, spreadsheets and job boards make it hard to see what needs follow-up.
The outcomeA board and table of every application from draft to offer, and a dashboard showing your funnel for the last 30 days, 90 days or all time, with a week-by-week chart and upcoming interviews.
What you need first
- Docker Desktop on macOS or Windows, or Docker Engine with the Compose plugin on Linux, plus about 2 GB of free memory
- A terminal: Terminal on macOS, a Linux shell, or WSL on Windows
- An AI model: a local one through Ollama or LM Studio, or a hosted OpenAI-compatible API, Anthropic or Mistral
- Your career history (or an existing resume as PDF, Word or Markdown) to build the profile from
Steps
- Start Dossier with
docker compose up -dand sign in at http://localhost:3000 - Create an application for each job from New application, or from a posting you saved in Find jobs
- Move each application across the board as its status changes, or edit it in the table
- Open the dashboard and pick the funnel range you want: last 30 days, 90 days or all time
- Export your data as one file from the app regularly, using its export feature
Prompt for your agent
Using the AienTech/dossier repo, after it is running at http://localhost:3000, read the applications on the board and the dashboard funnel for the last 30 days. Return a short list of applications with a status and the next interview date. Verify the counts match the number of applications shown on the table view.
Caveat. Dossier is desktop only and single user, so it works best in a laptop or desktop browser with one password and one profile.
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