consensus-persona-generator

Generate and persist reusable persona panels (persona_set artifacts) for consensus decision workflows. This skill initializes evaluator diversity for downstr...

Security Scan

The skill's code, runtime instructions, and declared requirements are consistent with its stated purpose (generating and persisting persona_set artifacts); nothing requested or installed appears disproportionate.

Purpose & Capability

Name/description match the code and files: the package deterministically generates persona entries and writes a persona_set artifact via consensus-guard-core. Required bins (node, tsx) and the two CONSENSUS_STATE_* env vars align with the stated need to read/write board state.

Instruction Scope

SKILL.md instructions and run.js only describe/perform deterministic persona generation, schema validation, and writing artifacts to the configured consensus state path. The runtime does not read unexpected system files or reach out to external endpoints in the shipped logic.

Install Mechanism

Install spec uses npm (package: consensus-persona-generator) which is the expected distribution mechanism for a Node package. This is standard but carries the usual npm-registry dependency risk (supply-chain compromise of dependencies like consensus-guard-core or transitive packages).

Credentials

Only CONSENSUS_STATE_FILE and CONSENSUS_STATE_ROOT are required; both are clearly tied to where state/artifacts are persisted. No unrelated secrets or cloud credentials are requested.

Persistence & Privilege

The skill is not always-enabled and does not request special platform privileges. It writes artifacts under the configured consensus state path only, and does not modify other skills or system-wide configs in the provided code.

Assessment

This skill appears to do what it says: generate persona sets and persist them to a configured state path. Before installing, ensure CONSENSUS_STATE_FILE and CONSENSUS_STATE_ROOT point to a dedicated, non-sensitive directory (do not point at /, home, or directories containing secrets). Review or pin the consensus-guard-core dependency (and its integrity) because runtime board operations are delegated to that package — supply-chain issues there would affect this skill. As usual with npm packages, prefer installing in an isolated environment or sandbox and inspect the installed dependency tree if you require additional assurance.

consensus-persona-generator is the entrypoint for evaluator diversity in the Consensus.Tools ecosystem.

What this skill does

• 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

Why this matters

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.

Ecosystem role

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

Inputs / outputs (automation-friendly)

• 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

Typical use cases

• 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, credentials, and network behavior

• 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

Dependency trust model

• 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

Install

npm i consensus-persona-generator

Quick start

node --import tsx run.js --input ./examples/persona-input.json

Tool-call integration

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.

Invoke Contract

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.