◆ Google Looker

Check Looker system activity

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 taskI need to check the system activity for the past 24 hours to see if there were any failed…+
I need to check the system activity for the past 24 hours to see if there were any failed scheduled reports, specifically for the 'Daily Revenue Summary' report. Tell me the status and any relevant error messages.
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 report on system health to the leadership team, analyze the system activity over the…+
Before I report on system health to the leadership team, analyze the system activity over the last week. Identify any recurring patterns of failed scheduled reports, long-running queries impacting performance for the finance team, or unusual user login activity, and suggest areas for optimization.
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 'Daily Revenue Summary' report failed to deliver to the CFO this morning, and I can't…+
The 'Daily Revenue Summary' report failed to deliver to the CFO this morning, and I can't immediately see why in the activity logs.
The 'Daily Revenue Summary' report failed to deliver to the CFO this morning, and I can't immediately see why in the activity logs. I'm afraid of missing critical deliveries, especially to the CFO. I don't know if it was a data issue, a system hiccup, or something else entirely. What's the most efficient way to pinpoint the exact cause of this scheduled report failure and ensure it never happens again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe often discover system activity issues like failed scheduled reports or slow queries only…+
We often discover system activity issues like failed scheduled reports or slow queries only after a user complains.
We often discover system activity issues like failed scheduled reports or slow queries only after a user complains, which damages our team's credibility. I'm spending too much time reacting to these problems. What habit should I change to proactively monitor system activity, identifying and addressing potential performance bottlenecks or delivery failures before they impact our critical business users?
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 Google Looker'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.