consensus-persona-generator
v1.1.14Generate and persist reusable persona panels (persona_set artifacts) for consensus decision workflows. This skill initializes evaluator diversity for downstr...
⭐ 0· 448·0 current·0 all-time
byKai Cianflone@kaicianflone
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & 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.Like a lobster shell, security has layers — review code before you run it.
latestvk97fgj8cyxk11v1bjsepcy7sv5825kjq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsnode, tsx
EnvCONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT
Install
Node
npm i -g consensus-persona-generator