← ClaudeAtlas

moa-solvelisted

Use when you have a HARD, open-ended, high-stakes problem worth throwing multiple AI models at and pulling the best solution out — architecture decisions, strategy design, thorny debugging, research synthesis, "what am I missing", tool/system design. This is the SOLVE counterpart to multi-review (which critiques an existing artifact). It drives Hermes' NATIVE Mixture-of-Agents runtime (`/moa` and the `moa` virtual provider): a configured reference layer answers independently, then an aggregator writes a NEW best-of-breed answer via a component ledger — not an average, not a cut-and-paste splice. Also encodes WHEN NOT to use a panel (most problems), routing to a single strong model instead.
TechNickAI/hermes-skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill TechNickAI/hermes-skills
# MOA-Solve — Mixture-of-Agents for hard problems ## What this is A control plane for solving hard problems with multiple models, built on **Hermes' own MoA runtime**. Grounded in Mixture-of-Agents (Wang et al., Together AI, arXiv:2406.04692, ICLR 2025): a **reference layer** (several model families answer independently) plus an **aggregator** (one strong model writes a NEW synthesized answer). The paper's load-bearing result: the aggregator that _synthesizes_ beats an LLM-ranker that merely _picks the best proposal_. That is the empirical basis for "pull the best from EACH, don't pick the single best ONE." Important reframing (do not skip): "best from each" does NOT mean cut-and-paste splicing spans from references. Splicing produces Frankenstein artifacts where model A's architecture assumes state that model B's grafted completion never provides. It means: **synthesize a superior answer that is accountable to the strongest element found in each reference**, grafted through explicit interface checks. The component ledger (below) is how you do that without averaging to mush. **This skill does not implement fan-out.** Hermes already ships a real MoA runtime with parallel reference dispatch, per-slot provider/model routing, credential handling, prompt-cache decoration, usage/cost accounting, and trace persistence. This skill is the **method** — when to convene a panel, how to brief it, and how to synthesize the result. Do not hand-roll an HTTP fan-out script; see "Why there