Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Persona-weighted pre-send email governance for AI systems. Produces APPROVE/BLOCK/REWRITE decisions, writes decision artifacts to the board ledger, updates p...
Persona-weighted pre-send email governance for AI systems. Produces APPROVE/BLOCK/REWRITE decisions, writes decision artifacts to the board ledger, updates p...
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-send-email-guard is a production-style outbound communication guardrail.
evaluates an email draft with a persona panel aggregates votes by reputation (weighted approval policy) enforces hard-block categories (sensitive data, legal/medical certainty, disallowed guarantees) returns final decision: APPROVE | BLOCK | REWRITE writes decision artifacts to board state
Email is high-impact and irreversible once sent. This skill reduces hallucinated promises and policy-violating claims before external side effects occur.
Stack position: consensus-tools -> consensus-interact pattern -> persona_set -> send-email-guard It converts raw generation into governed action with auditability.
strict JSON contracts for automation pipelines idempotent retries to prevent duplicate reputation mutation reputation updates calibrate evaluator influence over time
customer-facing outbound messaging partner/legal-sensitive communications automated campaign quality gates
runtime binaries: node, tsx network calls: none in guard decision 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 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
npm i consensus-send-email-guard
node --import tsx run.js --input ./examples/email-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.