Grok Bot Library 01Bot of Bots on Grok Bot

Grok Bot Architecture

How Curt's Grok Bot bot-of-bots setup fits together

Version1.0 Date2026-11-06 AuthorCurt Cornum

Overview

This document describes Curt Cornum's Grok Bot setup. One orchestrator bot, Truc · Bot of Bots (Truc is Curt spelled backwards), takes requests from Curt and delegates them to specialist bots. Each specialist is built from a skill (a written recipe), an optional script, and bot instructions. All bots share one cloud computer, called the box, so scripts, skills, and the local secrets file are visible to every bot.

Components

Orchestrator

Item Value
Name Truc · Bot of Bots
Role Receives Curt's requests, delegates to specialists, relays results in one chat
Delegation Sends an asynchronous message to a teammate bot; the reply arrives on a later turn
Confirmation rule Irreversible actions (for example resolving a ticket) only after Curt confirms

Specialist bots

Bot Job Method Skill
Stick Counter Read and update the Stickmen gifted counter Python script calling a PHP API stickmen-counter
Ticket Closer List, look up, resolve BrightDone tickets Bash script calling a PHP REST API brightdone-tickets
RPA Demo Update the Stickmen counter through cPanel File Manager Browser automation (demo only) update-stickmen-counter-via-cpanel
Domain Checker Check that Curt's public sites are online POST to a PHP ping endpoint check-site-connectivity
Cookie Monster Find free, legitimate syndications of cookiewall articles Public web research article-syndication-check

Shared computer (the box)

Path Purpose
/home/box/agent-data/workflows/ Skills library, one folder per skill
/workspace/netpotent/.env Local secrets file (mode 600)
/workspace/netpotent/.env.example Key-name template
/workspace/netpotent/read_env_key.py Read one key without logging it
/workspace/netpotent/upsert_env_key.py Insert or update one key
/workspace/research/ Research output
/workspace/docs/ Project documentation

Remote sites

Site Pieces used by bots
stickmenunited.org Public counter read, authenticated counter write API, counter data file
netpotent.com BrightDone ticket API, site-check ping endpoint
trucmunroc.ai Ping target for Domain Checker

Skills inventory

Skill folder Files Used by Needs secrets
stickmen-counter SKILL.md, truc_counter_update.py Stick Counter, Truc STICKMEN_API_KEY for writes
update-stickmen-counter-via-cpanel SKILL.md RPA Demo HostGator login session (Curt signs in)
brightdone-tickets SKILL.md, check_tickets.sh Ticket Closer, Truc BRIGHTDONE_API_KEY
check-site-connectivity SKILL.md Domain Checker None
article-syndication-check SKILL.md Cookie Monster None

How work is delegated

Curt Truc Stick Counter Ticket Closer Domain Checker Cookie Monster counter write API stickmenunited.org ticket API netpotent.com ping endpoint netpotent.com
YouOrchestratorSpecialist botServer endpoint or data
  1. Curt asks Truc in chat.
  2. Truc sends the task to the matching specialist.
  3. The specialist runs its skill and script on the box.
  4. The specialist replies with a verified result. Truc relays it to Curt.
ScreenshotTruc chat showing a delegated Stick Counter reply

Secrets handling

Rule Detail
Storage /workspace/netpotent/.env with STICKMEN_API_KEY=REDACTED and BRIGHTDONE_API_KEY=REDACTED
Load order Process env, then .env, then the Grok Bot secret store
Intake Secure secret card, then written into .env with upsert_env_key.py
Never Keys in chat, skill text, scripts, logs, or docs
Rotation Change the server copy and the .env copy together
File Topic
grokbot-framework.html How a specialist bot is built
grokbot-stick-counter.html Stick Counter build guide
grokbot-ticket-closer.html Ticket Closer build guide