FreeArchived OpenClaw skill

Put one idea through four opposing seats.

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.

Temporary seatsThe specialist agents spawn for the session instead of becoming permanent infrastructure.
One coordinatorYour main agent gathers the debate and synthesizes the final memo.
Plain filesThe package contains SKILL.md, README.md, and a documented config example.

Why four seats

One model agrees too easily. Give the idea resistance.

The roundtable forces the proposal through four different jobs: originality, execution, risk, and buyer relevance.

01

Generate tension

The provocateur tries to escape the obvious answer while the skeptic attacks whatever sounds clever but fragile.

02

Force execution detail

The operator asks what ships first, which dependency blocks it, and where the hidden complexity lives.

03

Keep the buyer in the room

The customer seat judges the idea from the outside, where novelty matters less than relevance and trust.

The four seats

Different jobs. One decision.

The value is not four agents repeating the same answer. Each seat receives a distinct lens and the coordinator must reconcile the conflict.

P

Provocateur

Pushes beyond the safe answer and proposes the move the rest of the room may reject too quickly.

O

Operator

Turns the proposal into concrete first steps, dependencies, owners, and constraints.

S

Skeptic

Finds weak assumptions, trust gaps, operational debt, and the easiest way the idea fails.

C

Customer

Responds to the promise, friction, credibility, and relevance as a buyer rather than a builder.

How it runs

Install once. Convene on demand.

The first run creates the working configuration. Later sessions can reuse that context while rotating the proposing seat.

roundtable.md
# 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

Disagreement in. Decision memo out.

This example shows the output shape. It is illustrative, not a client result.

decision-memo.md
# 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

Three files. No checkout.

The preserved archive contains the complete skill instructions, a plain-English setup guide, and a documented configuration example.

  • SKILL.md with the full workflow
  • README.md setup guide
  • config.example.json
  • Temporary seat architecture
  • Local memo output pattern
Get Moltron Roundtable by email

roundtable-skill.zip · 3 files · email delivery

Get the archive

Send the Roundtable skill to your inbox.

Enter your details and we will email you an expiring download link. The ZIP is not published on this page.

FREE DOWNLOADDELIVERED BY EMAILNO SPAM. UNSUBSCRIBE ANYTIME

Email me the Roundtable

We use these details to deliver this archive and send occasional Applied Leverage communications.

Compatibility

Know what you are downloading.

Is this a current Hermes skill?

No. This is the preserved OpenClaw-era package. The workflow can inform a modern implementation, but current Hermes compatibility is not verified.

Does it require four permanent agents?

No. The package is designed around temporary seats that spawn for the session and dissolve after the coordinator has collected their responses.

Is the sample memo a real result?

No. It is explicitly illustrative and exists only to show the expected structure of the debate and synthesis.

A roundtable debates the idea. An operating loop ships it.

Bring one recurring workflow. We will map the sources, review gate, output, owner, and first live cycle.