Generate tension
The provocateur tries to escape the obvious answer while the skeptic attacks whatever sounds clever but fragile.
Moltron Roundtable spawns a temporary provocateur, operator, skeptic, and customer voice. They challenge one proposal, then your coordinator turns the disagreement into a decision memo.
Free email delivery. No checkout. This is the original OpenClaw-era package; current Hermes compatibility is not verified.
Why four seats
The roundtable forces the proposal through four different jobs: originality, execution, risk, and buyer relevance.
The provocateur tries to escape the obvious answer while the skeptic attacks whatever sounds clever but fragile.
The operator asks what ships first, which dependency blocks it, and where the hidden complexity lives.
The customer seat judges the idea from the outside, where novelty matters less than relevance and trust.
The four seats
The value is not four agents repeating the same answer. Each seat receives a distinct lens and the coordinator must reconcile the conflict.
Pushes beyond the safe answer and proposes the move the rest of the room may reject too quickly.
Turns the proposal into concrete first steps, dependencies, owners, and constraints.
Finds weak assumptions, trust gaps, operational debt, and the easiest way the idea fails.
Responds to the promise, friction, credibility, and relevance as a buyer rather than a builder.
How it runs
The first run creates the working configuration. Later sessions can reuse that context while rotating the proposing seat.
# 1. Copy the package into your skills folder skills/moltron-roundtable/ # 2. Ask your coordinator to start a session "Run the roundtable on this idea." # 3. The coordinator boots temporary seats provocateur → challenge received operator → execution path received skeptic → risk analysis received customer → buyer reaction received # 4. One memo returns decision + objections + next actions
Illustrative output
This example shows the output shape. It is illustrative, not a client result.
# Roundtable — recurring client brief idea PROVOCATEUR Ship the brief before the weekly call so the meeting begins with decisions, not status collection. OPERATOR Start with one account. Inputs: call notes, open tasks, delivery risks. Output: one approval-ready brief. SKEPTIC The brief fails if the source trail is missing or stale. Block output when the last client record is too old. CUSTOMER I will trust it if I can see where every risk came from and correct the source before the call. DECISION Build the one-account version first. Require source links, freshness labels, and human approval.
Original package
The preserved archive contains the complete skill instructions, a plain-English setup guide, and a documented configuration example.
Get the archive
Enter your details and we will email you an expiring download link. The ZIP is not published on this page.
Compatibility
No. This is the preserved OpenClaw-era package. The workflow can inform a modern implementation, but current Hermes compatibility is not verified.
No. The package is designed around temporary seats that spawn for the session and dissolve after the coordinator has collected their responses.
No. It is explicitly illustrative and exists only to show the expected structure of the debate and synthesis.
Bring one recurring workflow. We will map the sources, review gate, output, owner, and first live cycle.