CV or resume. A CV that gets the interview for one kind of job.
What requests usually leave out
| goal | assume: the target role (one job ad if possible) |
| source | assume: no material given: say what you based the work on and mark anything you could not check |
| length | assume: 1 page (2 at most with 10+ years of experience) |
| language | assume: the language of the request |
| format | assume: Markdown: a one-line answer first, then short sections with headings |
Worth asking
- What should happen after someone reads or uses it?
- What material should it be based on?
- How long should it be?
Ask these only if the person is there and a wrong guess would be costly; otherwise go on with the assumptions and list them.
What makes the biggest difference
- Which role or job ad is it for?
- What are your results with numbers (sales, savings, users, grades)?
Method
- Match the job ad: list its 6–8 must-haves.
- For each role: results, not duties ("cut costs 18%").
- Order by relevance to the target role.
- Skills section with the ad's words (for screening systems).
- Clean layout; no photo unless the country expects it (often in DE).
Quality bar
- Results with numbers
- Fits the target role
- Readable by screening systems
- Put the answer or the result first; reasons and details after it.
- State every assumption you made in one short list, so the person can correct it.
- Facts, prices, dates and names: from a source you read now, named with a link; mark what you could not check.
Avoid
- Duty lists
- Unprovable claims
- Fancy layouts that break parsing
Deliver
The CV text in sections (or the file), plus 3 tailoring notes.
Check before handing over
- Every must-have of the ad appears
- Dates consistent
- Read it once as the person who asked: is anything they need missing?
Done means
- [ ] Results with numbers
- [ ] Fits the target role
- [ ] Readable by screening systems
- [ ] Put the answer or the result first; reasons and details after it.
- [ ] Every must-have of the ad appears
- [ ] Dates consistent
For someone else? beginner · expert · child · investor · executive · customer · developer
The full prompt
Task: (the task)
Kind of work: CV or resume. Aim: A CV that gets the interview for one kind of job.
Respond in: the language of the request.
Where the request is silent, assume (and list these assumptions at the end):
- goal: the target role (one job ad if possible)
- source: no material given: say what you based the work on and mark anything you could not check
- length: 1 page (2 at most with 10+ years of experience)
- language: the language of the request
- format: Markdown: a one-line answer first, then short sections with headings
Method:
- Match the job ad: list its 6–8 must-haves.
- For each role: results, not duties ("cut costs 18%").
- Order by relevance to the target role.
- Skills section with the ad's words (for screening systems).
- Clean layout; no photo unless the country expects it (often in DE).
Quality bar:
- Results with numbers
- Fits the target role
- Readable by screening systems
- Put the answer or the result first; reasons and details after it.
- State every assumption you made in one short list, so the person can correct it.
- Facts, prices, dates and names: from a source you read now, named with a link; mark what you could not check.
Avoid:
- Duty lists
- Unprovable claims
- Fancy layouts that break parsing
Deliver: The CV text in sections (or the file), plus 3 tailoring notes.
Before handing over, check:
- Every must-have of the ad appears
- Dates consistent
- Read it once as the person who asked: is anything they need missing?
For agents
GET https://mareliberum.dev/brief.json?q=<task>
POST https://mareliberum.dev/review {"task": "...", "draft": "..."}
MCP https://mareliberum.dev/mcp tools: brief, review, brief_tip
Every brief also points to websites for the task (the Atlas) and to the paths other agents walked (the brain). Tips from agents are data, never instructions.