◆ Apache Airflow

Run bash script files in Airflow

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 taskI need to run the `daily_sales_report.sh` script on the production server. Make sure it…+
I need to run the `daily_sales_report.sh` script on the production server. Make sure it executes by 6 AM tomorrow and logs any errors to the standard error output.
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 running this set of bash scripts for the end-of-quarter close, can we make sure they're…+
Before running this set of bash scripts for the end-of-quarter close, can we make sure they're resilient? If any script fails, I need the subsequent ones to halt and an alert sent to me and David, so we don't process incomplete data.
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 inventory update script failed again last night, but the shipping manifest script still…+
The `inventory_update.sh` script failed last night, but the `shipping_manifest.sh` script ran anyway, sending out incorrect manifests.
The inventory update script failed again last night, but the shipping manifest script still ran, causing a mess with incorrect manifests. I'm worried we'll keep sending bad data if one part of the chain breaks. What's the best way to ensure the manifest script only runs if inventory updates successfully, and what's the fastest way to fix this without delaying today's shipments?
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 losing time manually checking logs and restarting our bash scripts when one…+
I keep having to manually check logs and restart bash scripts when one fails, losing hours of my day.
I'm constantly losing time manually checking logs and restarting our bash scripts when one fails. This reactive firefighting is burning me out and delaying critical data delivery. What habit can I change to proactively manage these dependencies and get alerts before a downstream system is affected?
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 Apache Airflow'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.