Skip to content

Application documents

kairos generate writes the documents for one job: a tailored resume (by default), a cover letter, a selection criteria response, or all three. Each one is fitted to its page range, and it uses only your own facts.

kairos generate <job-id>                          # tailored resume, PDF
kairos generate <job-id> --all --to "Vicky Q., Overseas Recruiting Manager"
kairos generate <job-id> -d cover-letter -f pdf -f md --note "referred by Lin Tang"
kairos generate <job-id> --pages 2 --intensity strong
kairos generate <job-id> -d criteria --criteria-file criteria.txt --word-limit 250

Files are saved to [documents] out_dir/<company>-<role>/ on the machine that runs the command, for example resume.pdf and cover-letter.md. A run will not write over files from an earlier run unless you pass --force.

Which roles and projects a resume shows

Before tailoring, Kairos picks the roles and projects to show (decision 0009). Each entry (a ### heading and the lines under it) is scored by the target's skills that its own text names: 2 points for a required skill, 1 for a preferred one. An entry that names none is left out. At least 2 projects and 1 role are always shown, and projects are ordered by score. Nothing is written in this step, so a resume still holds only your own words.

The run's message names each entry left out and why. Overrule the choice by part of an entry's heading:

kairos generate <job-id> --keep "Kairos" --drop "Wedding site"

Or see every entry and evidence story with its score first and tick the ones to use:

kairos generate <job-id> --all --pick

--pick lists the roles and projects (and, for a cover letter or criteria response, the evidence stories with the criterion each matches best), then asks for numbers such as 1,3-5 or none. Enter takes the proposal. The run shows exactly the ticked entries, with no minimum, and its letters cite only the ticked stories (decision 0014).

General resumes for a kind of role

A role profile holds the skills a kind of role asks for, counted from jobs you saved and analysed. A skill at least half of them require is required; one at least a quarter of them mention is preferred. A profile needs at least 3 analysed jobs, or a skills file.

Keep one stack per profile. "Backend" ads for Java, Go and Python ask for different skills, so no skill reaches half of them and the profile comes out thin. --skill counts only the jobs whose analysis names any of the given skills.

kairos roles build "Python Backend Engineer" --title backend --skill python --skill django
kairos roles build "Backend Engineer" --job 5683ec14 --job a1b2   # name jobs instead
kairos roles build "Go Developer" --skills-file go.toml          # write the skills
kairos roles show backend-engineer          # its skills, and every entry shown or not
kairos roles edit backend-engineer --keep "Kairos" --drop "Wedding site"
kairos generate --role backend-engineer --language zh

A skills file lists [[required]] and [[preferred]] skills, each with a name and an optional level (1–10), category and aliases, plus an optional keywords list.

Only a resume can be written for a role: a cover letter and a selection criteria response answer one employer. The files go to [documents] out_dir/role-<slug>-<language>/, or role-<slug>/ without --language. Sections that tailoring does not touch (education, the header, the section headings) stay in the base resume's language, so keep one base resume per language and mark the matching one as the base before a run.

Page ranges

Document Range
Resume, --pages 1 0.5 – 1 page
Resume, --pages 2 1.5 – 2 pages
Cover letter 0.5 – 1 page
Selection criteria 0.5 – 1 page; with --word-limit or --char-limit, up to 1 page

A document that cannot land in its range is not written, and the command exits with status 3 and says what to change. Kairos never pads a document with invented content. For example, a resume with too little material for two pages tells you to choose one page or add to the base resume.

Selection criteria

Selection criteria are an Australian format, so they are written in English only.

  • Which criteria. Without --criteria-file, Kairos reads up to 5 from the ad and keeps them for the next run. --max-criteria reads the ad again for that many. A criteria file has one per line; write (desirable) on a desirable one.
  • What fits. Every essential criterion is answered. Desirable ones are added one at a time while the response stays within one page, and only then does each answer grow, from 70 to 130 words.
  • How each answer reads. One sentence that claims the criterion, then where, what you did and the result. The heading is the ad's own wording.
  • The ad's limits. --word-limit and --char-limit are followed exactly and checked on every answer. They lift the half-page minimum, never the one-page maximum: if the essentials alone run over a page, the response is refused with the measured length.

Where the facts come from

  • Your base resume and your evidence library. Every number and claim must come from these. Before writing a letter, add your stories with kairos evidence import. A letter that states a number you have not given is rewritten once, then refused.
  • The ad. The letter may repeat the ad's names and terms, but never its numbers, so a figure in the ad is not passed off as yours.
  • Your profile. Kairos writes the work-rights sentence from [profile.fit] needs_sponsorship_in and [profile] visas, and the notice period from [profile] notice_period.
  • Kairos itself. The letter's frame is never written by the LLM: the date, the addressee (--to), the subject line, the sign-off ([documents] signoff) and your name, which comes from the base resume.
[profile]
notice_period = "four weeks"
visas = { AU = { name = "Temporary Graduate visa (subclass 485)", expires = "2027-06" } }

[documents]
signoff = "Kind regards"
out_dir = "~/Documents/Applications"
never_print = ["Acme"]            # names no resume, letter or response may print
hidden_entries = ["Wedding site"] # base-resume entries no document ever shows

never_print names are matched as whole words in any case. Anything that names one (an entry, a line, an evidence story) is removed before a model sees it, and every written document is checked for them. A hidden entry never appears in --preview or kairos roles show.

Why it works this way: decision 0008.

Drafting stories for criteria you have none for

A letter or criteria response needs one story per criterion. When a job asks for something your library has no story for, Kairos can draft one from your base resume:

kairos evidence draft <job>      # up to 3 drafts, essential criteria first
kairos evidence drafts           # the drafts waiting for you
kairos evidence accept <id>      # append to your evidence file and import it
kairos evidence ignore <id>
  • A draft uses only facts from one resume entry, and passes the same checks as an import and a letter: no new numbers or names, no buzzwords, nothing internal.
  • A criterion your resume shows nothing for is reported as a gap, never filled.
  • accept writes to the file you last imported, then imports it again; the file stays the source. It refuses when that file has changed since its import, so import your edits first. Edit the story there afterwards and import again to change it.

Why: decision 0012.