← Back to Skills Marketplace
kaicianflone

Consensus Publish Guard

by Kai Cianflone · GitHub ↗ · v1.1.17 · MIT-0
cross-platform ✓ Security Clean
439
Downloads
0
Stars
0
Active Installs
19
Versions
Install in OpenClaw
/install consensus-publish-guard
Description
Persona-weighted governance for outbound publishing (blog, social, announcements). Prevents unsafe public claims via hard-block checks, weighted consensus, r...
README (SKILL.md)

consensus-publish-guard

consensus-publish-guard protects public-facing content before release.

What this skill does

  • reviews content drafts with persona consensus
  • flags policy/legal/sensitive-risk patterns
  • decides APPROVE | BLOCK | REWRITE
  • emits rewrite patch when fixable
  • persists decision artifacts to board state

Why this matters

Public content creates brand, legal, and trust exposure. Consensus review creates a safer publish gate than single-pass generation.

Ecosystem role

Uses deterministic logic from consensus-guard-core and existing persona inputs, persisted via consensus board primitives.

Good fit for

  • AI-assisted social/media pipelines
  • product launch copy checks
  • policy-sensitive communications

Runtime, credentials, and network behavior

  • runtime binaries: node, tsx
  • network calls: none in the guard decision path itself
  • 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-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

Install assumptions

This repository currently expects a local sibling checkout of consensus-guard-core.

# from repos/ directory
# repos/
#   consensus-guard-core/
#   consensus-publish-guard/

Then install dependencies in this repo:

npm i

Install (registry)

npm i consensus-publish-guard

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() starts the guard flow and executes deterministic policy evaluation with board operations via shared guard-core wrappers.

external_agent mode

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.
Usage Guidance
This skill appears to do what it says: a local, deterministic publish guard that writes audit artifacts to a configured state path. Before installing, verify the consensus-guard-core dependency (it performs board reads/writes and may introduce additional I/O or network behavior), ensure CONSENSUS_STATE_FILE/CONSENSUS_STATE_ROOT point to a directory where you permit writes and that no sensitive secrets are stored there, and run the included tests (npm test / demo) in a sandbox. If you need absolute assurance of 'no network calls', inspect or vendor-lock the consensus-guard-core package source or run the guard in an isolated environment.
Capability Analysis
Type: OpenClaw Skill Name: consensus-publish-guard Version: 1.1.17 The consensus-publish-guard skill bundle implements a content governance and moderation system designed to review outbound drafts (social media, blogs) for policy risks. The code in src/index.mjs and run.js performs deterministic logic, such as keyword flagging and weighted vote aggregation, and persists results to a local state directory. No evidence of data exfiltration, malicious execution (eval/exec), or harmful prompt injection was found; the filesystem writes are restricted to configured state paths and a local output directory for audit artifacts.
Capability Assessment
Purpose & Capability
Name/description (persona-weighted publish guard) match the code and declared requirements: Node/tsx runtime, an npm package install, and two state-related env vars for the consensus state path. The package depends on consensus-guard-core for board operations which is expected for this role.
Instruction Scope
SKILL.md and code show a purely local decision path that reads an input JSON, computes votes/aggregation, and writes audit artifacts to a configured state path. The logic does not access unrelated system paths or request unrelated credentials. Caveat: board operations are delegated to consensus-guard-core (not included here), so its exact I/O/network behavior should be audited to fully confirm the 'no network calls' claim.
Install Mechanism
Install is via npm (consensus-publish-guard) which is normal for a Node skill. package-lock.json is present. This is moderate-risk compared to instruction-only skills because installing pulls code from the npm registry (including consensus-guard-core). No arbitrary remote download URLs, extract-from-URL, or obscure hosts were used.
Credentials
The only required env vars are CONSENSUS_STATE_FILE and CONSENSUS_STATE_ROOT, which match the stated need to locate/persist board state artifacts. No unrelated secrets (AWS keys, tokens, etc.) are requested.
Persistence & Privilege
always:false (no forced global presence). The skill writes its own decision/artifact files under the configured state path and creates output files (./out) when run via run.js. It does not request system-wide privilege changes or modify other skills' configs.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install consensus-publish-guard
  3. After installation, invoke the skill by name or use /consensus-publish-guard
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.17
consensus-publish-guard 1.1.17 - Updated internal package metadata. - No user-facing or functional changes.
v1.1.16
Aligned SKILL metadata/install docs for registry-only path and removed misleading install bins.
v1.1.15
Bumped consensus-guard-core dependency to ^1.1.15 and rolled forward release.
v1.1.14
Added explicit requires/env/install SKILL frontmatter for registry scanner parity.
v1.1.13
Updated to consensus-guard-core ^1.1.13 with package-root import contract and compatibility fixes.
v1.1.12
Bumped consensus-guard-core dependency to ^1.1.11 and rolled forward release.
v1.1.11
Bumped consensus-guard-core dependency to ^1.1.10 and released patch version.
v1.1.10
Bumped semver deps (consensus-guard-core 1.1.5 / consensus-tools 0.1.8) and version.
v1.1.9
Clarified install/runtime metadata and dependency-source behavior; regenerated lockfile.
v1.1.8
Decoupled guard/provider path; deterministic contract updates.
v1.1.7
Bump consensus-guard-core dependency to ^1.1.4 for corrected invoke contract and shared core alignment.
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
Initial public release
Metadata
Slug consensus-publish-guard
Version 1.1.17
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 19
Frequently Asked Questions

What is Consensus Publish Guard?

Persona-weighted governance for outbound publishing (blog, social, announcements). Prevents unsafe public claims via hard-block checks, weighted consensus, r... It is an AI Agent Skill for Claude Code / OpenClaw, with 439 downloads so far.

How do I install Consensus Publish Guard?

Run "/install consensus-publish-guard" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Consensus Publish Guard free?

Yes, Consensus Publish Guard is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Consensus Publish Guard support?

Consensus Publish Guard is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Consensus Publish Guard?

It is built and maintained by Kai Cianflone (@kaicianflone); the current version is v1.1.17.

💬 Comments