◆ MATLAB

Analyze historic weather conditions

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun the script 'weather_data_processor.m' on the 'historical_weather_2023.csv' dataset.…+
Run the script 'weather_data_processor.m' on the 'historical_weather_2023.csv' dataset. Generate the daily average temperature and humidity for each month and save the results as '2023_monthly_averages.csv'. Ensure the output includes the date and location columns.
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 present this weather analysis to the climate team, make it easier for them to quickly…+
Before I present this weather analysis to the climate team, make it easier for them to quickly grasp the trends. Highlight the five days with the most extreme temperature swings, and visualize the correlation between wind speed and precipitation in a clear, labeled plot.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy extreme weather prediction model, which performed well on historical data, is producing…+
The model I built for predicting extreme weather events is showing wildly inconsistent results when I feed it new data from last week.
My extreme weather prediction model, which performed well on historical data, is producing erratic outputs with last week's real-time feeds. The team needs these forecasts by tomorrow, but I'm worried about false alarms. I suspect a data format mismatch or a sensor calibration issue, but I can't pinpoint it. What's the most likely cause, and how should I quickly diagnose and address it without breaking the existing pipeline?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly spending too much time manually reformatting and cleaning sensor data from…+
I keep struggling to quickly integrate new, varied sensor data into my existing analysis scripts.
I'm constantly spending too much time manually reformatting and cleaning sensor data from different sources before I can even start my analysis. This delays critical insights for the project lead. What habit should I change to build more robust, adaptable data ingestion routines that can handle unexpected variations without constant manual intervention?
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.