← 返回 Skills 市场

consensus-support-reply-guard

Name: consensus-support-reply-guard
Author: kaicianflone

作者 Kai Cianflone · GitHub ↗ · v1.1.15

cross-platform ✓ 安全检测通过

464

总下载

当前安装

版本数

在 OpenClaw 中安装

/install consensus-support-reply-guard

功能描述

Risk-aware support response governance with persona-weighted consensus. Detects legal/sensitive/confidentiality issues, applies hard-block policy checks, and...

使用说明 (SKILL.md)

consensus-support-reply-guard

consensus-support-reply-guard is a customer-trust guard for support workflows.

What this skill does

evaluates support drafts before sending
detects high-risk claim patterns
blocks or rewrites responses when policy violations appear
updates persona reputations based on final decision alignment
preserves decision history in board artifacts

Why this matters

Support replies are high-frequency and brand-critical. This skill prevents overconfident legal/PII mistakes at scale.

Ecosystem role

Composes with consensus board state using explicit vote inputs and deterministic guard decisions.

Ideal scenarios

automated ticket triage replies
L1/L2 AI response review gates
regulated or enterprise support channels

Runtime, credentials, and network behavior

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

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.

安全使用建议

This package appears coherent for local support-reply governance, but before installing: 1) Inspect the consensus-guard-core package (dependency) to confirm its board read/write behavior and where it stores state; 2) Verify exactly how resolveStatePath uses CONSENSUS_STATE_FILE / CONSENSUS_STATE_ROOT to ensure artifacts are written to an intended directory (not a sensitive system path); 3) Treat the install metadata oddity ('creates binaries: node, tsx') as a packaging comment—do not allow any installer to overwrite your system node binary; 4) Run npm audit / review the dependency tree and, if possible, install and run in an isolated environment (container) first. If you rely on this in production, pin dependency versions and review the guard-core package source and release provenance.

功能分析

Type: OpenClaw Skill Name: consensus-support-reply-guard Version: 1.1.15 The OpenClaw skill 'consensus-support-reply-guard' is designed for risk-aware support response governance, detecting sensitive content and applying policy checks. Its code and documentation align with this stated purpose, focusing on input validation, policy evaluation via the 'consensus-guard-core' dependency, and writing auditable decision artifacts to a configurable local filesystem path. There is no evidence of prompt injection attempts in markdown files, unauthorized network calls, credential exfiltration, persistence mechanisms, or other malicious behaviors. File system access is limited to writing internal state, and required environment variables are for path configuration, not sensitive data.

能力评估

ℹ Purpose & Capability

Name/description (support reply governance) aligns with the code and SKILL.md: the package runs Node, uses a consensus-guard-core library, evaluates drafts, and writes decision artifacts to a configured state path. Minor oddity: the install metadata claims the package 'creates binaries: node, tsx' — installing an npm package normally should not create a system 'node' binary. This appears to be a metadata/packaging description issue rather than functional mismatch, but it's worth noting.

✓ Instruction Scope

SKILL.md and run.js/src/index.mjs show the skill performs deterministic local policy checks, aggregates votes (or accepts external votes), and writes artifacts to the configured consensus state path. The runtime does not reference unrelated system files or secrets; it only uses the consensus state path resolution and calls into consensus-guard-core wrappers for board reads/writes.

✓ Install Mechanism

The install is an npm package (consensus-support-reply-guard) with dependencies declared in package.json and package-lock.json; packages are resolved from the npm registry. There are no ad-hoc downloads from unknown URLs or archive extraction steps in the spec. The package-lock shows normal npm/optional deps (esbuild variants, etc.).

✓ Credentials

Declared required environment variables (CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT) are proportional to the stated behavior (filesystem-backed board/state artifacts). No API keys, tokens, or unrelated credentials are requested. The code does not read other environment variables beyond state path resolution.

✓ Persistence & Privilege

Skill does not request always:true and is user-invocable only. It writes to its configured consensus state path (expected for audit artifacts) and does not modify other skills or system-wide settings. Autonomous invocation is allowed by default but is not combined with any broad credential access.

如何使用

确保已安装 OpenClaw（本地或 Docker 部署）
在对话框中输入安装命令：/install consensus-support-reply-guard
安装完成后，直接呼叫该 Skill 的名称或使用 /consensus-support-reply-guard 触发
根据 Skill 的参数说明提供必要输入，即可获得结构化输出

版本历史

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

Decoupled guard/provider path; deterministic contract updates.

v1.1.8

Bump consensus-guard-core dependency to ^1.1.4 for corrected invoke contract and shared core alignment.

v1.1.7

Scanner hardening: remove required OPENAI_API_KEY metadata; clarify optional/conditional LLM credentials

v1.1.6

Dependency alignment: use npm semver consensus-persona-generator ^1.1.4 (no git refs)

v1.1.5

Scanner-hardening: explicit conditional credential declaration and runtime disclosure

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

元数据

Slug consensus-support-reply-guard

版本 1.1.15

许可证 —

累计安装 0

当前安装数 0

历史版本数 17

常见问题