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

Manage and maintain Linux systems

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 taskInstall the 'nginx' web server and 'php-fpm' on the 'webserver03' machine. Ensure they start…+
Install the 'nginx' web server and 'php-fpm' on the 'webserver03' machine. Ensure they start automatically on boot and configure 'nginx' to serve content from '/var/www/html' with PHP processing enabled. Restart both services once configured.
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 ensure our 'database_server_01' machine is robust and secure. Before I hand it off to…+
I need to ensure our 'database_server_01' machine is robust and secure. Before I hand it off to the data team, audit its current configuration for common vulnerabilities, suggest hardening measures for SSH and file permissions, and verify that critical services are running with the least privilege.
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 main 'prod_app_server' is reporting a load average of 15, but 'top' shows no single process…+
The 'prod_app_server' is showing high load average but no obvious process consuming CPU.
The main 'prod_app_server' is reporting a load average of 15, but 'top' shows no single process hogging CPU. Users are complaining about slow responses. I'm worried about an outage during peak hours. I can't just restart it without understanding why. What's the most likely underlying issue, and what's the safest first step to pinpoint the problem without disrupting service?
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 losing hours every week manually logging into individual Linux servers to apply security…+
I spend too much time manually updating packages and patching servers.
I'm losing hours every week manually logging into individual Linux servers to apply security patches and update packages. It's tedious, error-prone, and I'm afraid I'll miss a critical update. What habit should I change in my system maintenance workflow to automate these routine tasks more effectively across the server fleet?
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.