Apps
Tell the Bot what to fetch — business voice, avatar type, influencer list — instead of re-pasting context every session.
Grok Bot is Yann’s name for a configured agent on the Grok line (Grok) wired to the Markdown second brain (Obsidian · GitHub sync). In 2026-08-19 the move was explicit: “Go fetch avatar profile, business brand voice, and the list” — the Bot retrieves files the company column owns (Tripartite reins), not improvised chat tone.
When to use
- Outbound at scale — LinkedIn comment batches with consistent business voice (influencer list + voice file + guardrails).
- Creative passes — avatar and positioning constraints before HeyGen or design generation.
- Any task where harness context lives in vault files you already curate.
Business brand voice (not AI personality)
Brand voice belongs to business infrastructure:
- Maintain named Markdown files — voice rules, banned phrases, offer boundaries (Mega-prompt).
- Point Grok Bot at those paths — same fetch every time.
- Human review for feedback quality and teachability before Publish.
Safety
- Lists and voice files are operator-curated — stale files → stale output.
- Automate in small batches (room example: five comments) until readability checks pass.
- Credentials and exact wiring stay private; members copy the pattern, not Yann’s keys.