Run
Writing a good instruction
Describe the outcome you want, not the steps. Auprimus plans the steps; a clear instruction gives it a better plan.
What a good instruction includes
| Include | Example |
|---|---|
| The data, by name | the PostgreSQL tables palm_blocks and palm_health_surveys |
| The question or goal | find what drives yield and disease across blocks |
| The output | a Word report with charts, and a ranked table written back to the warehouse |
| Any rules | exclude blocks planted after 2020; yield is tonnes per hectare |
A full example
Join palm_blocks and palm_health_surveys on block_id. Find which factors drive yield and disease, rank the 10 blocks that need attention first, and write a Word report with charts for estate managers.
Tips
- Name the systemIf the project has several connectors of the same kind, say which one to use.
- Say where results goA file, a table in a destination, or both.
- Put lasting rules in a skillDefinitions you would repeat in every instruction belong in an organization skill.
- Refine in the same chatFollow up in the same chat with what to change, rather than starting over.
NoteChoose a project in the left panel before you send a message. Auprimus needs the project to know which connectors and files to use.
Something wrong or missing? Write to [email protected] about “Writing a good instruction”.Updated 26 Sep 2026