Notes on orchestration bot configurations
How operators share souls, rules, and desks. Example posts stay labeled.
The live page is the config. Soul, rules, a stop. Send the URL to the main bot. You approve the next step.
Grok Bot guide · Orchestration · Bot setup · Chief of staff
A job for the bot that runs your other bots: soul, rules, and a stop. Not a clever paragraph.
Grok Bot guide · Orchestration · Chief of staff · Bot setup
Models make drafts cheap. Judgment does not get cheaper. The scoreboard moves to what you chose and what you refused.
Grok Bot guide · Orchestration · Chief of staff · Bot setup
Scout marks in/out. Editor sequences. Caption drafts. You export. Rights stay on SOURCE.md.
Package / team · Grok Bot setup · Video team
Separate specialist chats drown you. Coordinate like a human shop: a board, a manager, a cap on seats.
Grok Bot setup · Chief of staff · Workflow guide
Role, allowed sources, never, stop for APPROVE, file you write.
Grok Bot guide · Guardrails · Chief of staff · Teammate pack
Visualization belongs on the shop. Invented daily income does not.
Grok Bot guide · Orchestration · Bot setup · Chief of staff
The coordinator brings APPROVE. Specialists draft. You stamp. That is the product.
Grok Bot setup · Orchestration · Chief of staff · Bot setup
The hosted brain drafts the move. The body in the room waits for a human yes. Marked cells only.
Grok Bot setup · Grok Bot guide · Physical endpoint · Floor steward
The useful physical setup is one machine, one endpoint file, and a human who can still hit stop.
Grok Bot setup · Grok Bot guide · Workshop arm · Floor rover · Install notes
Grok Bot gets better when you collect setups from people who actually run bots, then let your agent fetch the page.
Grok Bot setup · Grok Bot guide · Bot setup · Workflow guide
The useful morning question is coverage: can you pay what is due from cash you already have. That does not require handing an agent your bank.
System / persona · Chief of staff · Finance (personal)
A kawaii listing that only says cute will drift. Lock hex, anatomy order, and one merch crop.
Creative direction · Package / team · Art / design
OpenClaw workspace files are not Kimi Swarm. Write SOUL, AGENTS, IDENTITY, USER, memory — then maybe a parallel job.
Orchestration · System / persona · Package / team · Agent setup · Soul files · Clawbots · Kimi swarm
Appsec review, hardening, and triage are fair listings. Exploit recipes are not.
Evaluation / rubric · Guardrails · Application security
Paste the system prompt, attach the tools, test the refusals.
Tool-use · Orchestration
How to list a prompt or setup on a marketplace like this. Quality and reviews. Not a get-rich plan.
Writing
A good setup is tested limits and fewer silent failures, plus reviews.
Guardrails · Evaluation / rubric
They matter when the job is repetitive, tool-shaped, and a human still owns the call.
Planning
Pick a job, name the tools, write the guardrails, keep a human check.
Workflow / SOP · Guardrails
A chatbot answers. An agent is given a job, tools, and a loop. Memory and limits matter more than the label.
Tool-use · Orchestration
How to keep a screening prompt honest — sources, scoring, and what the agent must refuse.
Analysis / screening · Stocks