← Back to Skills Marketplace
consensus-persona-respawn
by
Kai Cianflone
· GitHub ↗
· v1.1.13
582
Downloads
0
Stars
0
Active Installs
16
Versions
Install in OpenClaw
/install consensus-persona-respawn
Description
Ledger-informed persona lifecycle management. Replaces low-performing personas with successor personas derived from mistake patterns in board decision histor...
README (SKILL.md)
consensus-persona-respawn
consensus-persona-respawn is the adaptive maintenance loop for persona governance.
What this skill does
- identifies dead/weak personas by trigger or reputation threshold
- mines historical decision artifacts for mistake patterns
- generates successor persona profiles informed by those failures
- writes
persona_respawnand updatedpersona_setartifacts - keeps governance panel quality from stagnating
Why this matters
A static evaluator panel drifts over time. This skill provides lifecycle renewal so consensus quality improves instead of degrading.
Ecosystem role
Consumes persona-engine outputs for long-term adaptation and ties directly into board-ledger evidence.
Best use cases
- long-running agent teams
- recurring decision domains with repeated failure classes
- autonomous systems requiring evaluator maintenance
Runtime and network behavior
- runtime binaries:
node,tsx - network calls: none in shipped respawn 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-coreis the first-party consensus package used in runtime execution- versions are semver-pinned in
package.jsonfor reproducible installs - this skill does not request host-wide privileges and does not mutate other skills
Install
npm i consensus-persona-respawn
Quick start
node --import tsx run.js --input ./examples/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\x3COutputJson | ErrorJson>
invoke() executes persona replacement based on lineage and failure patterns. Reputation deltas are expected from consensus-persona-engine outputs.
Usage Guidance
This skill appears internally consistent for local, ledger-backed persona maintenance. Before installing: (1) confirm CONSENSUS_STATE_FILE / CONSENSUS_STATE_ROOT point to the intended state JSON (or supply statePath in opts) so artifact writes go to the right place; (2) review the behavior of consensus-guard-core/writeArtifact in your environment to ensure artifact writes are acceptable; (3) run the included tests in a disposable environment to verify expected behavior; (4) note that the package has no external credential or network requirements in shipped logic, but you should still pin dependencies and review upstream packages if you plan to run this in production.
Capability Analysis
Type: OpenClaw Skill
Name: consensus-persona-respawn
Version: 1.1.13
The skill's core logic and documentation appear benign, focusing on local persona lifecycle management and state artifact writes. However, the `run.js` entry point uses `process.argv` to parse the `--input` file path, which presents a shell injection vulnerability if the OpenClaw agent's orchestration layer constructs the command with unsanitized user input. While the skill itself does not demonstrate malicious intent, this RCE risk, stemming from a lack of input sanitization in the command-line argument parsing, classifies it as suspicious.
Capability Assessment
Purpose & Capability
Name/description (persona respawn from ledger history) align with required binaries (node, tsx), the npm package install, and the code which reads/writes board artifacts under a configured consensus state path. Required env vars (CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT) are coherent with a filesystem-backed state store.
Instruction Scope
SKILL.md and run.js/index.mjs limit runtime actions to reading the configured consensus state and writing persona_respawn/persona_set artifacts. There are no unexpected network calls, credential reads, or instructions to access unrelated system files.
Install Mechanism
Install uses a published npm package (consensus-persona-respawn) and depends on consensus-guard-core and tsx; this is an expected and traceable mechanism. No downloads from arbitrary URLs or extract-from-URL steps are present.
Credentials
The skill declares only state-path environment variables (CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT) and no secret tokens. The code itself calls resolveStatePath(opts) rather than reading process.env directly, but requiring state-path env vars is proportionate to a filesystem-backed ledger.
Persistence & Privilege
The skill is not always-on (always:false), does not request system-wide privileges, and only writes artifacts under the configured consensus state path. It does not modify other skills' configs.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install consensus-persona-respawn - After installation, invoke the skill by name or use
/consensus-persona-respawn - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.13
Aligned SKILL metadata/install docs for registry-only path and removed stale backend credential wording.
v1.1.12
Bumped consensus-guard-core dependency to ^1.1.15 and rolled forward release.
v1.1.11
Updated to consensus-guard-core ^1.1.13 with package-root import contract and compatibility fixes.
v1.1.10
Bumped consensus-guard-core dependency to ^1.1.11 and rolled forward release.
v1.1.9
Bumped consensus-guard-core dependency to ^1.1.10 and released patch version.
v1.1.8
Bumped semver deps (consensus-guard-core 1.1.5 / consensus-tools 0.1.8) and version.
v1.1.7
Docs/contracts aligned: persona-engine owns reputation updates.
v1.1.6
Scanner hardening: remove required OPENAI_API_KEY metadata; clarify optional/conditional LLM credentials
v1.1.5
confirm release sync
v1.1.4
Security hardening: explicit runtime/credential model and semver-pinned npm dependencies
v1.1.3
Packaging hardening: standalone install metadata, dependency cleanup, and safer runtime requirements
v1.1.2
Security hardening: statePath confined to safe root with traversal protection
v1.1.1
1.1.1: tested examples/input.json in e2e to keep docs and behavior synced
v1.1.0
Release 1.1.0: invoke contract + external-agent support + ecosystem alignment
v1.0.0
1.0.0 initial public release
v0.1.0
Initial public release
Metadata
Frequently Asked Questions
What is consensus-persona-respawn?
Ledger-informed persona lifecycle management. Replaces low-performing personas with successor personas derived from mistake patterns in board decision histor... It is an AI Agent Skill for Claude Code / OpenClaw, with 582 downloads so far.
How do I install consensus-persona-respawn?
Run "/install consensus-persona-respawn" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is consensus-persona-respawn free?
Yes, consensus-persona-respawn is completely free (open-source). You can download, install and use it at no cost.
Which platforms does consensus-persona-respawn support?
consensus-persona-respawn is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created consensus-persona-respawn?
It is built and maintained by Kai Cianflone (@kaicianflone); the current version is v1.1.13.
More Skills