One-person desk
A company of one, with a chief of staff who never hits send.
6 bots · 20 min to stand up
Open blueprintWork
Grok Bot is great until your memory only lives inside one vendor.
Khe Hy (@khemaridh) has been heavy on Grok Bot but does not want context trapped there. He keeps durable notes in GitHub: routines and skills convert files to markdown, add metadata, and file them — mostly agents touching the files. For structured work he uses Notion databases (pipelines he will actually edit) and Notion task lists various bots read. Connectors stay on his side so he can plug the same context into different LLMs.
GitHub as markdown memory via routines/skills. Notion as structured DBs + bot task lists. Bots read and write there; you own the store.
Bots
Context Clerk
Convert agreed file drops to markdown, add metadata, file into GitHub folders. Mirror structured tasks into Notion DBs you named. No silent store deletes.
Plugins
Notion
Required
Browser
Optional
Files
A GitHub repo (or folder) for markdown memory + a Notion DB for pipelines/tasks.
Routines
Periodic convert-and-file pass into GitHub. Notion stays the human-edited structure layer.
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
Do not force-push, delete repos, or publish without your yes. Bot writes to your stores stay reviewable.
Steal the two-store split: files in git, structure in Notion.
Khe Hy @khemaridh · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
A company of one, with a chief of staff who never hits send.
6 bots · 20 min to stand up
Open blueprint