Drop in a job link. Get an ATS-ready CV and cover letter, tailored to the role, scored honestly, and written only from your real experience. Local to your machine, built from your facts.
It reads the ad the way an employer wrote it, then builds each piece around the parts of your history that genuinely match.
A clear number out of 100 with a breakdown of where you match and where you fall short. No flattery. A stretch is called a stretch.
Tuned to this role, in your own voice, leading with your strongest matches and the ad's real keywords, only where you truly have them.
A researched salary range for your role and city, plus notice and work-permit fields marked clearly for you to fill in.
Two passes strip AI-sounding filler and over-the-top hype, so the writing reads human and quietly confident.
ATS-styled Word files land in a final/ folder, ready to upload. No Word? You get a clean printable page instead.
A simple board tracks every application from drafting to interview, so nothing slips through the cracks.
The toolkit is a set of small, focused skills that hand work to each other. Hover or tap a step to see what it does. A job ad goes in one end; a finished, cleaned, exported application comes out the other.
Each skill does one job and passes the result on. Together they take a single job link all the way to ready-to-send Word documents, only ever using your real experience.
The toolkit ships blank. You fill in your real facts once, and every word it writes traces back to them. If a job wants something you do not have, it tells you, rather than making it up.
Before a person sees your CV, an Applicant Tracking System reads it as plain text and looks for the ad's exact words. Beautiful layouts often confuse it, and you are filtered out before page one. This toolkit stays clean to the eye and readable to the machine.
Never used a tool like this? Follow the steps in order. Each one shows exactly what to type. A "terminal" is the text window on your computer: Terminal on Mac, PowerShell on Windows. Copy a line, paste it in, press Enter.
These are the pieces the toolkit builds on. Pick your operating system and run the lines for it. You only do this once.
# 1. Homebrew, the installer that fetches the rest (paste, press Enter, follow prompts)
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"# 2. Git (usually already there) + Node.js + Pandoc
brew install git node pandoc# 3. Claude Code, the app that runs the toolkit
curl -fsSL https://claude.ai/install.sh | bash# Run these in PowerShell. Winget ships with Windows 10/11.
# 1. Git + Node.js + Pandoc
winget install Git.Git OpenJS.NodeJS JohnMacFarlane.Pandoc# 2. Claude Code, the app that runs the toolkit
irm https://claude.ai/install.ps1 | iex# 3. Close and reopen PowerShell so the new tools are found.# Debian / Ubuntu. For other distros use your package manager.
# 1. Git + Node.js + Pandoc
sudo apt update && sudo apt install -y git nodejs npm pandoc# 2. Claude Code, the app that runs the toolkit
curl -fsSL https://claude.ai/install.sh | bashWhat each is for: Git fetches the toolkit, Node.js powers some helpers, Pandoc turns your CV into a Word file, and Claude Code is the app you talk to. Pandoc is optional: without it you still get a clean printable page.
Open your terminal and check it installed, then start it. The first time, it opens your browser to sign in with a Claude account (Pro/Max) or an Anthropic API key. You only log in once.
claude --version # should print a version numberclaude # starts it, opens the browser to log inWith Claude Code running, type these two lines, pressing Enter after each. The first tells it where the toolkit lives, the second installs it. If the new commands do not appear, type /reload-plugins.
/plugin marketplace add mcmespinaa/job-application-toolkit/plugin install job-application@job-application-toolkitThis makes the folder where your applications will live. Use any path you like. It is safe to run again and never overwrites anything you have filled in.
/job-application:job-setup ~/Documents/Job ApplicationsOpen the new folder in any text editor. In 00_master/master-cv.md replace every [FILL IN] with your real information, and set your tone in voice.md. To teach it your style, drop old CVs and letters into _archive/ and run the mine command. If the archive is empty, just skip it. It invents nothing.
/job-application:job-setup --mine-archive # optional: learn from your past applicationsCopy a job ad's link and run the command below. If the page is behind a login, it will ask you to paste the text or a screenshot. When it finishes, you get a folder with your CV, letter, form answers, and ready-to-upload Word files, plus a short "before you submit" checklist. Read it, fill the blanks, and send.
/job-application:job-application https://link-to-the-job-adAfter setup, every future application is just this one line.
Everything works without these. Add them later if a cloud copy or a visual board would help. Nothing here is required, and nothing changes where your local files land.
Have each CV and cover letter also saved as a Google Doc in a tidy Job Applications/<Company>/ folder on your Drive. Google Drive is a Claude account connector, so you sign in once and it works everywhere you use that account, including VS Code and the terminal.
claude mcp listOnce connected, the toolkit syncs automatically on each run. Skip it for one run with --no-drive. Your documents always land in your local final/ folder regardless. This only adds a cloud copy in your own Drive.
Your workspace is plain text, so it opens directly in Obsidian. With the Kanban community plugin, Applications Board.md becomes a drag-and-drop board from drafting to interview.
brew install --cask obsidianwinget install Obsidian.Obsidian# download the AppImage / .deb from obsidian.md, or:
flatpak install flathub md.obsidian.ObsidianThe vault is local and yours. Nothing syncs anywhere unless you set up Obsidian Sync yourself.
This page is the quick start. For the complete reference, the method behind it, or a hand when something does not work, here is where to look.
The complete README: every command, every option, the troubleshooting table, and the file-by-file walkthrough. The best place to start after this page.
Open the README ↗ ◰UnderstandWhy the workspace is shaped the way it is. The Integrated Context Method is what keeps the toolkit both tailored to each job and honest to your real history.
Read the method ↗ ❂AskHit a snag, found a bug, or want a feature? Open an issue on GitHub. Contributions and ideas are welcome, it is open-source and built in the open.
Open an issue ↗Hi, I'm Maria. I built this toolkit, and it is free, with no email and no sign-up, and it always will be. If it saved you time or got you a callback, you can say thanks with a coffee. It genuinely means a lot.
☕ Buy Maria a coffee