Two months into my job search, I set up a resume builder on Claude Code. The idea was straightforward: one tool, every new role, tailored output each time. No more rewriting the same sections from scratch.
It did not work the way I expected. The CV came back with details that were not mine, a professional summary that overstated things, and achievements that sounded plausible but did not reflect my actual experience. I spent more time editing the output than I would have writing from scratch.
I blamed the tool and moved on. ChatGPT for one application, Gemini for the next, Perplexity when I wanted a different angle. Each had strengths. None of them fixed the problem because the problem was not the tool. My prompts were too open-ended. I was asking for a tailored CV without telling Claude what tailored meant to me, what I refused to inflate, what needed to stay exactly as it was.
The learning happened gradually, across too many applications. The more specific I got about what I did not want, the better the output became. That lesson was overdue.
When I learned about Claude’s Cowork mode and, specifically, Skills, I wanted to apply that thinking properly. In Claude, a Skill is a folder of instructions, scripts, and resources that Claude loads dynamically to handle specialized tasks in a repeatable way. You define how you want things done once, and that context carries forward every time you run it.
Before building anything, I had a more immediate problem: I had lost track of my own job applications. Three months of searching and I could not reliably list what I applied to, when, or at what stage. I used Cowork to pull that entire backlog into a clean, structured summary. It took one task to set up, and the result filled in gaps I needed for other applications I was working on at the time.
Then I built the Skill.
One job description in. Six files out: a tailored CV with achievement-focused bullets matched to the role, a cover letter, a LinkedIn cold message to the hiring manager, a direct email, a follow-up for after the silence, and an interview preparation document. All editable, all in one prompt.
The interview prep file was the part I had not originally planned for, and it became the most useful. I added it to answer a specific question: do the likely interview questions for this role actually match what I have done in my career? Going through those questions against my own experience gave me a clearer read on fit than any gut feeling would. A few applications I felt more confident about after seeing them. A couple made me pause before investing more hours. That signal alone is worth including every time.
The output still needs a final review. There are details to verify, phrasing to adjust, the occasional sentence that does not sound like me. That will always be true, and it should be. What has changed is the starting point. The first draft arrives close to done rather than needing a structural rebuild.
I am still refining the Skill as I use it more. There will be gaps I notice only after a few more applications, things I keep having to fix that should be handled automatically. That is part of the process.
But going from a job description to a complete, editable application package in a single prompt is a genuinely different experience from rewriting the same three paragraphs for the fifteenth time. Three months of searching, and the most useful thing I learned was how to give better instructions. The tools were capable all along.
Next JD, one prompt, full package. That is where I am now.