◆ Elasticsearch

List all Elasticsearch indexes

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 taskShow me all the current indexes. I need to quickly see what's running on the cluster right…+
Show me all the current indexes. I need to quickly see what's running on the cluster right now.
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 present to the security team, list all the indexes, but highlight any that aren't…+
Before I present to the security team, list all the indexes, but highlight any that aren't following our 'app-name-YYYY.MM.DD' naming convention. They're looking for compliance gaps.
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 client is asking why their dashboard isn't showing today's data, and I can't find an index…+
The client is asking why they can't see recent data in their dashboard, but I can't find an index that matches the expected pattern for today's date.
The client is asking why their dashboard isn't showing today's data, and I can't find an index that matches our usual 'client-YYYY.MM.DD' pattern for the current day. I'm afraid data isn't flowing. What's the most common reason a new daily index wouldn't appear, and what's the first thing I should check to diagnose if data ingestion has stopped?
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 wasting time manually verifying that new application deployments have created…+
I spend too much time manually checking for new indexes or missing ones after deployments.
I'm constantly wasting time manually verifying that new application deployments have created their expected indexes, or hunting for missing ones. This often delays testing. What habit should I adopt to automatically confirm index creation and health after a deployment, without having to manually inspect every time?
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 Elasticsearch'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.