Want to access all premium content?

Become a paying subscriber to get access to all courses, guides like this, prompts and skills library, and $500+ worth of AI tools.

career-ops is a free, open-source job-search tool that works inside Claude Code. Give it a job ad and it compares the requirements with your CV, assigns a score from 1 to 5, identifies gaps, and helps prepare a tailored CV.

You review the documents and submit applications yourself. career-ops doesn’t send them.

This week-long plan covers installation, profile setup, five job reviews, CV improvements, and one application. You’ll need Claude Code with a paid Claude plan, Node.js, and your current CV.

Step 1: Install career-ops. Monday: install the project and check the setup.

Step 2: Teach it your CV. Tuesday: share your experience, preferences, and work rights.

Step 3: Score five live jobs. Wednesday: compare five roles against your profile.

Step 4: Fix the gaps. Thursday: improve weak wording and add evidence you already have.

Step 5: Tailor and track. Friday: prepare your documents, apply, and record the result.

Step 1: Install career-ops

On Monday, open Terminal in your projects folder and run:

npx @santifer/career-ops init

The command creates a career-ops folder containing the project.

If Terminal can’t find npx, install Node.js from nodejs.org, then reopen Terminal.

Enter the new folder:

cd career-ops

Install Chromium, which the project uses to generate PDFs:

npx playwright install chromium

Run the setup check:

npm run doctor

Look for a passing Node.js check requiring version 22.13 or newer, plus this billing message:

Billing source: no API key in the environment

If the check detects an API key, resolve the billing configuration before continuing. The supplied setup warns that an environment key can route usage to separately billed API access. Remove the relevant export from your shell profile if you intend to use your plan, restart Terminal, and run /login in Claude Code.

Four missing setup files are expected at this stage. The next step creates them through chat.

Start Claude Code:

claude

Enter /career-ops without any additional text. Check that it displays the available modes, from pipeline through update.

Step 2: Teach it your CV

On Tuesday, give career-ops the information it will use to assess jobs:

❝

Set me up. Here is my CV: [paste your CV text] Roles I want: [for example, junior data analyst or marketing coordinator] Where I can work: [city, country, or remote] Lowest salary I'd accept: [amount] Hard no's: [for example, commission-only, unpaid trial tasks, 5 days in the office] Work rights: [countries where I can work without sponsorship] Score me strictly. Only use experience that is in my CV, and tell me when a claim has no proof behind it.

Allow a few minutes for setup. Claude repeats the doctor check until the required files pass.

Be specific about work authorization. A role requiring rights you don’t hold can score as low as 1.0. A “Remote, US only” listing still has a location restriction.

Check the saved profile:

❝

Summarize what you know about me in five lines: roles, location, salary floor, hard no's and work rights.

Correct any missing or inaccurate details. The README notes that early assessments become more useful as you supply evidence of your experience.

Step 3: Score five live jobs

On Wednesday, collect five current ads for roles related to your experience. Submit them individually:

/career-ops https://link-to-the-job

A full run produces an A–H report, a score from 1 to 5, a PDF, and a tracker entry. Block G reviews the posting’s legitimacy separately from the fit score.

In Alvaro’s demo test, each full run took 7 to 10 minutes.

For a quicker first pass, use /career-ops triage with the link. It returns an initial go-or-no-go assessment without saving files. You can also paste the ad’s text if its page is slow or inaccessible.

Ask for a shorter view of the full report:

❝

Show me only the top of the report for [company]: the score, the decision, the top 3 strengths and the top 3 gaps. Keep it to one screen.

Result

How to use it

4.0 or higher

Keep the role on your Friday shortlist

Below 4.0

The README recommends skipping it; review the gaps

Conditional decision

Resolve the stated question, such as salary or hours, before deciding

Warning in block G

Investigate the posting before proceeding, regardless of its score

If no role reaches 4.0, review why. Alvaro’s demo CV scored a maximum of 3.8 across eight jobs in the initial test.

After reviewing five roles, request a comparison:

❝

Put my five scored jobs in one table: company, role, score, top gap, and apply or skip.

Step 4: Fix the gaps

On Thursday, look for weaknesses that appear across several reports:

❝

Read my five reports in the reports folder. List the gaps that came up in more than one job, ranked by how often they came up. For each gap, tell me if I can fix it this week by rewording my CV, by adding proof I already have, or only with new experience.

Start with unclear wording and missing evidence. Give Claude a real example to add:

❝

Add this to my CV: [a real example with a number, for example "ran the shop's Instagram for 6 months, grew it from 300 to 1,100 followers"]. Use only what I wrote here.

Rescore your strongest job after updating the profile.

In Alvaro’s test, adding two supporting examples about short videos and LinkedIn posts raised one role’s score from 3.8 to 4.2. That reflected additional evidence in the profile, not new experience gained overnight.

Keep every addition accurate. For gaps requiring training or practical work, see Use cases #1 and #2.

Step 5: Tailor and track

On Friday, select your strongest suitable role and request its CV:

/career-ops pdf

The command creates a tailored PDF in the output folder. Confirm that it uses the intended job description.

Next, prepare the cover letter:

/career-ops cover

The workflow first asks why you want the role, what problem you would address, how you would start, and which tone you prefer. It then asks which gaps to discuss.

Review the draft in chat before approving the PDF.

Check every claim against your actual experience. Remove unsupported details before submitting the application on the company’s website.

Open the tracker:

/career-ops tracker

After applying, tell it:

Mark [company] as applied.

The tracker records the status and sets the first follow-up a week later. When you receive a response, use /career-ops outcome to record it.

Use cases

Use case #1: Assess a course before buying it

Check whether a course addresses the gaps in your target roles:

/career-ops training https://link-to-the-course

The assessment includes a recommendation and may suggest cheaper or free alternatives. Compare its reasoning with Thursday’s gap list.

Use case #2: Choose a portfolio project

Review a project idea before committing your time:

❝

/career-ops project A two-week project: I clean a public sales dataset and build a dashboard that answers three business questions. Would this help me get the roles in my profile?

Use the response to judge whether the project would demonstrate skills your target jobs require.

Use case #3: Prepare interview answers

Ask for practice questions grounded in the role and your experience:

❝

Using the report for [company name] and my CV, write the five interview questions they are likely to ask, with a short STAR answer for each from my own experience.

Fill in any bracketed details yourself. Read the answers aloud and remove examples or claims you cannot support.

Use case #4: Draft a hiring-manager message

Run:

/career-ops contacto

The mode searches for a relevant hiring manager, recruiter, or team member and drafts a LinkedIn note. When it cannot verify someone’s identity, it should explain where you can look.

Check the recipient yourself. Keep the draft under the guide’s 200-character target, then send it from your own account.

Limitations

The project is free, but the setup described here uses Claude Code through a paid Claude plan. Check for an ANTHROPIC_API_KEY in your environment if you intend to use subscription access rather than API billing.

Fit scores are recommendations. They do not predict an offer, and a higher score does not establish that a CV is accurate. Review every document and practice answer for invented experience.

Alvaro’s full report runs took 7 to 10 minutes each. Allow time for both generation and review.

Built-in job discovery focuses on technology companies and platforms such as Greenhouse, Lever, and Ashby. Paste job ads directly when discovery does not cover your field or location.

The workflow stores your CV locally and sends its contents to the AI provider used for processing. Follow job-site terms and review each application individually.

The original test used career-ops 1.39.0 on a Mac on November 10, 2026. Commands and behavior may differ in later releases.

Closing

Begin with one role you are considering. Read its assessment, check the gaps, and decide whether it deserves an application.

Then work through the five-job plan. Use the 4.0 threshold as the project’s screening recommendation and apply your own judgment before submitting.

See you in the next one :)