{"slug": "oriko-cli-create-your-cv-in-the-terminal-with-builtin-agent-support", "title": "Oriko CLI – Create your CV in the terminal with builtin Agent support", "summary": "Honeyglass released Oriko, a command-line tool that lets an AI agent tailor a single master CV to individual job postings by reordering, hiding and shortening existing content without inventing new claims. Oriko installs via a curl script that also deploys an agent skill for Claude Code and other agents through the skills CLI, previews every page in the terminal, and outputs a Word file for Google Docs or a PDF via LibreOffice. The tool stores one small version file per job posting, so a job added to the master CV once appears in every version, and its CI runs a supply check that admits packages only from an allow list and only once a new version is three days old.", "body_md": "oriko makes a fitting version of your CV for every job you apply to. You write your CV once, with your jobs, skills, languages and contact details. When you find a job you like, you give the posting to an AI assistant, in plain words and in any language. The assistant fits your CV to it: it moves the matching skills up, hides what does not help and shortens long lists, and it never invents anything. You see the result right away as a preview of every page in the terminal, and you get a Word file that you open in Google Docs and save as PDF, or the PDF itself when LibreOffice is installed.\n\n- 🤖 **Built for AI assistants** : oriko is a command-line tool an AI agent can drive on its own,\nfrom the first look at your CV to the finished file.\n- 🧱 **Clean pages** : a job never breaks across two pages. If it does not fit, it moves to the next\npage as a whole.\n- 🎯 **One CV, many versions** : each job posting gets a small version file. Add a new job to your\nCV once, and every version has it.\n- ✅ **Honest by design** : a version only hides, reorders and shortens what you wrote. New claims\nneed your yes.\n- 👀 **Preview before you build** : see every page in the terminal, and how full it is.\n- 🌍 **Several CVs** : one per language or per person, side by side.\n- 🛡️ **Safe dependencies** : our own[supply check](https://github.com/honeyglass/actions/tree/main/supply-check) runs first in every CI run. A package comes in only from an allow list, a new version only once\nit is three days old, and no package may run programs while it installs. More in[SECURITY.md](https://github.com/honeyglass/oriko/blob/main/SECURITY.md) .\n\n```\ncurl -fsSL https://raw.githubusercontent.com/honeyglass/oriko/main/install.sh | sh\n```\n\nThe script installs the command `oriko` and then the agent skill, for Claude Code and every other\nagent it finds. For the skill it runs the [skills CLI](https://www.skills.sh/) behind skills.sh.\nRun the line again to update both.\n\n## **With the PDF, without Google Docs**\n\n```\ncurl -fsSL https://raw.githubusercontent.com/honeyglass/oriko/main/install.sh | sh -s -- --pdf\n```\n\noriko always writes the Word file for Google Docs. With [LibreOffice](https://www.libreoffice.org)\nit writes the PDF too, the page Google Docs would make: `oriko build --out cv.pdf`. `--pdf`\ninstalls LibreOffice with brew, apt or dnf; without it, the script names the command to run.\n\n## **Command and skill separately**\n\n```\ncurl -fsSL https://raw.githubusercontent.com/honeyglass/oriko/main/install.sh | sh -s -- --no-skill\nnpx skills add honeyglass/oriko -g -y\n```\n\n## **Manual installation**\n\n```\ngit clone https://github.com/honeyglass/oriko.git\ncd oriko\npnpm install --frozen-lockfile\nnode bin/oriko.ts schema\n```\n\nGive the agent three things at once, then answer its questions:\n\n- **Your old CV** : a PDF, a Word file, or your oriko CV.\n- **Notes in your own words** : what you did, how you work, what the old CV leaves out. Short\nlines are enough, in any language.\n- **The job posting** : a file or a link.\n\n```\nCreate a CV for this job. My CV: ~/cv.pdf. My notes: ~/notes.txt. The posting: ~/job.pdf\n```\n\nThe agent reads all three, asks in short rounds before a fact from your notes goes into your CV, and builds a version for the posting. You read the preview and say what to change in plain words (\"shorter\", \"leave out Figma\", \"Built instead of Delivered\"); the agent changes it and shows the preview again. At the end you get the Word file, or the PDF.\n\nThis works well because each part does one job: your notes bring the facts the old CV misses, the posting says what matters, and oriko checks every step, so nothing is invented.\n\nShorter requests work too:\n\n```\nFit my CV to this job: <paste the job posting>\nCreate a new CV for me. Since 03/2021 I have worked as a data engineer at …\n```\n\n**What the agent does for a job posting:**\n\n- Picks your CV in the language of the posting.\n- Reads the parts of your CV that matter for this job.\n- Writes a version: matching skills first, unrelated old jobs hidden, long lists shortened.\n- Checks that every block fits on the pages, and fixes it if not.\n- Builds the Word file and shows you the preview, every change, and why it made it.\n- Tells you what the posting asks for that your CV does not show yet.\n\nNo CV yet? See [Good to know](https://github.com/honeyglass/oriko/blob/main/docs/good-to-know.md#-no-cv-yet).\n\nAn agent alone can be wrong without noticing, and a tool alone cannot read a job posting. oriko puts the two together: the agent does what needs judgment, and every step it takes runs through a CLI that checks it, refuses what does not fit and never guesses.\n\noriko has two parts. The **CLI** does the work and checks every input. The **skill** in\n[`.claude/skills/oriko/`](https://github.com/honeyglass/oriko/blob/main/.claude/skills/oriko/SKILL.md) is the agent's manual: which command to\nrun when, what it may change, and when it stops and asks you.\n\nThe skill is a fixed list of steps, and for each step the steps that may follow (a state machine).\nIt has two paths. To fit a CV to a posting, the agent reads the posting, inspects\nyour CV, drafts a version, checks it, builds it and reports. To write a CV, it sorts your facts,\nwrites them, checks them and hands over; with no CV at all, it first asks you a few short\nquestions. The agent moves only along the listed steps. When oriko refuses a draft, the agent goes back\none step and fixes it, at most three times; then it stops and asks you. The steps, what each one\ndoes and which may follow it, stand in [the flow of the skill](https://github.com/honeyglass/oriko/blob/main/.claude/skills/oriko/SKILL.md#flow).\n\nDX stands for developer experience: how easy a tool is to use. Agent DX asks the same question for\nan AI agent, which cannot click through a menu or guess what a vague error means. The rules start\nfrom Justin Poehnelt's article\n[Rewrite your CLI for AI agents](https://justin.poehnelt.com/posts/rewrite-your-cli-for-ai-agents/)\n(2026), with the [Google Workspace CLI](https://github.com/googleworkspace/cli) as its reference\nimplementation. [The CLI page](https://github.com/honeyglass/oriko/blob/main/docs/cli.md) lists every rule oriko follows, its commands, and a\nrefusal as the agent reads it.\n\noriko navigates on its own: `oriko` alone shows where to start, every success names the next\ncommands, a refusal names the command that fixes it, and an option without a value lists the\nvalues it accepts. A person needs no manual, and the agent acts on what oriko answers, never on a\nguess.\n\n## **Agent DX rules**\n\nThe rules marked ➕ oriko are new: the author of oriko added them from building tools for agents.\n\n| Rule | What oriko does | Why it helps the agent | Source | \n|---|---|---|---|\n| Raw JSON input | takes its whole input as one JSON object | passes the data as it is, without many flags | article | \n| Schema at runtime | `oriko schema` shows every command and its input | looks the format up in the tool itself | article | \n| JSON when piped | text for people, JSON for programs | each reader gets what it can read | article | \n| Input hardening | the Word file and photos stay inside their folder | a mistake never writes elsewhere | article | \n| Dry runs | `--dry-run` says what would happen | tries a command safely first | article | \n| Agent skill | the agent's manual ships with the code | knows when to stop and ask you | article | \n| Checks in layers | shape, then version, then pages; all errors at once | fixes real errors in one go | ➕ oriko | \n| Errors with a hint | each error says where and what to change | fixes the input on its own | ➕ oriko | \n| All or nothing | a refused command writes nothing | no file is left half changed | ➕ oriko | \n| Exit codes 0, 1, 2 | 0 ok, 1 fix the input, 2 something broke | knows the next step from one number | ➕ oriko | \n| Plan before the file | `plan` shows which block lands on which page | fixes an overflow before building | ➕ oriko | \n| Hints that run | a refusal names the command that lists the fitting values | runs it and picks a real value | ➕ oriko | \n| Options that list | an option without a value lists the values it accepts | finds names and ids in one call | ➕ oriko | \n| Next steps | every success names its next commands and what each still needs | always knows where to go on | ➕ oriko | \n| Nothing passes silently | an unknown command, option or word is refused, a group alone lists its actions | never acts on a typo | ➕ oriko | \n\n**See your CV before the file exists.** `oriko preview` draws every page in the terminal, the left\ncolumn beside the right one, as in the finished document:\n\n## **The same preview as text**\n\n```\n╭─ Page 1 of 3 ────────────────────────────────────────┬───────────────────────────╮\n│                                                      │                           │\n│   ╭───────┐                                     Jane │ CONTACT ───────────────── │\n│   │       └┐                                     Doe │                           │\n│   │ ●   ●  │                 Senior Backend Engineer │ Germany, Berlin           │\n│   │•  ◡   •│                                         │ Example Street 1          │\n│   │ ── ─── │                                         │ 10115 Berlin              │\n│   ╰────────╯                                         │ +49 (0) 30 000 000        │\n│                                                      │ jane.doe@example.com      │\n│                                                      │ Profile »                 │\n│                                                      │                           │\n│ PROFESSIONAL EXPERIENCE ──────────────────────────── │ SKILLS ────────────────── │\n│                                                      │                           │\n│ ● Senior Backend Engineer            03/2021 – today │ Programming Languages     │\n│ │                                                    │   Go                ●●●●● │\n│ │ Northwind Logistics GmbH · Berlin (DE)             │   TypeScript        ●●●●○ │\n│ │ › Rebuilt the shipment tracking service in Go      │   SQL               ●●●●○ │\n│ │   for ten times the load, at 40,000 events per     │   Java              ●●●○○ │\n│ │   second                                           │   Rust              ●●○○○ │\n├──────────────────────────────────────────────────────┴───────────────────────────┤\n│ Left  ■■■■■■■■□□ 84 % full     Right ■■■■■■■■■■ 97 % full                        │\n╰──────────────────────────────────────────────────────────────────────────────────╯\noriko preview --profile go-e-senior-backend   # the version for one job posting\noriko preview --cv jane-doe                   # your CV as it stands\n```\n\n**Send the preview as a CV.** `build --style terminal` writes the sheets as a Word file, one A4\npage each, set in Fira Code so Google Docs keeps every character in its column. Send the classic\nfile to managers and the terminal file to developers:\n\n```\noriko build --profile go-e-senior-backend --style terminal --out go-e-terminal.docx\n```\n\nWhat each mark of the preview means: [the terminal preview page](https://github.com/honeyglass/oriko/blob/main/docs/terminal-preview.md).\n\nYour CVs live outside the repository, in `~/.oriko`; `--home <folder>` points oriko at another one.\n\n```\n~/.oriko/\n  cvs/jane-doe.json           your CV: language, person, contact, pages, blocks\n  cvs/jane-doe.png            its photo\n  profiles/backend-job.json   one version per job posting, naming its CV in \"cv\"\n```\n\n- **Google Docs** : the layout is tuned to how Google Docs sets the file, with Open Sans and\nCalibri. Open the Word file there and save it as PDF.\n- ⚠️ **Word and LibreOffice** set the same file with other line breaks, so a block that fits in\nGoogle Docs may spill over to the next page.\n- **PDF without Google Docs** :`oriko build --out <name>.pdf` writes the PDF through[LibreOffice](https://www.libreoffice.org/download) , which has to be installed: on macOS`brew install --cask libreoffice` , on Debian or Ubuntu`sudo apt install libreoffice` , on\nWindows`winget install TheDocumentFoundation.LibreOffice` . Without it, oriko refuses and names\nthese commands. For the PDF, oriko writes a .docx adjusted to how LibreOffice sets it and hands\nover the font files Google Docs uses ([assets/fonts](https://github.com/honeyglass/oriko/blob/main/assets/fonts/README.md) ), so the PDF shows\nthe page Google Docs shows: the same lines, page breaks and positions, within about 1 pt. Only\nCalibri differs: it is not free, so the name and the headings use a font with its widths and\nits baseline, whose letters look a little different. The terminal style matches exactly. macOS\nand Linux; Windows is not covered yet.\n- **Terminal style** : set in Fira Code, which Google Docs offers, so every character keeps its\ncolumn.\n- **Terminal preview** : every line is 84 characters wide; a narrower terminal breaks the lines.\n- **Node** : 24 or newer, which runs the TypeScript files of oriko as they are.\n- **Install script** : macOS and Linux. Windows is not tested; use the manual installation there.\n- **Agents** : the skill is written and tested for Claude Code. The quickstart adds it to every\nagent the skills CLI finds; any agent that can run a command can use the CLI through`oriko schema` .\n\n- More CV templates\n-  An [ATS check](https://enhancv.com/resources/resume-checker/) of the classic CV after every build\n- The skill for Codex\n- The skill for Gemini CLI\n- A cover letter per job posting, from the same facts as the CV\n- A one-line installer for Windows\n- A new CV from a LinkedIn export or a JSON Resume file\n- The PDF from Google Docs without uploading the file by hand\n-  Publish on npm as `oriko`\n\n```\npnpm test             # api and internals tests, fails below 95 % coverage\npnpm run typecheck\npnpm run format:check\nsh tests/e2e/install.e2e.sh   # the install script in empty home folders\n```\n\nCopyright (C) 2026 Serkan Sipahi. oriko is free software under the\n[GNU Affero General Public License v3.0](https://github.com/honeyglass/oriko/blob/main/LICENSE): you may use, change and share it. Anyone who\nshares a changed version, or offers one as a service over a network, must publish its source\nunder the same license.\n\nThe name oriko and the Oriko character are not covered by this license. That includes the\nfiles in [`brand/`](https://github.com/honeyglass/oriko/blob/main/brand) and the Oriko drawing the preview shows; all rights to them stay\nwith the author. A changed version of oriko needs another name and logo.", "url": "https://wpnews.pro/news/oriko-cli-create-your-cv-in-the-terminal-with-builtin-agent-support", "canonical_source": "https://github.com/honeyglass/oriko/", "published_at": "2026-11-18 07:45:00+00:00", "updated_at": "2026-11-18 08:15:04.834535+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools"], "entities": ["Oriko", "Honeyglass", "Claude Code", "LibreOffice", "Google Docs"], "also_reported_by": [], "takeaway": "Oriko ships as a CLI plus an agent skill that an AI agent drives end to end: it reads the master CV, user notes and job posting, then writes a version that only reorders, hides or shortens existing content, requiring user approval before any new claim is added.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/oriko-cli-create-your-cv-in-the-terminal-with-builtin-agent-support", "markdown": "https://wpnews.pro/news/oriko-cli-create-your-cv-in-the-terminal-with-builtin-agent-support.md", "text": "https://wpnews.pro/news/oriko-cli-create-your-cv-in-the-terminal-with-builtin-agent-support.txt", "jsonld": "https://wpnews.pro/news/oriko-cli-create-your-cv-in-the-terminal-with-builtin-agent-support.jsonld"}}