Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Ledger-informed persona lifecycle management. Replaces low-performing personas with successor personas derived from mistake patterns in board decision histor...
Ledger-informed persona lifecycle management. Replaces low-performing personas with successor personas derived from mistake patterns in board decision histor...
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-respawn is the adaptive maintenance loop for persona governance.
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_respawn and updated persona_set artifacts keeps governance panel quality from stagnating
A static evaluator panel drifts over time. This skill provides lifecycle renewal so consensus quality improves instead of degrading.
Consumes persona-engine outputs for long-term adaptation and ties directly into board-ledger evidence.
long-running agent teams recurring decision domains with repeated failure classes autonomous systems requiring evaluator maintenance
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
consensus-guard-core is the first-party consensus package used in runtime execution 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-respawn
node --import tsx run.js --input ./examples/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() executes persona replacement based on lineage and failure patterns. Reputation deltas are expected from consensus-persona-engine outputs.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.