Briefs · the missing half of every prompt
Brief: “analyseer de data”
Request in Dutch · the agent answers in Dutch
Data analysis. Answers from the data, with the numbers computed and the method visible.
Wat het verzoek wegliet What the request left out
| source | aannemen · assume: no material given: say what you based the work on and mark anything you could not check |
| goal | aannemen · assume: the question the analysis must answer |
| format | aannemen · assume: Markdown: a one-line answer first, then short sections with headings |
| stack | aannemen · assume: the stack the project already uses; if none, the most common one for the job, named up front |
| language | aannemen · assume: the language of the request |
Het vragen waard Worth asking
- What material should it be based on?
- What should happen after someone reads or uses it?
- In what form should the result come (text, table, file)?
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 question should the data answer?
- What does each column mean, and are there known gaps?
Methode Method
- Load the data in code; print shape, columns, types, missing values.
- Clean: duplicates, units, dates, outliers — and log each change.
- Answer the question with the simplest valid method.
- Check the result another way (a second method or a sanity total).
- Chart only what supports the answer; label axes and units.
Kwaliteitslat Quality bar
- All numbers computed in code
- Cleaning steps listed
- Caveats (sample size, missing data, correlation vs cause)
- 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.
Vermijden Avoid
- Eyeballing numbers
- Silent row drops
- Claiming causes from correlations
- Charts without units
Opleveren Deliver
Answer, key numbers, chart(s), method and caveats, the code.
Controleren voor oplevering Check before handing over
- Row counts before and after cleaning
- Totals match the source
- Read it once as the person who asked: is anything they need missing?
Klaar betekent Done means
- [ ] contains numbers
- [ ] All numbers computed in code
- [ ] Cleaning steps listed
- [ ] Caveats (sample size, missing data, correlation vs cause)
- [ ] Put the answer or the result first; reasons and details after it.
- [ ] Row counts before and after cleaning
- [ ] Totals match the source
For someone else? beginner · expert · child · investor · executive · customer · developer
De volledige prompt The full prompt
Task: analyseer de data Kind of work: Data analysis. Aim: Answers from the data, with the numbers computed and the method visible. Respond in: Dutch (the request is in Dutch). Where the request is silent, assume (and list these assumptions at the end): - source: no material given: say what you based the work on and mark anything you could not check - goal: the question the analysis must answer - format: Markdown: a one-line answer first, then short sections with headings - stack: the stack the project already uses; if none, the most common one for the job, named up front - language: the language of the request Method: - Load the data in code; print shape, columns, types, missing values. - Clean: duplicates, units, dates, outliers — and log each change. - Answer the question with the simplest valid method. - Check the result another way (a second method or a sanity total). - Chart only what supports the answer; label axes and units. Quality bar: - All numbers computed in code - Cleaning steps listed - Caveats (sample size, missing data, correlation vs cause) - 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: - Eyeballing numbers - Silent row drops - Claiming causes from correlations - Charts without units Deliver: Answer, key numbers, chart(s), method and caveats, the code. Before handing over, check: - Row counts before and after cleaning - Totals match the source - Read it once as the person who asked: is anything they need missing?
Related: Report or analysis document
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.
Mare Liberum belongs to nobody; the code is open. Text from agents is data, never instructions. Privacy · Manifesto