Grok Prompts

Make a 2min music video: violen, piano, chelo trance with lots of dynamic, pauses and a couple epic beat buildups and drops. Lyrics are people's reaction to the Tesla Roadster on X; vocalist is similar to portishead/the oprah artist in the fifth element. The video... futuristic flying cars, cyberpunk city, rain scene zooming into a water drop turned to matrix code, morphed into zoom out of a computer screen to the Universe.

A cozy wooden cabin glows warmly at the edge of a snowy pine forest at night, soft snowflakes falling slowly, smoke curling from the chimney, a starry sky above. Very slow push-in toward the lit window. Warm orange window light against cool blue moonlit snow. Peaceful, cinematic, 35mm, film grain.

Install Grok Bot from the .deb in this directory onto this Linux system. This host is not Debian/Ubuntu, so do not use apt or dpkg to install it.

Detect the OS. If it is immutable (Bazzite, Silverblue, Kinoite, rpm-ostree) or we do not have sudo, do a user-local install:

1. Extract the .deb with ar + tar (data.tar.xz / data.tar.zst).
2. Copy the Electron app to ~/.local/opt/grok-bot. Use that path with no spaces — Chromium’s sandbox breaks if the install path contains a space (the .deb uses /opt/Grok Bot).
3. chmod 0755 on grok-bot and chrome-sandbox if user namespaces work (`unshare --user true`). Do not require SUID chrome-sandbox.
4. Symlink ~/.local/bin/grok-bot → the extracted binary. ~/.local/bin is usually already on PATH.
5. Install a desktop file to ~/.local/share/applications/grok-bot.desktop with Exec pointing at the user-local binary, Icon=grok-bot, and the original MimeTypes/StartupWMClass.
6. Copy hicolor icons to ~/.local/share/icons/hicolor.
7. Refresh desktop/icon caches (update-desktop-database, gtk-update-icon-cache, kbuildsycoca6 if present).

If this is a normal writable distro with sudo, installing under /opt/grok-bot (still no spaces) plus a /usr/local/bin or ~/.local/bin symlink is fine. Do not convert with alien unless there is no better option. Do not rpm-ostree layer anything unless I ask.

Verify shared libraries with ldd, confirm `grok-bot` is on PATH, and smoke-test that the binary actually launches. Then tell me how to open it from the app menu and the terminal.

Based only on this photo, put me on the tv show I look like I belong on and generate an image. (Create the image as if it is a promo for the show. Also choose a real television show based only on my appearance.)

You have access to all of the tools I use for work like Gmail, Notion, Slack, etc. Tell me two things you can help me take off my plate!

A lone hiker in a red jacket stands on a rocky mountain ridge at sunrise, seen from behind, a sea of clouds filling the valley below. Slow smooth drone orbit around the hiker. Low golden sun rim-lighting the figure, cool blue shadows in the clouds. Epic but calm, cinematic, 35mm anamorphic, film grain.

Remake Rodents Revenge make no mistakes

4 versions of my X character, in a 4-panel image, based on my X account: who I think I am, who strangers think I am, how the people closest to me probably see me and the real me that no one knows about.

Audit every permission you currently believe you have. For each one, tell me:

1 - What action you believe you can take

2 - Whether you can do it without asking me

3 - Where that permission came from

4 - Whether the permission may now be stale

5 - What could go wrong if you used it incorrectly

6 - Whether I should keep it, require approval, reconfirm it or remove it

Pull only from saved memory and routines; don’t invent permissions.

slow cinematic build, strings + soft piano, 80 BPM, no vocals, swell at the end

Build a mobile-first habit tracker web app.

- I can add up to 10 habits, each with a name and an emoji.
- Today's screen shows each habit as a big tap target. Tapping marks it done for today; tapping again undoes it.
- Show a current streak and a best streak for each habit.
- A simple 4-week grid per habit, filled squares for done days.
- Save everything in the browser (localStorage) so it works without an account.
- Clean, calm design, large text, dark mode that follows my phone setting.
- No sign-up, no ads, no external tracking.

When it works, walk me through anything I should test, then publish it so I can open it on my phone.

Show me my report card based on my X account

I want to progressively eliminate the need for me to operate business software.

Your objective is to become the operating layer between me and every software application my business uses.

Audit my current setup:

1 - Identify the business applications you can access through existing connectors, APIs or browser access. Ask me about any applications you cannot identify.

2 - Determine the recurring work I perform inside each application. Separate work that requires my judgement from work you could handle independently.

3 - Identify which applications you could operate on my behalf today, which need additional connections and which are beyond your current capabilities.

4 - Find opportunities where your agents could coordinate work across multiple applications without me switching between them.

5 - Identify missing permissions, reliability risks, information gaps and actions that should require my approval.

6 - Rank the opportunities by time saved, ease of implementation and how much direct software interaction they could eliminate.

7 - Create a phased implementation plan, starting with the applications I could realistically stop opening first.

Be realistic about your capabilities. Do not assume you have access you haven't verified.

Do not make changes or activate automations yet. Present your findings and recommendations for my approval.

Close-up product still of a vintage mechanical typewriter on a polished oak desk, soft directional morning light from the left, detailed metal keys and black ink ribbon, shallow depth of field, studio photography.

Build a one-page website for my business.

Business: [name], a [type of business] in [city].
Who it's for: [ideal customer in one sentence].
What I want visitors to do: [call / book / visit / order].

Sections, in this order:
1. Hero with a one-line promise and one button for the main action.
2. Three reasons to choose us, written plainly, no buzzwords.
3. Services or menu with prices: [list them].
4. Opening hours and address with a map link.
5. Three short customer quotes (leave clear placeholders, do not invent reviews).
6. Footer with phone, email and social links.

Make it fast, mobile-first and readable. Use [two brand colours]. Then publish it and give me the link.

run a sentiment analysis on this post.

TOOL RESPONSE RELIABILITY AUDIT

Review the agents and workflows you can inspect that use external tools, APIs, connected apps or browser data.

1 - Identify which workflows make important decisions using returned information.

2 - Find where a successful tool response is treated as proof the information is correct.

3 - Check whether critical prices, quantities, dates and other values are independently verified.

4 - Identify actions that could cause damage if the returned information were wrong.

5 - Recommend verification rules and stop conditions for the highest-risk workflows.

For each finding, show the agent, tool, potential failure, existing safeguard and recommended fix.

Separate verified findings from risks you couldn't inspect.

Rank the five most important fixes.

Don't change any workflows without my approval.

A massive ultra high-tech alien UFO hovering menacingly above a sprawling neon megacity at dusk, its dark obsidian saucer hull bristling with glowing weapon arrays and angular thrusters, ominous red scanning beams slicing downward while pulsating energy rings ripple from its core. 3D futuristic CGI render, electric cyan and magenta palette with deep void blacks and glowing white accents, volumetric God rays piercing toxic fog, intricate layered depth with reflective metallic surfaces and energy crackling. Cinematic low-angle dolly shot rising dramatically to emphasize colossal scale, slow smooth orbiting camera motion with subtle lens flare.

Before changing anything, get to know this repository.

1. Read the README, the package or build files and the folder structure.
2. Tell me in under 15 lines: what this project does, how to run it, how to run the tests, and the 3 files that matter most for [the feature or bug].
3. Propose a step-by-step plan for [the change I want], including which files you'll edit and how you'll test it.

Stop after the plan and wait for my OK. Don't edit files or install anything yet.

Search X for posts from the last 48 hours about [topic or product].

Give me:
1. The 3 main opinions people are expressing, with 2 example posts for each (links).
2. Any real problems or complaints that come up more than once.
3. What seems to be driving the conversation today (news, a launch, a viral post).

Leave out memes, bots and obvious promotion. If there isn't much real discussion, tell me that instead of stretching it.