What this adds

AITuber (plugin) — an AI video studio your Grok Bot can drive: script, voice-over, visuals, captions, and publishing to a connected channel.

Checklist

• This PR adds exactly ONE new file under content/ (plus assets for this entry, if any).
• It follows CONTRIBUTING.md — required fields + the golden rules (G1–G8).
• npm run validate passes locally (schema, slug, vocabularies).
• slug is kebab-case and exactly matches the filename.
• I ran / used this myself end to end — it works today.
• Every URL in the frontmatter resolves to real, relevant content.
• The prompt body is the real, complete prompt — not a summary or a teaser.
• The entry body is plain markdown — no raw HTML.
• I did NOT set verified_at or status: live — a maintainer sets those during verification (§10.1).
• This is not an ad.
• If this is someone else's work — n/a, this is my own product.
• If the source is a YouTube video — n/a.
• I license this contribution under CC BY 4.0 (attribution: entry author + grokbot.dev).

Where it came from

I am the founder. AITuber is at https://aituber.app; the hosted MCP server is https://mcp.aituber.app, documented at https://aituber.app/mcp and https://aituber.app/api.

The prompt is written against those docs and tested against the live server, not from memory. It names only capabilities the server really exposes, and it makes the bot read the docs itself before wiring anything up. Because generating spends credits and publishing is public, the prompt gates both: the bot quotes the cost from the real credit balance before it starts, and holds every export and post until the user approves it.

Notes for the reviewer:

• x_handle is omitted on purpose. AITuber has no product X account, and I would rather leave the field empty than point it at something that is not the product. founder is set.
• works_with: ["X"] because publishing to X is a real, shipped destination alongside YouTube, TikTok and Instagram. The other three are not in the controlled vocabulary, so they are described in the body instead.
• npm run build also passes locally, including check-links and audit-scripts.