$ ls -la drwxr-xr-x docs/ $ run script
◆ Bash

Generate reports and perform analysis

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 taskGenerate a report for last month's server uptime for all machines in the 'web_servers' group,…+
Generate a report for last month's server uptime for all machines in the 'web_servers' group, showing average uptime and any instances of downtime longer than 5 minutes. Output it to a CSV file named 'uptime_report_july.csv'.
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 acceptI need to analyze the access logs for the main website from yesterday. Before I present the…+
I need to analyze the access logs for the main website from yesterday. Before I present the traffic patterns to marketing, make it easier to understand. Summarize the top 10 most visited pages and the top 5 unique IP addresses, and flag any requests that resulted in a 4xx or 5xx status code.
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 database team needs a report on user activity from the 'users' table for the last quarter…+
The database team is asking for a usage report, but my usual query is running too slow and might crash the server.
The database team needs a report on user activity from the 'users' table for the last quarter by end of day. My standard SQL query for this is timing out and putting a heavy load on the production database. I'm worried about impacting live user experience if I force it. What's the best way to get this data without bringing down the server, and what alternatives should I consider if the direct query isn't feasible?
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 always scrambling to compare performance metrics—like CPU usage or response times—between…+
I consistently struggle to compare performance metrics across different deployment cycles.
I'm always scrambling to compare performance metrics—like CPU usage or response times—between our current production environment and the previous release. It's hard to tell if a change actually improved things. What habit should I change to make it easier to track and compare these metrics systematically after every deployment?
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 Bash'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.