Notes

How operators share souls, rules, and desks. Example posts stay labeled.

• Sell a job description, not a clever prompt

  Eleven orchestration tips from @kloss_xyz, mapped into a Prompt Place listing: scope, accounts, hours, handoffs, forbidden zones, silence, and permanent corrections.

  Grok Bot guide · Orchestration · Bot setup · Chief of staff

• Give each bot one job

  The giant AI computers are still being built. Until they are ready, give each bot one subject — like a teacher, not a whole school.

  Grok Bot guide · Guardrails · Bot setup · Chief of staff

• The manager bot only points

  One chat that does everything is a clerk. A real setup is a manager, a few leads, and workers with one job. You still say yes.

  Grok Bot guide · Orchestration · Chief of staff · Bot setup

• You are not out of AI. The backpack is too full.

  The weekly limit usually dies on leftover notes, not on a weak model. Split the jobs. Write each job down. Keep automatic checks quiet.

  Grok Bot guide · Guardrails · Bot setup · Chief of staff

• Give the bot a passport, not your login

  A name, its own inbox, a tiny spend limit, and a kill switch beat “just log in as me.”

  Grok Bot guide · Guardrails · Bot setup · Chief of staff

• Share the setup page, not a genius prompt

  The live page is the setup: who the bot is, what it may do, when it must stop. Send the URL. You approve the next step.

  Grok Bot guide · Orchestration · Bot setup · Chief of staff

• What a manager-bot setup actually is

  A job for the bot that runs your other bots: who it is, the rules, and a stop. Not a clever paragraph.

  Grok Bot guide · Orchestration · Chief of staff · Bot setup

• You will be measured by your ideas, not your typing

  Drafts got cheap. Judgment did not. The scoreboard moves to what you chose and what you refused.

  Grok Bot guide · Orchestration · Chief of staff · Bot setup

• A clip swarm reads a transcript. It does not rip the file.

  Scout marks in/out. Editor sequences. Caption drafts. You export. Rights stay on SOURCE.md.

  Package / team · Grok Bot setup · Video team

• One project, one channel

  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

• A desk map is a protocol. A dollar ticker is a clip.

  Visualization belongs on the shop. Invented daily income does not.

  Grok Bot guide · Orchestration · Bot setup · Chief of staff

• The SKU is a zero-ambiguity charter

  Role, allowed sources, never, stop for APPROVE, file you write.

  Grok Bot guide · Guardrails · Chief of staff · Teammate pack

• Head of desk never places the trade

  The coordinator brings APPROVE. Specialists draft. You stamp. That is the product.

  Grok Bot setup · Orchestration · Chief of staff · Bot setup

• A physical bot is a paste, not a robot login

  The hosted brain drafts the move. The body waits for a human yes.

  Grok Bot setup · Floor robot

• A physical Grok Bot needs a deadman, not a longer prompt

  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

• Send the setup page. Do not write a genius prompt.

  Copy the listing URL. Paste it into Grok Bot. That is the product.

  Grok Bot setup · Grok Bot guide · Chief of staff · Bot setup

• A desk CFO reads a paste, not a bank login

  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)

• Art packs need segments, not vibes

  An art orchestrator that only says pretty will drift. Lock hex, segment order, and one crop.

  Creative direction · Package / team · Art / design

• Stand up an orchestration agent with soul files

  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

• Selling defensive security prompts

  Appsec review, hardening, and triage are fair listings. Exploit recipes are not.

  Evaluation / rubric · Guardrails · Application security

• Turn a listing into a working agent

  Paste the system prompt, attach the tools, test the refusals.

  Tool-use · Orchestration

• Listing a prompt without pretending it is a paycheck

  How to list a prompt or setup on a marketplace like this. Quality and reviews. Not a get-rich plan.

  Writing

• Why pay for a curated prompt

  A good setup is tested limits and fewer silent failures, plus reviews.

  Guardrails · Evaluation / rubric

• Why AI agents matter without the hype

  They matter when the job is repetitive, tool-shaped, and a human still owns the call.

  Planning

• How to actually use an AI agent

  Pick a job, name the tools, write the guardrails, keep a human check.

  Workflow / SOP · Guardrails

• What an AI agent is (and what it is not)

  A chatbot answers. An agent is given a job, tools, and a loop. Memory and limits matter more than the label.

  Tool-use · Orchestration

• Writing an analysis prompt for stocks

  How to keep a screening prompt honest — sources, scoring, and what the agent must refuse.

  Analysis / screening · Stocks