The tailoring studio
The studio is where you tailor a resume with Jobably rather than waiting for one to be tailored for you. Open it from Resumes → Tailor for a job in the left navigation, or from Tailor resume on any match or board card. It walks your resume line by line — and, inside your experience section, role by role — and proposes changes with the reason each one serves this posting. Nothing changes until you say so.
Three steps
Section titled “Three steps”1. Review
Section titled “1. Review”Pick the master version to start from. If you have pinned one for the Studio, the studio starts there; otherwise it starts from your latest upload. Then Review my resume.
Jobably reads the posting first — what it repeats, what it requires, the level it is written for, and where it says the same thing as your resume in different words. Then it reviews each section. Sections appear as they finish, so you can start deciding while the rest is still running; leaving the page does not stop it.
On your own connected model (BYOK), the review also brings structure and layout recommendations — which section should lead for this posting, what to tighten, how to re-aim the summary, which of your existing competencies to put first — and a headline aimed at the role. On the included model these are skipped, and the studio says so.
2. Decide
Section titled “2. Decide”Every line of your resume is shown as it stands. Where Jobably has a proposal, it sits beneath the line with the reason and the posting phrases it works in, and you choose:
- Use this — the proposed wording replaces yours in this draft.
- Keep mine — your line stands.
- Edit — write your own version.
Any line, proposed or not, can be edited or left out of this draft. Your master resume is never changed; every decision applies to this posting’s draft only.
Length is decided before the review, and you can overrule it. The same budget a one-shot draft runs under applies when a session opens: up to 12 bullets for your current role, 6 for roles that ended in the last ten years, fewer for older ones, or the limit you set under Settings → Tailoring. Each bullet left out is marked left out for length in its section — put it back if it matters for this posting, and the built document reports what was left out.
A proposal keeps your words. A proposal that swaps in the posting’s word for one your own line never uses (the posting says supplier, your line says vendor), or that appends the posting’s own sentence to one of yours, is held back with the reason — in every section, the summary and your skills sections included. You can still write the word yourself by editing the line — the rule is for the model, not for you.
A proposal keeps your opener. A rewording that softens how a line opens (Drove becoming Contributed to) is held back; the line’s own opener stays.
Competency rows are reordered, never rewritten. A proposal for a row of competencies may only reorder the terms you listed, leading with what the posting asks for. One that adds, renames or drops a term is held back.
A line appears once. A bank entry already in one section of this draft is not proposed for another, and the build refuses a copy that slips through. The summary admits one added paragraph at most — the team-size line when the posting asks for one — and when every paragraph of your summary opens with a label, an addition is asked to open with one too.
What the posting opens with leads your current role. When the posting’s first sentence about the role names a duty and a bullet in your current role answers it, the built document places that bullet in the role’s top three and reports the move.
Team scope, when the posting asks for it. When the posting asks for leading people and your record states your team size, the summary review is asked to state it, with the figures exactly as your record has them, and proposes the line from your bank if it did not.
Additions come from your accomplishment bank: when the posting asks for something this section could evidence, the relevant bank entry is proposed as a new line, quoted beside it, for you to add, skip, or reword.
Two things the studio will not do:
- Apply a proposal you have not decided on. An undecided proposal is not applied; your own words are always the default.
- Show a proposal as if it were safe when it is not. Every proposal is checked against your record before you see it — every figure verbatim, every number on a line unchanged, every date as written, every sentence traceable to your resume or your bank. A proposal that fails is shown as held back, with the reason, and cannot be selected. The same checks run on anything you type: a number your record does not carry is refused where you typed it, with the reason, not at the download.
3. Build
Section titled “3. Build”Build the document composes the draft from your decisions, checks every changed line once more, and renders it into your own Word file — your fonts, margins and bullets — with a matching cover letter if you leave that box ticked. The result appears on the job’s card and under Resumes like any tailored resume, moves the job to Tailored on your board, and downloads through the same read-before-you-send step as every tailored file.
Beside the built document you get what the posting still asks for that your record does not evidence, and the review panel for one more approve-and-decline round on the finished draft. Change any decision and build again for a new version; earlier versions are kept.
From a connected assistant
Section titled “From a connected assistant”The same session is reachable over MCP: open_tailoring_session,
review_tailoring_session, get_tailoring_session (every proposal with its
reason and guard verdict), decide_tailoring, build_tailored_resume, and
discard_tailoring_session. It is one session per job, so you can start in
Claude and finish on the page, or the other way round. tailor_resume still
queues the one-shot background draft.
Starting over
Section titled “Starting over”Start over discards the proposals and decisions in a session and begins from the master again. Documents you already built stay on the job. Switching to a different master version also starts a fresh session, because your decisions were made on the lines of the version you were looking at.
For AI agents: llms.txt · llms-full.txt ·auth guide · tool reference
Built v1.1.0 · cec2567 · 2026-11-03 18:41 UTC

