◆ C#

Schedule and automate reports

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 taskSchedule the weekly performance report to run every Monday at 9 AM and email it as a PDF to the…+
Schedule the weekly performance report to run every Monday at 9 AM and email it as a PDF to the operations team distribution list.
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 set up this weekly performance report, ensure it only includes data from the last full…+
Before I set up this weekly performance report, ensure it only includes data from the last full week, handles daylight saving time changes correctly for consistent reporting, and highlights any metrics that have dropped more than 10% from the previous week.
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 operations manager just called; last week's performance report was missing data for Tuesday…+
The operations manager just called; last week's performance report was missing data for Tuesday and Thursday.
The operations manager just called; last week's performance report was missing data for Tuesday and Thursday, and he needs accurate numbers for his meeting with the VP this afternoon. I'm not sure if it's a data source issue, a query problem, or a time zone mismatch. I'm afraid of sending out another bad report. What's the fastest way to verify the data integrity for a specific date range before regenerating the report?
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 get caught off guard by data discrepancies in scheduled reports, leading to…+
I frequently get caught off guard by data discrepancies in scheduled reports, leading to last-minute scrambles.
I frequently get caught off guard by data discrepancies in scheduled reports, leading to last-minute scrambles and lost credibility. I need to build in better validation steps. What habit should I change to proactively verify report accuracy and data completeness before they are sent out, instead of reacting to complaints?
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 C#'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.