◆ Apache Airflow

Pass XCom variables into Python functions

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 Apache Airflow tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskTake the file path generated by the 'download_raw_data' task and pass it to the…+
Take the file path generated by the 'download_raw_data' task and pass it to the 'process_data_for_reporting' Python function in the daily sales report DAG. Make sure the processing function receives the correct, full path to the downloaded file.
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 the next marketing campaign attribution DAG runs, make sure the XCom variables are…+
Before the next marketing campaign attribution DAG runs, make sure the XCom variables are robust. If the 'extract_campaign_id' task fails or returns an unexpected value, ensure the downstream 'enrich_customer_data' task doesn't just crash. I need to know it can handle missing or malformed IDs gracefully.
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 pass a dynamically generated list of S3 bucket names from the…+
I'm trying to pass a dynamic list of S3 bucket names from one task to another, but the downstream task keeps getting an empty list.
I'm trying to pass a dynamically generated list of S3 bucket names from the 'list_active_buckets' task to the 'process_each_bucket' task in the data ingestion pipeline. The downstream task keeps receiving an empty list, even though the upstream task's logs show it's generating the correct list. I'm afraid I'm misconfiguring the XCom push/pull and missing a critical data source. What's the likely diagnosis for this empty list, and what's the best next move to ensure the list is passed correctly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time debugging downstream task failures because of issues with XCom variable…+
I frequently struggle with XCom variable types and serialization, leading to downstream task failures.
I keep losing time debugging downstream task failures because of issues with XCom variable types and serialization, especially when passing complex data structures. What habit should I change in how I define and manage XComs across tasks to prevent these common type-mismatch and serialization errors, ensuring data flows smoothly without unexpected crashes?
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.