MCP HubMCP Hub
Volver a habilidades

build-consensus

pjt222
Actualizado Yesterday
2 vistas
17
2
17
Ver en GitHub
Metaaiautomationdesigndata

Acerca de

Esta habilidad permite el consenso distribuido sin una autoridad central, utilizando mecanismos como votación por umbral y detección de quórum. Maneja la generación de propuestas, la defensa de las mismas, la resolución de bloqueos y la evaluación de calidad para decisiones grupales. Úsela cuando grupos sin líder necesiten elegir entre opciones, el control centralizado sea un cuello de botella, o para sistemas automatizados como IA multiagente o bases de datos distribuidas.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/build-consensus

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Konsens aufbauen

Achieve collective agreement across distributed agents ohne a central authority — using scout advocacy, threshold quorum sensing, and commitment dynamics modeled on honeybee swarm decision-making.

Wann verwenden

  • A group must collectively decide zwischen multiple options ohne a designated leader
  • Centralized decision-making is a bottleneck or a single point of failure
  • Stakeholders have different information and perspectives that muss integrated
  • Past decisions suffered from groupthink (premature convergence) or analysis paralysis (no convergence)
  • Designing automated systems that must reach consensus (distributed databases, multi-agent AI)
  • Complementing coordinate-swarm when the coordination requires explicit collective decisions

Eingaben

  • Erforderlich: The decision to be made (binary choice, selection from N options, parameter setting)
  • Erforderlich: The participating agents (team members, services, voters)
  • Optional: Known options with preliminary quality assessments
  • Optional: Decision urgency (time budget)
  • Optional: Acceptable error rate (can the group occasionally pick the second-best option?)
  • Optional: Current decision-making failure mode (groupthink, deadlock, flip-flopping)

Vorgehensweise

Schritt 1: Generieren Proposals Through Independent Scouting

Sicherstellen the decision space is adequately explored vor any advocacy begins.

  1. Zuweisen scouts to independently explore the option space:
    • Each scout evaluates options ohne knowing other scouts' findings
    • Independent evaluation prevents early herding toward popular-but-mediocre options
    • Scout count: at minimum, 3 scouts per serious option (for reliability)
  2. Scouts produce structured assessments:
    • Option identifier
    • Quality score (normalized 0-100 or categorical: poor/fair/good/excellent)
    • Key strengths and risks identified
    • Confidence level (how thoroughly was this option evaluated?)
  3. Aggregate scout reports ohne filtering — all options ueber a minimum quality threshold enter the advocacy phase

Erwartet: A set of independently evaluated proposals with quality scores and assessments. No option wurde eliminated by a single evaluator; diversity of perspective is preserved.

Bei Fehler: If scouts converge on the same option ohne independent evaluation, the scouting was not truly independent. Rerun with explicit information barriers. If too many options survive to the advocacy phase, raise the minimum quality threshold. If too few survive, lower it or add more scouts.

Schritt 2: Ausfuehren Advocacy Dynamics (Waggle Dance)

Erlauben scouts to advocate for their preferred options, with advocacy intensity proportional to quality.

  1. Each scout advocates for their top-rated option:
    • Advocacy intensity is proportional to the quality score (better options get more vigorous advocacy)
    • Advocacy is public — all agents observe all advocacy signals
    • Advocates present evidence and quality assessment, not just preference
  2. Uncommitted agents observe advocacy and evaluate:
    • Follow up on advocated options by inspecting them independently
    • If an agent's own inspection confirms the quality, they join the advocacy
    • If inspection reveals lower quality than advertised, they nicht join
  3. Cross-inspection dynamics:
    • Advocates for weaker options naturally lose followers as agents independently verify
    • Advocates for stronger options gain followers durch confirmed quality
    • The process is self-correcting: exaggerated advocacy fails the verification step
Advocacy Dynamics:
┌─────────────────────────────────────────────────────────┐
│ Scout A advocates Option 1 (quality 85) ──→ ◉◉◉◉◉     │
│ Scout B advocates Option 2 (quality 70) ──→ ◉◉◉        │
│ Scout C advocates Option 3 (quality 45) ──→ ◉           │
│                                                         │
│ Uncommitted agents inspect:                             │
│   Agent D inspects Option 1 → confirms → joins ◉◉◉◉◉◉  │
│   Agent E inspects Option 2 → confirms → joins ◉◉◉◉    │
│   Agent F inspects Option 3 → disagrees → inspects Opt 1│
│                               → confirms → joins ◉◉◉◉◉◉◉│
│                                                         │
│ Over time: Option 1 advocacy grows, Option 3 fades      │
└─────────────────────────────────────────────────────────┘

Erwartet: Advocacy for the best option(s) grows over time as agents independently verify quality. Advocacy for weaker options fades as verification fails. The group naturally converges toward the strongest option ohne any agent dictating the choice.

Bei Fehler: If advocacy doesn't converge (two options remain neck-and-neck), the options kann genuinely equivalent — proceed to quorum with either, or use a tiebreaker rule. If advocacy converges too fast on a mediocre option, increase the independence of evaluation (more scouts, stricter information barriers) and add a mandatory cross-inspection step.

Schritt 3: Set Quorum Threshold and Commit

Definieren the commitment threshold that triggers collective action.

  1. Set the quorum threshold:
    • Simple decisions: 50% + 1 of agents committed to one option
    • Important decisions: 66-75% committed to one option
    • Critical/irreversible decisions: 80%+ committed to one option
    • Rule of thumb: higher stakes → higher quorum → slower but more reliable consensus
  2. Ueberwachen commitment accumulation:
    • Verfolgen how many agents have committed to each option over time
    • Display commitment levels transparently (all agents can see the current state)
    • Do not allow commitment withdrawal mid-cycle (prevents oscillation)
  3. When quorum is reached:
    • The winning option is adopted as the collective decision
    • Advocates for losing options acknowledge the decision (no rogue agents)
    • Implementation begins sofort — delay nach consensus erodes commitment

Erwartet: A clear quorum moment where enough agents have independently committed to one option. The decision is legitimate because it emerged from independent evaluation, not authority or coercion.

Bei Fehler: If quorum is never reached innerhalb the time budget, escalate to Step 4 (deadlock resolution). If quorum is reached but agents are unhappy, the advocacy phase was too short — agents committed ohne adequate evaluation. If the consensus was wrong (discovered nach the fact), the independent scouting was insufficient — increase scout diversity and evaluation thoroughness in the next cycle.

Schritt 4: Loesen Deadlocks

Break decision gridlock when the natural consensus process stalls.

  1. Diagnose the deadlock type:
    • Genuine tie: two options are equally good → flip a coin; the cost of delay exceeds the cost of picking the "wrong" equal option
    • Information deficit: agents can't evaluate options well enough → invest in more scouting vor re-running advocacy
    • Faction formation: entrenched subgroups refuse to cross-inspect → introduce mandatory rotation where advocates must inspect the opposing option
    • Option proliferation: too many options fragment commitment → eliminate the bottom 50% and re-run advocacy
  2. Anwenden the appropriate resolution:
    • Genuine tie: random selection or merge options if compatible
    • Information deficit: time-boxed scouting extension
    • Faction formation: forced cross-inspection round
    • Option proliferation: ranked elimination tournament
  3. After resolution, reset the quorum clock and re-run Step 3

Erwartet: Deadlock resolved durch the appropriate intervention. The resolution is visible and accepted by the group as fair process, even if individual agents preferred a different outcome.

Bei Fehler: If deadlocks recur on the same decision, the decision framing kann wrong. Step back and ask: can the decision be decomposed into smaller, independent decisions? Can the scope be reduced? Is there a "try both and see" option? Sometimes the best consensus is "we'll run a time-boxed experiment."

Schritt 5: Bewerten Consensus Quality

Bewerten whether the consensus process produced a good decision, not just a decision.

  1. Post-decision assessment:
    • Was the winning option independently verified by mindestens N agents?
    • Was the decision speed appropriate (not too fast/groupthink, not too slow/paralysis)?
    • Did der Prozess surface information that would wurden missed by a single decision-maker?
    • Are agents committed to implementation, or merely compliant?
  2. Verfolgen consensus health metrics:
    • Time to quorum: decreasing over successive decisions indicates learning; increasing indicates growing complexity or dysfunction
    • Scout-to-commit ratio: how much scouting was needed per commitment? High ratio = difficult decision or low trust
    • Post-decision regret rate: how often does the group wish it had chosen differently?
  3. Feed learnings back into der Prozess:
    • Anpassen quorum thresholds basierend auf decision importance and past accuracy
    • Anpassen scout count basierend auf option complexity
    • Anpassen time budgets basierend auf historical time-to-quorum

Erwartet: A feedback loop that improves consensus quality over time. The group learns to scout more effectively, advocate more honestly, and commit more confidently.

Bei Fehler: If consensus quality metrics are poor (high regret, slow decisions), audit der Prozess for structural failures: insufficient scouting diversity, advocacy ohne verification, or thresholds set too low for the decision type. Rebuild the specific failing stage anstatt overhauling the entire process.

Validierung

  • Proposals were generated durch independent scouting (no herding)
  • Advocacy intensity was proportional to assessed quality
  • Uncommitted agents independently verified advocated options
  • Quorum threshold was appropriate for the decision's importance
  • Quorum was reached and the decision was implemented promptly
  • Deadlock resolution mechanism was available (even if unused)
  • Post-decision quality assessment was conducted

Haeufige Stolperfallen

  • Skipping independent scouting: Jumping directly to advocacy produces groupthink. The quality of consensus depends entirely on the quality of independent evaluation
  • Equal advocacy for unequal options: If every option gets the same advocacy unabhaengig von quality, der Prozess degenerates into random selection. Advocacy muss proportional to assessed quality
  • Commitment withdrawal: Allowing agents to un-commit creates oscillation. Once committed in a cycle, agents stay committed until the cycle resolves
  • Confusing consensus with unanimity: Consensus requires sufficient agreement, not total agreement. Waiting for 100% creates permanent deadlock
  • Ignoring the losing side: Agents who advocated for the losing option have information the group needs. Their concerns should inform implementation, even if they don't block the decision

Verwandte Skills

  • coordinate-swarm — foundational coordination framework that supports the signal-based consensus mechanism
  • defend-colony — collective defense decisions often require rapid consensus under threat
  • scale-colony — consensus mechanisms must adapt when the group size changes erheblich
  • dissolve-form — morphic skill for controlled dismantling, where consensus vor dissolution is critical
  • plan-sprint — sprint planning involves team consensus on commitment scope
  • conduct-retrospective — retrospectives are a form of consensus-building about process improvement
  • build-coherence — AI self-application variant; maps bee democracy to single-agent multi-path reasoning with confidence thresholds and deadlock resolution

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/de/skills/build-consensus
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Habilidades relacionadas

content-collections

Meta

Esta habilidad proporciona una configuración probada en producción para Content Collections, una herramienta centrada en TypeScript que transforma archivos Markdown/MDX en colecciones de datos con tipado seguro mediante validación Zod. Úsala al construir blogs, sitios de documentación o aplicaciones Vite + React con mucho contenido para garantizar seguridad de tipos y validación automática de contenido. Abarca todo, desde la configuración del plugin de Vite y compilación MDX hasta la optimización de despliegue y validación de esquemas.

Ver habilidad

polymarket

Meta

Esta habilidad permite a los desarrolladores crear aplicaciones con la plataforma de mercados de predicción Polymarket, incluyendo la integración de API para operaciones y datos de mercado. También proporciona transmisión de datos en tiempo real a través de WebSocket para monitorear operaciones en vivo y actividad del mercado. Úsela para implementar estrategias de trading o crear herramientas que procesen actualizaciones de mercado en tiempo real.

Ver habilidad

creating-opencode-plugins

Meta

Esta habilidad ayuda a los desarrolladores a crear complementos de OpenCode que se conectan a más de 25 tipos de eventos, como comandos, archivos y operaciones LSP. Proporciona la estructura del complemento, las especificaciones de la API de eventos y los patrones de implementación para módulos en JavaScript/TypeScript. Úsala cuando necesites interceptar, monitorear o extender el ciclo de vida del asistente de IA de OpenCode con lógica personalizada basada en eventos.

Ver habilidad

sglang

Meta

SGLang es un framework de alto rendimiento para el servicio de LLM que se especializa en generación rápida y estructurada para JSON, expresiones regulares y flujos de trabajo de agentes utilizando su caché de prefijos RadixAttention. Ofrece una inferencia significativamente más rápida, especialmente para tareas con prefijos repetidos, lo que lo hace ideal para salidas complejas y estructuradas, y conversaciones multiturno. Elige SGLang sobre alternativas como vLLM cuando necesites decodificación restringida o estés construyendo aplicaciones con uso extensivo de prefijos compartidos.

Ver habilidad