◆ JavaScript

Generate reports from data

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 taskGet the user activity report for the last quarter from the production database, specifically…+
Get the user activity report for the last quarter from the production database, specifically focusing on login attempts and successful authentications. Format the output as a CSV and save it to the shared drive for Maria by end of day.
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 send this weekly performance report to the executive team, make it easier to digest.…+
Before I send this weekly performance report to the executive team, make it easier to digest. Highlight any significant deviations from the previous week's metrics, summarize key trends at the top, and flag any data points that look anomalous and might need a second look.
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 new analytics dashboard is live, and the numbers for active users are significantly lower…+
The new analytics dashboard is showing wildly different numbers from the old one, and I just showed it to the VP of Product.
The new analytics dashboard is live, and the numbers for active users are significantly lower than what our old system reported. I just presented this to the VP of Product, and she's asking why. I'm worried we have a data pipeline issue, but I can't tell if it's a bug in the new dashboard's calculations or a real drop. What's the most likely cause, and how should I investigate this without causing panic?
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 hours each week pulling ad-hoc metrics from various systems for different…+
I keep spending too much time manually extracting metrics from different systems for ad-hoc requests.
I'm constantly losing hours each week pulling ad-hoc metrics from various systems for different stakeholders. It's usually a one-off request, but the sheer volume adds up. I need a better way to quickly access these common data points without having to write a new script every time. What habit should I change to streamline this process?
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 JavaScript'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.