Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Generate and persist reusable persona panels (persona_set artifacts) for consensus decision workflows. This skill initializes evaluator diversity for downstr...
Generate and persist reusable persona panels (persona_set artifacts) for consensus decision workflows. This skill initializes evaluator diversity for downstr...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
consensus-persona-generator is the entrypoint for evaluator diversity in the Consensus.Tools ecosystem.
creates N distinct decision personas (role, bias, risk posture, voting style) assigns initial reputation baselines for weighted arbitration (ongoing updates handled by consensus-persona-engine) persists a versioned persona_set artifact to board state reuses compatible persona sets when possible to reduce churn
Most agent pipelines fail because one model self-approves its own output. This skill injects structured disagreement first, so later guards operate over explicit multi-perspective review.
Stack position: consensus-tools -> consensus-interact pattern -> consensus-persona-generator -> domain guards -> consensus-persona-engine consensus-tools: board/job/submission ledger substrate consensus-interact: board-native orchestration contract persona-generator: lightweight multi-agent initialization layer persona-engine: reputation update and persona lifecycle state transition layer
strict JSON input contract (board_id, task_context, n_personas, etc.) strict JSON output with persona_set_id, personas[], and board write refs deterministic/replayable behavior where feasible
bootstrap evaluators for email/publish/support/merge/action guards regenerate persona cohorts by domain or risk profile establish reusable governance personas for long-running automation
runtime binaries: node, tsx network calls: none in shipped generator logic environment config read by this package: CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT filesystem writes: board/state artifacts under the configured consensus state path
consensus-guard-core is the first-party consensus runtime dependency for this package versions are semver-pinned in package.json for reproducible installs this skill does not request host-wide privileges and does not mutate other skills
npm i consensus-persona-generator
node --import tsx run.js --input ./examples/persona-input.json
This skill is wired to the consensus-interact contract boundary (via shared consensus-guard-core wrappers where applicable): readBoardPolicy getLatestPersonaSet / getPersonaSet writeArtifact / writeDecision idempotent decision lookup This keeps board orchestration standardized across skills.
This skill exposes a canonical entrypoint: invoke(input, opts?) -> Promise<OutputJson | ErrorJson> invoke() initializes or reuses persona sets and executes board operations via shared guard-core wrappers. It does not perform ongoing reputation mutation; that belongs to consensus-persona-engine.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.