◆ Apache Airflow

Set up automation tasks

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 taskSet up an automation task to archive old log files from the web servers to cold storage every…+
Set up an automation task to archive old log files from the web servers to cold storage every Sunday at 3 AM. The path is '/var/log/nginx' and the target is 's3://archive-logs'.
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 we automate the log archiving, let's make sure we're not inadvertently deleting anything…+
Before we automate the log archiving, let's make sure we're not inadvertently deleting anything critical. Can you add a step to verify the logs have been successfully moved to S3 before deleting them from the web servers, and also notify the operations team if the S3 transfer fails?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to automate the weekly database backup, but the credentials keep failing even though…+
I'm trying to automate the weekly database backup, but the credentials keep failing, and I can't see why.
I'm trying to automate the weekly database backup, but the credentials keep failing even though I've double-checked them against our secrets manager. The backup needs to run every Saturday night, and I'm afraid if it's not automated, someone will forget, and we'll be exposed. Is this a permissions issue on the database user, a network problem, or something with how the secrets are being passed? What's the best way to debug this securely without exposing the credentials in logs?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternSetting up new automation tasks often involves tedious, manual credential management and…+
Setting up new automation tasks often involves tedious, manual credential management and testing.
Setting up new automation tasks often involves tedious, manual credential management and extensive testing, leading to delays and potential security risks. This always slows down our ability to deliver new data pipelines to the product team. What habit can we change to streamline the secure handling of credentials for automation, making it faster and safer to deploy new tasks?
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.