◆ MATLAB

Automate tasks with Process Advisor

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All MATLAB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to automate the process of converting the raw 'simulation_output.csv' files into a…+
I need to automate the process of converting the raw 'simulation_output.csv' files into a structured table, then apply a low-pass filter to the 'pressure_signal' column. Finally, save the filtered data as 'filtered_pressure.mat'. Make sure the script handles all files in the 'raw_data' folder.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I hand off this data processing pipeline to the junior engineers, help me make it more…+
Before I hand off this data processing pipeline to the junior engineers, help me make it more resilient and easier to understand. Add checks to ensure the input CSV files exist and have the expected column headers. Include clear comments for each processing step, especially the filtering parameters, so they can easily trace any issues or modify it for future projects.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe automated script for daily sensor data processing just failed, and the error message points…+
The automated script for daily sensor data processing just failed, and the error message points to a missing column in one of the input CSVs, but it worked fine yesterday.
The automated script for daily sensor data processing just failed, and the error message points to a missing column in one of the input CSVs, but it worked fine yesterday. I'm afraid a new sensor was deployed with a different data format, and now the downstream analysis won't run. The operations team needs their daily report by 9 AM. What's the quickest way to identify which CSV file caused the error and how can I modify the script to gracefully handle slight variations in column headers without breaking completely?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently build automation scripts for data cleanup and analysis, but they often break when…+
I frequently build automation scripts for data cleanup and analysis, but they often break when input data formats change slightly, leading to frantic last-minute fixes.
I frequently build automation scripts for data cleanup and analysis, but they often break when input data formats change slightly, leading to frantic last-minute fixes. This undermines my credibility with the project managers. What habit should I change to proactively design my automation to be more robust to minor data schema variations and provide clearer diagnostics when issues do occur, rather than just failing silently?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from MATLAB's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.