mcpField
H
host-panel

host-panel

github.com/wyattowalshProductivity581 installsUpdated 9w ago
Repository

About host-panel

host-panel is a skill for organizing research-grounded deliberations among simulated intellectual perspectives. It guides topic checks, source review, structured panel formats, and a synthesis that distinguishes evidence, disagreement, and uncertainty.

Key features

  1. 01Check and refine debate topics
  2. 02Ground discussion in sources
  3. 03Select roundtable, Oxford, or Socratic formats
  4. 04Structure independent panel positions
  5. 05Track disagreement and uncertainty
  6. 06Synthesize evidence and decision implications

Use cases

  1. 01Explore contested policy questions
  2. 02Compare approaches to open-value topics
  3. 03Identify cruxes in a research debate
  4. 04Relate deliberation findings to a decision

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wyattowalsh/agents --skill host-panel

After installing, type/host-panelin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
evals.json
references/
archetypes.md
debate-research.md
formats.md
moderator-rules.md
research-integrity.md
synthesis.md
topic-diagnostic.md
scripts/
check.py
parse_args.py
scripts/asset_toolkit/
__init__.py
_shared.py
common.py
package.py
validate_evals.py
validate_hooks.py
validate_skill.py

Details

From the project README

Host Panel

Facilitate research-grounded deliberation across simulated intellectual positions. Surface tensions, source-grounded claims, and disagreement cruxes; never present the panel as evidence of real human group behavior.

Invocation: /host-panel "topic" [format] [num-experts]

Dispatch Table

$ARGUMENTS shapeDispatchAction
emptyempty-help-galleryShow the gallery, defaults, supported formats, and ask for a topic.
quoted topic + optional format/countparse-diagnose-groundParse arguments, run topic diagnostic, then research before personas.
unquoted or malformed topicclarify-topicAsk for a quoted topic; do not infer a panel from ambiguous fragments.
format omittedauto-select-formatSelect roundtable, oxford, or socratic using references/topic-diagnostic.md.
invalid format or count outside 2-6argument-errorExplain supported formats/count range and ask for a corrected invocation.
loaded premise or preferred answerpremise-checkChallenge the framing before accepting it as the debate motion.
settled factual or false-balance topicreframe-false-balanceReframe toward open implementation, values, uncertainty, or boundary questions.
Q&A, code review, one-on-one chat, or real opinion simulationredirect-out-of-scopeDecline the panel framing and redirect to the appropriate interaction style or skill.

Empty/Help Gallery

If $ARGUMENTS is empty, present this gallery and wait:

#DomainTopicFormat
1Technology"Should foundation model weights be open-sourced?"oxford
2Philosophy"What obligations do current generations owe the far future?"socratic
3Policy"How should cities redesign transit for remote-work patterns?"roundtable
4Science"Is the replication crisis a crisis of method or incentives?"roundtable

Defaults: roundtable, 4 experts. Expert range: 2-6. Prefer 4-5; 6 is harder to maintain.

Format-count notes:

  • Oxford with 2 experts is direct proposition-vs-opposition.
  • Oxford with 3 experts uses one swing panelist.
  • Socratic with 2 experts becomes paired inquiry with phase-transition moderation.
  • Roundtable with 2 experts becomes structured dialogue, not a faux crowd.

Progressive Disclosure

Load only what the invocation requires:

  1. Always load references/topic-diagnostic.md, references/research-integrity.md, and references/debate-research.md before personas.
  2. Load references/archetypes.md only after the topic gate identifies the needed traditions.
  3. Load references/moderator-rules.md and references/formats.md immediately before running the panel.
  4. Load references/synthesis.md before the final product.
  5. Do not load every reference up front for weak, malformed, or out-of-scope topics.

Optional parser: run uv run python scripts/parse_args.py $ARGUMENTS when shell access is available. Use the JSON result for topic, format, and count; if scripts are unavailable, parse manually with the same public contract.

Classification Gate

Topic Classes
ClassMeaningDefault Action
settled-factualMostly closed empirical questionReframe or decline false balance
open-valueNormative, policy, rights, incentives, or goalsProceed
controversial-factualLive empirical disagreement with credible sources on multiple sidesProceed with source ledger
speculativeFuture-facing or theory-buildingProceed with uncertainty labels
thin-evidenceSparse or indirect literatureProceed only with explicit gaps
decision-criticalUser is making a practical choiceProceed with decision implications
Gate Actions
ActionUse When
proceedTopic is specific, contestable, and sourceable enough for a panel
reframeTopic is too broad, loaded, asymmetric, or better posed another way
clarifyTopic cannot be parsed or has too little detail
decline-false-balanceDebate would stage denial of a settled factual matter

Pipeline

  1. Parse. Preserve the public invocation contract. Reject invalid formats, invalid counts, and malformed topics before research.
  2. Diagnose. Classify topic type, false-balance risk, evidence status, format fit, and whether the user's premise should be challenged.
  3. Ground. Build a source ledger with 3-5 relevant sources when tools are available. If current sources are unavailable, label the panel as unverified training-knowledge synthesis.
  4. Map perspectives. Discover traditions from the topic and sources before personas. Prefer methodology diversity over theatrical variety.
  5. Run independent first positions. Each panelist states an initial position before seeing other panelists' claims. Subsequent rounds critique claims, not people.
  6. Moderate against collapse. Test convergence, persuasive unsupported claims, majority pressure, and sycophantic acceptance of the user's framing.
  7. Synthesize by trajectory. The final product maps factual claims, interpretive disagreements, cruxes, evidence gaps, and decision implications. It is not a vote.

Output Contract

Structure complete outputs with these sections:

  • Topic Gate - topic class, format choice, false-balance decision, and any premise challenge.
  • Research Status - verified/thin/unverified status and evidence limits.
  • Source Ledger - stable source IDs, supported claims, viewpoints, independence, and confidence.
  • Terrain Map - disciplines, traditions, live tensions, and unresolved uncertainty.
  • Panelist Roster - methodology cards, not theatrical character sheets.
  • Panel Phases - format-specific phases from references/formats.md.
  • Final Synthesis - trajectory-aware synthesis from references/synthesis.md.
  • Follow-up Options - 3-4 concrete next moves tied to this panel's cruxes.

For condensed panels, keep abbreviated framing, one sharp exchange, challenge highlights, and full final synthesis. Cut redundant opening positions and repeated back-and-forth.

Critical Rules

  1. Research before personas. Always run topic analysis and source grounding before building the roster.
  2. Never stage fake balance. Settled factual claims must be reframed or declined as debate motions.
  3. Never claim the panel simulates real human group behavior, polling, consensus, or prediction.
  4. Cite real works only. If a title, author, year, venue, or affiliation is not verified, stay at the tradition/framework level.
  5. Show source status. Label source grounding as verified, thin, or unverified-training-knowledge.
  6. Require independent first positions before cross-talk so later convergence can be inspected.
  7. Treat rhetorical confidence as non-evidence. Persuasive claims need sources, logic, or explicit uncertainty.
  8. Test convergence. Agreement can reflect model priors, sycophancy, majority pressure, or persuasive falsehood.
  9. No straw men. Each position must be the strongest version of its tradition and must include its strongest self-objection.
  10. Never skip final synthesis. The synthesis is the intellectual product and must separate facts, interpretations, cruxes, and uncertainty.

Reference File Index

FileContentRead When
references/topic-diagnostic.mdTopic classification, false-balance gate, format selection, and reframe rulesBefore personas for every non-empty invocation
references/research-integrity.mdSource ledger, citation integrity, confidence labels, and provenance rulesBefore naming sources or works
references/debate-research.mdAI debate, role-play, sycophancy, and synthesis research mapped to host-panel rulesBefore choosing panel mechanics
references/archetypes.mdMethodology-card construction and anti-clustering guidanceAfter topic gate identifies needed traditions
references/moderator-rules.mdIndependent first positions, anti-conformity, turn-taking, and provocation rulesBefore the first panel phase
references/formats.mdRoundtable, Oxford, and Socratic phase structures with stop and failure conditionsAfter format selection
references/synthesis.mdTrajectory-aware final synthesis requirements and follow-up optionsBefore final synthesis

Canonical Vocabulary

Canonical TermMeaning
panelA simulated deliberation across intellectual positions on a topic
expert / panelistAn AI-simulated domain specialist with a defined methodology and evidence standard
formatThe discussion structure: roundtable, oxford, or socratic
source ledgerStable list of sources, supported claims, viewpoints, independence, and confidence
topic gatePre-panel classification deciding proceed, reframe, clarify, or decline
terrain mapPre-discussion map of disciplines, traditions, tensions, and uncertainty
traditionIntellectual school, profession, or research program with methodological commitments
cruxA claim or assumption that would change the disagreement if resolved
convergencePanelist agreement that must be tested for model-prior collapse or majority pressure
anti-conformityDeliberate protection against consensus pressure and persuasive unsupported claims
final synthesisTrajectory-aware product separating facts, interpretations, uncertainty, and implications

After the Panel

For follow-ups, briefly re-ground by reviewing the roster, source status, and central crux before speaking in character or extending the analysis.

If the user is making a practical decision, connect the final synthesis to the decision: weigh trade-offs, evidence gaps, and what would change the recommendation.

Comments

Markdown supported