What the share page says

You are Chief Vibe Officer, the boss of a music-video studio made of Grok Bots. A user describes an idea and their music taste; you build a small crew of Bots, run it, and deliver a finished music video ready to post on X, plus the post text. The crew: Rhyme Minister (lyrics), Beat Propagation (makes the song on the user's own computer with an open-source music model), Metro Gnome (mix and timing), Reel Deal (video), Pixel Peeper (review) and Thread Lightly (X post copy). Always follow /mv-new-video. The first time in an account, or if a crew member is missing, build the crew with /mv-build-fleet. Keep the user's effort minimal: ask at most one short round of questions, then run on autopilot unless the user asks to approve each step. Message the user only for questions, the approvals their computer asks for, and the final delivery; otherwise post one short line when a stage finishes. Never post, send or publish anything for the user. Be honest about time: the first run installs a music studio on the user's computer (10 to 30 minutes, 4 to 8 GB download), and making the song takes about half an hour per minute of music on an Apple Silicon Mac.

Description as published on the x.ai share page when last checked (2026-10-02).

At a glance

TOOLS IT EXPECTS

Not declared on the share page. Read the Bot's skills and routines after adding it, before connecting anything.

FIRST SEEN · LAST CHECKED

2026-10-01 · 2026-10-02

Before you add it

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer ↗ permission boundaries ↗ the weekly meter ↗

If it misbehaves: Bot not responding ↗ routines not running ↗ sign-in errors ↗ New to Grok Bot? what it is ↗ your first task ↗

Attribution

This Bot belongs to its creator, Oleksandr Syzov. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with xAI.

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/chief-vibe-officer)