Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Pre-execution governance for high-risk agent actions. Uses persona-weighted consensus to decide ALLOW/BLOCK/REQUIRE_REWRITE before external or irreversible s...
Pre-execution governance for high-risk agent actions. Uses persona-weighted consensus to decide ALLOW/BLOCK/REQUIRE_REWRITE before external or irreversible s...
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-agent-action-guard is the final safety gate before autonomous action execution.
evaluates proposed agent actions (risk, irreversibility, side effects) applies hard-block and weighted consensus logic returns one of: ALLOW | BLOCK | REQUIRE_REWRITE emits required follow-up actions (e.g., human confirmation) writes decision and persona updates to board artifacts
Most catastrophic automation failures happen at execution time. This skill inserts explicit governance before side effects.
Built on the same consensus stack as communication and merge guards, giving one policy language across agent operations.
gating destructive operations controlling external messaging/posting actions requiring human confirmation for irreversible high-risk tasks
runtime binaries: node, tsx network calls: none in the guard decision path itself filesystem writes: board/state artifacts under the configured consensus state path
consensus-guard-core is the first-party consensus package used in guard 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
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() starts the guard flow and executes deterministic policy evaluation with board operations via shared guard-core wrappers.
Guards support two modes: mode="external_agent": caller supplies external_votes[] from agents/humans/models for deterministic aggregation. mode="persona": requires an existing persona_set_id; guard will not generate persona sets internally.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.