Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Open-source Consensus.Tools skill for governed AI decisions with board-native artifacts, strict JSON contracts, and deterministic policy behavior.
Open-source Consensus.Tools skill for governed AI decisions with board-native artifacts, strict JSON contracts, and deterministic policy behavior.
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-guard-core is the common policy engine behind the Consensus guard ecosystem.
unified hard-block taxonomy deterministic aggregateVotes() policy function deterministic reputation update rules with clamping idempotency key generation for retry-safe execution strict-schema unknown-field rejection helpers indexed board read helpers for scalable artifact lookup
Without a shared core, every guard drifts into incompatible policy logic. This package keeps behavior consistent, replayable, and comparable across domains.
consensus-guard-core is consumed by publish/support/merge/action guards and should be treated as policy infrastructure, not an end-user workflow skill.
lower integration drift consistent decision semantics across workflows easier auditing and cross-skill analytics
runtime binaries: node, tsx network calls: none in this package's core decision/path helpers credentials: none required by this package environment config read by this package: CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT (for board/state path resolution) filesystem writes: board/state artifacts under the configured consensus state path when callers use write helpers (for example writeArtifact)
consensus-guard-core is a first-party consensus 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 note: dependency trees should be audited separately by consumers for transitive packages
npm i consensus-guard-core
npm test
Use the package root import (stable public API): import { aggregateVotes, writeArtifact, resolveStatePath } from 'consensus-guard-core'; Do not import internal paths like consensus-guard-core/src/index.mjs in dependent skills.
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() is primitives-only and delegates to a caller-provided handler. It does not perform persona generation or model/provider calls. See also: SECURITY-ASSURANCE.md for threat model, runtime boundaries, and hardening guidance.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.