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

Perform daily administrative tasks

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 taskList all active processes for the 'web_server' user and show their CPU and memory…+
List all active processes for the 'web_server' user and show their CPU and memory usage.
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 restart the 'database_service', show me its current status, active connections, and…+
Before I restart the 'database_service', show me its current status, active connections, and open files so I can confirm it's safe to proceed and understand the impact.
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 'backup_database.sh' script failed last night with a 'permission denied' error, but it ran…+
The nightly backup script failed, and I'm getting calls from management about data integrity.
The 'backup_database.sh' script failed last night with a 'permission denied' error, but it ran fine for weeks. John, the new intern, was working on some file permissions yesterday. I'm afraid I'll have to restore from an older backup if I can't fix this quickly, which means losing a day's data. What's the most efficient way to diagnose the permission issue and get the backup running before the end of the day?
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 interrupted by system alerts about disk space, high CPU, or service failures,…+
I'm always reacting to system alerts instead of proactively managing them.
I'm constantly interrupted by system alerts about disk space, high CPU, or service failures, which makes it hard to focus on development tasks. I feel like I'm always putting out fires instead of preventing them. What habit can I change to move from reactive firefighting to proactive system management and anticipate these issues?
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.